yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] kukuk10:
Hi Stratosk, I just experience weird behavior on my SGS after using Semaphore Auto brightness (Dark). Just after receiving and ending a phone call out in the sun, the phone just keep on opening and closing different apps on its own. This is the first time this happened just after using Semaphore 2.4.0. and Autobrightness...Weird thing is when I went indoor where the light is not so bright the opening and closing behavior stops..So i just have to disable Semaphore auto brightness..Im not sure if this is related to the new autobrightness but this is the first time it happened..thanks
[Galaxy S I9000 Android Development] stratosk:
I just implemented this and test it. I don't find it very useful. The brightness update is blocked/unblocked from sysfs. When unblocked, applications like flashlight can set the brightness but the driver overrides the setting almost immediately.

But I also implemented suspend/resume functions to stop the driver processing when screen goes off. It will be included in next release.

I have already thought this but I believe that this is not possible. The boot logo drawing takes place when frame buffer driver initializes and in that stage there is no filesystem mounted. But I will check this again.

I don't think this is related to kernel or auto brightness. Can you reproduce this or happened just once?
[Galaxy S I9000 Android Development] yani2000:
I also experienced some "Superuser" weridness.

When I flashed a rom and this kernel and added some apps to superuser allowed list I had no apps under allowed list in Superuser app, even tho access to some apps have been granted.

It didn't asked me again for access confirmation and I didn't put much thought in it.

Yesterday I was working with "rmmod" command in Terminal Emulator and after few minutes my phone froze and then soft-rebooted. I had to grant access to all of my previously granted apps again, but now they are in the allowed list in Superuser app.

Could the "rmmod sema_autobr" command have caused this or is it something else?

Stratosk what are your thoughts on the "rmmod" command, is it safe to use?

Note: I'm not using the latest Titanium Backup app.
[Galaxy S I9000 Android Development] stratosk:
Confirmation of root access is configurable through Superuser application.

The rmmod command is safe. But unloading modules that is used by the system may cause problems if the module does not clean properly when exits.

If you remove the smartassv2 governor with rmmod, you will get a crash. This is the reason I don't unload in semaphore scripts.

Maybe you rmmod the smartassv2 module?
[Galaxy S I9000 Android Development] Black Rose:
BTW, I am using a stock rooted kernel at the moment and Titanium gives the same warning.

You can turn off the warning in the Titanium settings.
[Galaxy S I9000 Android Development] yani2000:
Yes, I know. I said my confirmed apps didn't show up in allowed access list in Superuser app after fresh ROM+your kernel install.

After my phone crashed (after doing the "rmmod" command) I had to confirm access to apps again.

This time, they are in allowed list in Superuser app (and I hope they will stay there).

No, I didn't try to rmmod smartassV2 module but your auto brightness module (answer lies in my previous post). :)

Heh, you're also working on a fix?

I have it done already, but my fix is quick and dirty (made in Tasker app).

When start flashlight app --> "rmmod sema_autobr"; When exit flashlight app --> "insmod /lib/modules/sema_autobr.ko" :)

As stated before, my first try of rmmod didn't go too well (it was executed in Terminal Emulator app), but now, after many retries it works well (executed thru Locale Execute Plugin in Tasker app).
[Galaxy S I9000 Android Development] stratosk:
I think the lost of allowed apps in Superuser was due to the crash.

As I said rmmod should be safe. If this crashes with sema_autobr.ko then something goes wrong in my module when unloading it.

I tried to fix it but with no luck. I unblocked the brightness setting but the Semaphore driver overrides the adjustment from framework.

Edit: I just tried to load and unload the module sema_autobr.ko (with insmod, rmmod) through adb shell. I did it about 100 times. No reboot.
[Galaxy S I9000 Android Development] yani2000:
Yes, I also think that I lost my phantom allowed app list in Superuser was due to the crash.

You didn't get what I was trying to say, but it's OK, nobody else posted similar problems.

I guess it only happened to me due to some faulty flashing or something. No worries! :)

Yes, same with me! -->
[Galaxy S I9000 Android Development] stratosk:
I'm sorry that I didn't get it. :)

Please clarify.
[Galaxy S I9000 Android Development] yani2000:
Problem lies in this first part of the next list (points 1-3):

1. flashed a ROM and your Semaphore kernel

2. Run Root Explorer and grant it ROOT access.

3. Root Explorer app not shown in Superuser app under allowed app list, but Root Explorer never nagged me to reconfirm access!

4. After few days I executed "rmmod sema_autobr" command in Terminal Emulator app.

Phone froze after few minutes and then soft-rebooted.

5. Root Explorer and other apps requested ROOT access again, but this time they are normally visible in allowed apps list in Superuser app.

6. Run Flashligh app with "rmmod"/"insmod" commands hundred times again without problems.

And it's working really perfectly after that crash. :)
[Galaxy S I9000 Android Development] stratosk:
Now, I see your point.

But I think this (points 1-3) is not kernel issue. Kernel installs su binary. An applications runs the su, and su 'asks' Superuser application for grant or not the permissions. Kernel has nothing to do with this.

Also, rmmod command should unload the module in milliseconds. If there was a problem in module, your phone would crash immediately after the rmmod command. (you may try it with a rmmod with smartass module - please note that this cause a reboot)
[Galaxy S I9000 Android Development] jeozme:
It is working fine with Terminal Emulator for me. Can you tell me how to do this automatically with Tasker? I can open TE when starting Flashlight but I have no clue how to type su/rmmod/insmod in there automatically. (I don't want to buy locale)
[Galaxy S I9000 Android Development] yani2000:
I'm actually waiting for stratosk to hopefully come up with a better solution, but if there is enough demand for this I can release the quick and dirty fix (Tasker solution).

All that are interested can just send me a PM.
[Galaxy S I9000 Android Development] stratosk:
Hi,

Yes, it supports.
[Galaxy S I9000 Android Development] hackeron:
No issues at all so far with the latest version.. works good. However.. havent tried all functions like auto brightness stuff yet... only some tweaks
[Galaxy S I9000 Android Development] yani2000:
Semaphore's Auto Brightness quick and dirty fix for Flashlight

Here is the quick and dirty fix that all of you requested and will give you max brightness on Flashlight apps.

What you need installed:

- Tasker (paid app :( - but one of the reasons Android OS is better than iOS :) )

- Locale Execute Plug-in (free app & works with Tasker!)

Go to home screen with at least 1x1 free space on it.

Add a Shortcut and choose "Task" (Tasker icon).

Choose "New Task" and name it "Flashlight" and check "One-Time".

- Add --> Plugin --> Execute --> Configuration: "@! rmmod sema_autobr" (without the " sign; press back button to save)

- Add --> Application --> Load app --> Choose Flashlight app.

Set icon: just choose "Application icon" and then choose the same Flashlight app.

Add Profile and name it (eg. Flashlight app).

Choose context:

Application: Again choose the same Flashlight app.

Add task:

- Add --> Plugin --> Execute --> Configuration: "@! insmod /lib/modules/sema_autobr.ko" (without the " sign; press back button to save)

Move this task to be an Exit task.

My Flashlight app is: Color Flashlight.

Of course my own solution is a bit different (hold phone face down and flashlight automatically opens), because there are 100 different ways to do it in Tasker. This is just an example.

You just need to make sure that the "rmmod" command is executed before the Flashlight app is started and "insmod" command is executed after the Flashlight app is closed.

Also make sure that you accept ROOT access twice for Locale Execute plugin (one for "rmmod" and one for "insmod" command).

And the Semaphore's Auto Brightness profiles (Normal, Bright, Dark) stay the same after you exit the Flashlight app.

(Remarks are in green.)
[Galaxy S I9000 Android Development] jacobuscuracao:
this kernel Rules!

was on 4.0.3 for several months on and off TH or Onecosmic etc but finally got to a point where it screwed my phone and I couldn't even get into recovery.

flashed JVZ and CF-Root and then Semaphore and it's all Good - everything I need and faster than any current ICS build :)
[Galaxy S I9000 Android Development] djb77:
Yea I had my time testing out some ICS builds, but I ended up back on 2.3.x very quickly. ICS is ok but too many bugs at the moment.
[Galaxy S I9000 Android Development] bralgei:
i agree.

and if you realy want battery life, change your launcher to Ice Cream Sandwich 4.0

and you will get 40% more battery life.

I do not understand why TW launcher consumes so much power? well this is one major trick.

Btw. I have 2700 score in quadrant and with no overclocking.

I run this kernel (semafore 2.4) over GalaxyDroid 5.0 rom.

Battery last 2 days.
[Galaxy S I9000 Android Development] djb77:
Do you know where I could grab just the ICS Launcher without the whole Firmware? I'm interested in checking it out on a 2.3.6
[Galaxy S I9000 Android Development] hackeron:
Can you guys test if it blinks green when you press power button to shut down screen?
[Galaxy S I9000 Android Development] jocke_lulle:
Its due to the voodoo color. You can try to set it to stock color in semaphore app. Or you can try to do as Stratosk says here http://www.semaphore.gr/faq

Another trick is to use screen off effect:)
[Galaxy S I9000 Android Development] Madmanden:
No green here, just the lovely crt off effect. :)
[Galaxy S I9000 Android Development] bralgei:
iti is on the market if you search for ''ICS launcher" - I am using the Team Syndicate version.

Works in background and use so little power.

I kind of tested a lot of launchers.

Launcher Pro is another viable option.

But no TWLauncher. I tested this JW1 version for 5 days. In the moment I switched back to my old ICS Launcher...bang...no more draining.

I choosed to do so because I had to optimise the rest of the settinggs and programs running.

I knew that twlauncher consumes batterry, but I left it at the end.

Also, I use Titanium Pro to freeze all bloatware and useless programs that runs in the back.

I have only 4 programs constantly running including BLN (which I can live without) and whatapp that is the biggest consumer.

With whatapp closed I can have 4 days the battery running, but I need to be online.

good luck,
[Galaxy S I9000 Android Development] darckengel:
When you tried ICS, you realise that this launcher on the market is just a themed launcher to looks like ICS but has nothing to compare with the real one.

Go launcher is a lot better and you can theme it like ICS too if you really want.
[Galaxy S I9000 Android Development] jacobuscuracao:
I use ADW launcher and if you change the settings to allow for 5 icons in the dock, then it looks EXACTLY like ICS. You can also change the speed of the scroll to make it more smooth when changing pages.

For browser I've never used stock anyway: always use Opera with 'link' to keep my bookmarks. No browser beats Opera at this time.

use MIlocker to get rid of the standard lock screen (I HATE the full swipe to open)

sorry for the OT
[Galaxy S I9000 Android Development] bralgei:
of course I know that.

I am interested in battery life..that is why I choose this interface.
[Galaxy S I9000 Android Development] ~ Myzrael ~:
Hey stratosk i saw glitch kernel has a very complex but powerful overclock module, you can change system bus and overclock cpu ram and gpu. I don't know if you want to integrate in semaphore a so advanced (and dangerous) feature, anyway it would be cool :-)
[Galaxy S I9000 Android Development] fylim:
I was going to ask the same ;)
[Galaxy S I9000 Android Development] manjee:
Thank you, it works flawlessly :)
[Galaxy S I9000 Android Development] DarkSorcerer:
I second that on Go Launcher.

It has improved a lot lately, and even with all that set of settings, it's still one of the fastest and smooth launchers available.

I've been using Zeam, but the smoothness is gone in the latest releases. So, Go Launcher EX with ICS theme works fine for me.
[Galaxy S I9000 Android Development] ~ Myzrael ~:
Go launcher is more customizable, but adw is smoother
[Galaxy S I9000 Android Development] stratosk:
Hi,

Thanks, it's sounds interesting. But I don't think that I want something like that at the moment.

I'm pretty sure that many people will have problem with this. It's very nice but I think it's a little advanced (as you said) for many users. Maybe in the future.
[Galaxy S I9000 Android Development] zsandras:
In Call Recorder

Hi, stratosk I should like ask you if would be possible to find a working InCallRecorder apk which works with your kernel and Darkys JW1 ROM. I'm looking for a REC solution same as on Android Froyo was. Any idea?
[Galaxy S I9000 Android Development] stratosk:
Just in case that anyone is interested in:

JW1_2.4.0sc

- Stock color (voodoo color, speedmod color reverted)

- Semaphore Auto Brightness disabling when screen off
[Galaxy S I9000 Android Development] ZaneZam:
Thx Stratosk! My phone or rather my eyes likes the stock colorsettings much more than the voodo/speedmod fix

settings! I've forgotten how sharp my display can be! :) even with your autobrightness driver set to dark the colors don't look washed out as it was on voodo and everything stays sharp! Damn now i cant go back, i hope this is a preview 2.5.0 version :):) I'm really excited about the difference!
[Galaxy S I9000 Android Development] stratosk:
You welcome.

Actually, semaphore auto brightness does not have the same flexibility as with voodoo color. But if people want stock color I will try to add more levels of brightness and maintain both versions.
[Galaxy S I9000 Android Development] ZaneZam:
I would definitely appreciate this!! :)
[Galaxy S I9000 Android Development] kpucci:
Does this kernel support the galaxy s i9000m (bell canada)? I am hoping to use simplicity rom which uses semaphore.
[Galaxy S I9000 Android Development] mchud:
Yes. No problem. I have been using it for many releases now on a i9000m.
[Galaxy S I9000 Android Development] Dan_Aykroyd:
@stratosk

@stratosk:

I saw your latest release of the SC version (stock colors). What's the benefit of having auto brightness disabled when screen is off?

Also, will you be maintaining a third version from now on? (normal, bigmem and stock color)

Thanks!
[Galaxy S I9000 Android Development] Rebel2k:
The main purpose of having brightness control off while screen is off is to save up battery! :) (the brightness sensor isn't polled anymore, as indeed, that's useless, at least I guess!)
[Galaxy S I9000 Android Development] stratosk:
That's correct, this is the reason. The sensor does not polled and the brightness does not be set.

@Dan_Aykroyd

Yes, I will try to maintain 2 versions if people want a stock color version.

For my phone stock colors are fine. But, yesterday I compared my phone (with stock colors) with my brothers one (I9000 plus, everything stock). The difference was amazing. Mine has warm colors but my brother's one was very bluish.
[Galaxy S I9000 Android Development] hackeron:
What about Lukiqq's color tweaks, or stock cm7 colors, anything worth looking into?

For me I like the sharpness of stock colors, but its a litte too blueish and a little washed out..

Problem with voodoo color is that it looks crap for me at low grays/blues.. But colors also looks a bit more vivid in most cases..
[Galaxy S I9000 Android Development] flolep:
Honestly, for me and for several users who tried it, the best colors I saw on my sgs are the colours obtained by lukiqq who worked enormously on this figuring the best with several different versions, tests and users reporting.

The last implementation of lukiqq colors in his galaxian kernel is just perfect...

But as my favorite kernel is semaphore, the compromise is speedmod neutral colors.

But for sure, 100%, for me, speedmod, voodoo or lukiqq's implementations are far better than stock and I just won't never return to stock again.

But it's only my own opinion.

Take care.

+ +

EDIT: lol, hackeron, you were just faster, totally agree :p

Sent from my GT-I9000
[Galaxy S I9000 Android Development] darckengel:
Cm colors give me very ugly artifacts on dark pictures (tested on ics)

Using voodoo colors you can adjust to have very nice colors

But these tweaks are very depending on the brightness of the screen and with autobrightness, my settingd gives me sometimes a very ugly splash of yellow/green colors (i use very low colors settings usually) so i had to modify my settings to avoid this but i lose in picture quality, lukiq colors gives a good compromise in image quality and you don't have the typical voodoo colors splash bug. I know that tatsuya79 used to adapt luqik colors to talon kernel and release a lukis color version for every new talon version, maybe he could helo or do the same for semaphore
[Galaxy S I9000 Android Development] stratosk:
Maybe, I will try Lukiqq's colors when I'll find some time.
[Galaxy S I9000 Android Development] ~ Myzrael ~:
Talking about colors, has someone tried bravia engine? Does it really work?
[Galaxy S I9000 Android Development] darckengel:
It doesn't work yet, it's just placebo atm, just read ykk_five thread about it
[Galaxy S I9000 Android Development] Fenvarien:
Testing the 2.4.0sc kernel currently... Semaphore Autobrightness doesn't work here anymore after flashing the kernel. Nothing else has been changed, tried disabling and enabling via Semaphore App.

... using tapatalk
[Galaxy S I9000 Android Development] darckengel:
I works for me (just tried in putting my thumb on light sensor and brightness reduced nicely and gradually).
[Galaxy S I9000 Android Development] stratosk:
It works differently. With voodoo colour we have 255 levels of brightness. We can change the brightness to any level. With stock colour we have specific levels that the brightness can be adjusted.
[Galaxy S I9000 Android Development] Fenvarien:
I tried it in absolute darkness, the screen stayed bright. After flashing back to standard 2.4.0 the brightness is gradually reduced as it did before.

... using tapatalk
[Galaxy S I9000 Android Development] stratosk:
Yes, with the voodoo color reverted the brightness can be adjusted too low.

Did you try it on a bright environment (cover/uncover the sensor)?
[Galaxy S I9000 Android Development] Fenvarien:
Yes, I tried in a very bright room and could provoke an adjustment by covering the sensor. Thanks for the clarification, Stratosk!

But I will return to voodoo colours, because stock colour is too washed out for me and the brightness adjustment with the non-sc kernel version is faster and darker.

... using tapatalk
[Galaxy S I9000 Android Development] ingineru:
With the stock kernel sharpness is very very bad, best example is comments on the m.engadget.com site.

Semaphore colors are perfect for me.

Using 2.4 bm
[Galaxy S I9000 Android Development] djb77:
I can't really complain either about the default colours in Semaphore. I do get a little bit of green-screen every now and then when turning it back on, but not enough to talk about. Then again, I havent really remember stock colours anymore lol.

If its not too much to make another version for other users when updates come out (small editing etc) it would be nice to see both made available for people to choose from.
[Galaxy S I9000 Android Development] Fenvarien:
Of course only Stratosk can tell how much work it is, but maintaining 2 versions with non-bm and bm variants could be quite time consuming...

Anyways, the great work of Stratosk is highly appreciated and I can't imagine my I9000 without Semaphore! :-)

... using tapatalk
[Galaxy S I9000 Android Development] djb77:
Just a suggestion thats all...
[Galaxy S I9000 Android Development] stratosk:
Actually, I maintain a bm and non-bm for captivate also. :)

But, I think a can do this.
[Galaxy S I9000 Android Development] Bogie1:
And thank you very much for the Cappy versions too!
[Galaxy S I9000 Android Development] Nergla:
Hi - did you get any feedback from Titanium Backup regarding the root permissions ?
[Galaxy S I9000 Android Development] djb77:
Yea was wondering the same thing...
[Galaxy S I9000 Android Development] stratosk:
No, not yet. I will send an email to the author of Superuser also.
[Galaxy S I9000 Android Development] chachi:
(grovel)

sc-bm if you get bored this weekend please. ? :D
[Galaxy S I9000 Android Development] montrealguy:
Is there any danger to using the overclocking option on Semphore 2.4? Does it increase the responsiveness of the phone?

When it overclocks, doesn't it use up the battery much faster?
[Galaxy S I9000 Android Development] cenonmin:
Hi all,

Just wondering if the latest JW1 works on a JVS ROM (Tweaky) ?

Thank you.
[Galaxy S I9000 Android Development] stratosk:
Yes, yes and yes. :)

About overclocking. Chip manufacturers design a chip to run upt to a specific frequency (1GHz in our case). But always they design it with a tolerance. I think that using an overclocking with logical limits, it's safe. I believe that OC by 20-30% is safe, but you have to use it with your own risk.

I use 1.2GHz on my phone for about 7-8 months and so far never had issues.

Edit: Consumed power on a chip is linear proportional to frequency. So, if you overclocking to 1.2Ghz you consume 20% more power than running on 1GHz (considering that your phone always stays at 1GHz).
[Galaxy S I9000 Android Development] stratosk:
Hi,

Yes it should work.
[Galaxy S I9000 Android Development] jugster:
I just wanted to add that power consumption does not scale linearly with frequency. Perhaps in the range we are playing with it it does. But not generically.

Besides that I think your kernel rocks, but right now I'm trying ics which is pretty neat.
[Galaxy S I9000 Android Development] cenonmin:
Thank you, quick response as always :)
[Galaxy S I9000 Android Development] stratosk:
I read this in wikipedia http://en.wikipedia.org/wiki/CPU_power_dissipation:

The power consumed by a CPU, is approximately proportional to current CPU frequency, and to the square of the CPU voltage:

P = C*V2*f

(where C is capacitance, f is frequency and V is voltage).

I also read this http://www.linuxinsight.com/files/ols2006/pallipadi-reprint.pdf

written from creators of ondemand governor.

I'm too bored to search my old books from university, so I'm not totally sure.:)
[Galaxy S I9000 Android Development] bralgei:
I dissagree, It works super. You can see after you flash in CWM, that is a visual improovement in clarity, color and smoothness.
[Galaxy S I9000 Android Development] tiwag:
Thanks for the link to the interesting

Article. See chapter 2.1. Says the same as Wikipedia (but adds leakage and switching losses as further terms as well)

You can be sure.

See also here, i wrote also about this effect.

http://xdaforums.com/showthread.php?p=19210656

Brgds tiwag
[Galaxy S I9000 Android Development] mammenj:
I had the same problem with cf-root. The workaround was to turn off the wifi and reboot the phone, after reboot bluetooth started working for me.
[Galaxy S I9000 Android Development] habylab:
Whenever I turn on wireless tehthering, I get an error underneath it, where it normally says activated? Is this normal or do I need to load a module. I think I did the iptables one but no change since doing it. Maybe the wrong permissions? I also couldn't get conservative enabled via this method too, using a module, but I've given up using that for now.
[Galaxy S I9000 Android Development] johan81:
What kernel do you use? If it is Semaphore's, read the first post of his thread and you will find the answer.