yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] nmcc89:
This thread by droidphile in the sgs2 forums and this thread by knzo in the optimus black forums have detailed explanations for both governers and i/o schedulers. I've found them both very useful before.
[Galaxy S I9000 Android Development] Difusal:
what the hell? :o I flash semaphore constantly, but now, when I flash it, I just get the Semaphore app! no sight of CWM and SU app :o what's wrong?
[Galaxy S I9000 Android Development] ZaneZam:
All is normal, stratosk removed them a few versions ago!
[Galaxy S I9000 Android Development] robogo1982:
Sorry for my delayed response guys :)

First, my phone told me the "two bootloaders walk into a bar" joke :D after that, there were occasional small freezes when I tried doing something the phone didn't expect me to do. I know it sounds weird, but for instance, I hit the home button in the middle of writing an email in Gmail and it kinda hesitated a bit. The overall performance of the phone was slightly slower than on 2.1.1, as soon as I went back to it it was all fine.

Maybe I'm imagining things.
[Galaxy S I9000 Android Development] stratosk:
You definitely don't imagine things. :)

But, how long did you try the new version?

Maybe an instant load on your phone caused this?
[Galaxy S I9000 Android Development] Difusal:
why? :x

I installed 1.8.0 and then 2.2.0 and now I still have those apps as I would expect.

But if I installed only 2.2.0, I would have only the semaphore app and no SU or CWM apps :s
[Galaxy S I9000 Android Development] stratosk:
You may install superuser application anytime you want from market.

Also, you may have reboot in recovery for all CWM functionality.
[Galaxy S I9000 Android Development] burakgon:
Amazing job. Looks like big imporivement after 2.1. I like the new trigger. Sh*t I can'y turn back to ics because of wonderful semaphore.
[Galaxy S I9000 Android Development] ZaneZam:
Thats right, if you update from 1.8.0 you will still have the apps installed because

the update does not remove them. When you start from scratch they are not going to be installed because they are not included anymore in the new version, so all is normal :)

as stratosk said you can reinstall superuser from market and CWM manger from somewhere or you could go the self-experienced way 1.8.0 -> 2.2.0 again. ;)
[Galaxy S I9000 Android Development] micalb:
In call audio problem

Hi all, I've tried a lot of FW/Kernel combo before landing here and I love this config, I'm now on JW1/JVT modem/2.2.0 Kernel, but i have a wierd problem with audio during call.

When I receive a call and i put handsfree on, after a while people stop receive my voice, I could hear them normally (pause/unpause the call solve the problem).

I had this problem with previous Semaphore kernel and previous ROM, that's why I tried to change them both, I only have same modem/CSC of previous config.

I know it's probably nothing related to kernel as I have searched and nobody complain about that, I'm only looking for hints for debug this terrible problem.

And yes, I've wiped, cleared cache and dalvik, Hope someone could help me.
[Galaxy S I9000 Android Development] Darksword:
well, that happens to me sometimes but in a different way

ppl can hear me but i cant hear them till i do hold/unhold

and its a famous issue of the JVT modem (even though its one of the best and most powerful modems) but some ppl face that problem and im ok with it since it has a strong wifi/gsm signal
[Galaxy S I9000 Android Development] micalb:
My next test is to set in voodoo control app recording presets set it to original, this is suppse to be a workaround in CM7 for hello hello bug, I'll reprt result as soon as i get it.
[Galaxy S I9000 Android Development] DarknessWarrior:
@ your sig: http://www.crazyaboutmobile.com/2011/12/27/samsung-reviewing-galaxy-ics-upgrades-response-demand/

there's still hope :D
[Galaxy S I9000 Android Development] stratosk:
New version JW1_2.3.0

- ondemand: is_is_busy = 0, sampling_down_momentum = 0, sampling_rate = 40000 when screen off

- Semaphore Auto brightness driver (enable through Semaphore Application - disable auto brightness from settings first, for best results set brightness to lowest value from settings)

This is the first version of my auto brightness mini driver. So, please, If you have problems just disable it. I will try to improve it in next versions. :)
[Galaxy S I9000 Android Development] linyuhang24:
nice job, but where is the download link?
[Galaxy S I9000 Android Development] stratosk:
I'm sorry. I removed the link due to an error.

It's OK now.
[Galaxy S I9000 Android Development] nmeuret:
2.3.0 installed on oSerX JVZ ROM, install OK, works Ok so far.
[Galaxy S I9000 Android Development] andip71:
As always.... flashed already, will post my findings if any.

Thanks for the work. Especially the changed polling interval when screen off sounds very good for me (and my battery).

Andi
[Galaxy S I9000 Android Development] dherre65:
Sounds great! Could you give us some details on how your autobrightness differs from the Sammy one? Thanks :)
[Galaxy S I9000 Android Development] robogo1982:
It was for one whole day. Will do more testing when I get some time :)
[Galaxy S I9000 Android Development] stratosk:
I made this as an alternative to the default one. It's disabled by default.

Now, I understood why Samsung had such issues with auto brightness. :) Because you can't get an accurate measurement from light sensor. Some times when bring your phone under a direct light, it gives you lower values than greater one!

I don't what exactly Samsung does in the framework. But here is what I did:

First of all I tried to give more dark settings. This will be configurable in next versions.

The brightness values are from 10 (maybe to dark?) to 255 (the most bright).

The driver gets sample input from light sensor every 0.4s. After 2 seconds calculates the average input from 5 samples and if there is big difference from previous average adjust the brightness immediately. If there is no big difference adjust the brightness by just one step.
[Galaxy S I9000 Android Development] Sacob:
can't wait for 2.3.0 BM
[Galaxy S I9000 Android Development] Rebel2k:
Flashed the 2.3.0 already, to test. Everything is fine after a few minutes. I'll continue to test! ;)
[Galaxy S I9000 Android Development] chachi:
thanks for this stratos ... a bm version would be nice but I'm not going to moan about it, happiest holidays to you and kudos for taking the time during this period to do this
[Galaxy S I9000 Android Development] Ashtrix:
Stratosk does his magic again ;)..!

Thank you again....though i'm on ICS , i'd love to check on your thread daily for the wonderful updates & new mods that you put into your kernel..hope that i can get a new Semaphore for ICS :p .
[Galaxy S I9000 Android Development] dherre65:
Thank you for the response. I'm flashing a stock rom right now, going to test it from now.
[Galaxy S I9000 Android Development] DarkSorcerer:
Hi stratosk,

Hope you had a good holiday! Meanwhile, new version.. You've certainly been busy!

Would like to know if you think the autobrightness module will have its toll on battery life... What do you think?

Thanks (and installing 2.3.0, of course! ;) )
[Galaxy S I9000 Android Development] stratosk:
Hi,

I'm still on vacation (that's why the new version :) ). It was OK. What about you?

About the auto brightness. Honestly I don't know. It's too new for me also.

The overhead is a work queue (a timer) on the kernel that check light sensor every 0.4s and updates brightness every 2s. On the other hand, I hope that will be better (battery life), because of more frequent brightness changes and, I think, a little darker in low external light.

So, we will see. :)
[Galaxy S I9000 Android Development] DarkSorcerer:
Ok as well. Thanks for asking.

You can count on us to tell you how it will behave as well. ;)

Meanwhile, hope you enjoy the days off!

Thank you,
[Galaxy S I9000 Android Development] ZaneZam:
Hey stratosk thx for the new innovative version! Your autobrightness driver is working well and its reacting very good, better/faster than the stock one! Yeah, we will see how it impacts power consumption. Apropos power consumption, has anyone experienced that the so called "gingerbred charging bug" (i am on stock JVZ) is gone since semaphore version 2.2.0? On my last three charging cycles the phone behaves as it should, hmm observing further on, but that would be a nice side effect! ;-)
[Galaxy S I9000 Android Development] skodaslx:
So this is already done with version 2.3. right? No need for this script in 2.3. as it was in v2.2 ?
[Galaxy S I9000 Android Development] stratosk:
No, there is a difference.

In 2.3.0 version the sampling rate will change to from 10000 (original value) to original value * 4 = 40000 when the screen goes off (also the sampling_down_momentum = 0 and io_is_busy=0). When the screen goes on sampling rate will change back to 10000.

Please note that if you change the sampling rate with this script to 40000, when the script goes off the sampling rate will change to 40000 * 4 = 160000.
[Galaxy S I9000 Android Development] stratosk:
You welcome. I noticed some little conflicts with framework's changes to brightness but I think that generally works OK. Maybe some more tweaking on future versions will improve it. But, I have no brain for the rest of the night. :p I worked 2 full days on it. I think my vision is reduced. :D

About the gingerbread charging bug. I didn't do anything. So, I think that under the same circumstances you will have it again. IMO, (maybe I'm wrong because I never search for it) this is quite simple. You charge, the battery reach to a maximum (not battery's max for safety reason), charging stops but the phone don't go deep idle because it's connected to cable. Then the phone starts discharging. If you don't disconnect it early you will have the gingerbread bug.
[Galaxy S I9000 Android Development] skodaslx:
sampling rate to 40000 with the SemaphoreScripts_AddOn_Gov_Efficient.zip script

and sampling rate to 40000 with kernel version 2.3.0

so can we use the script also with 2.3.0 or not ?

I think my first post about this wasn't clear enough. Sorry for that.
[Galaxy S I9000 Android Development] stratosk:
Maybe my explanation was not clear enough. :)

With version 2.3.0 without the script:

screen on: sampling rate 10000

screen off: sampling rate 40000

With version 2.3.0 with HM.Carbide's script:

screen on: sampling rate 40000

screen off: sampling rate 160000

With the 2.3.0 version sampling rate is multiplied by 4 when screen goes off.

So, it's up to you if you want to use the script or not. I would prefer more snappy phone. But if you want the script you 'll have less overhead due to ondemand and less frequency transitions.
[Galaxy S I9000 Android Development] ZaneZam:
Yes you have exactly right analysed the charging bug :) i think you dont have to worry you've got enough brain left, hehe! The thing is that on the last three charges i let the phone longer connected to the cable as usual because i slept longer (yes i am also on vacation *g*) and it was on 100% battery after disconnect. Thats also strage, normaly it should drop to ~97% as you stated for safety and with the bug i got often about 85% after diconnecting charger. The only thing that i did was installing your christmas gift kernel 2.2.0 and i forgot to disable usb debugging (disabling should help to avoid the charging bug but actually it did not really, its more a rumor than a workaround!) and after that three times (!!) no bug. :eek:

I know you didn't do anything in this direction but maybe as i said it's a side effect, anyway i will let you know if this positive behaving stays or if the bug returns and i was chasing a ghost. ;)
[Galaxy S I9000 Android Development] pxrave:
no u cant use the script because stratosk use a multiplier 4

if u have problems contact me in german => pm
[Galaxy S I9000 Android Development] jackpham:
When Semaphore_kernel_JW1_2.2.0 for Captivate?
[Galaxy S I9000 Android Development] stratosk:
Maybe tomorrow version 2.3.0
[Galaxy S I9000 Android Development] krige:
I just tried to flash Semaphore JW1_2.3.0 over Semaphore JVZ_2.1.1 on a stock JW1. Odin reported the following errors:

<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

The phone won't turn on and shows a black screen with a white phone icon connected with a white computer icon through a dashed line with a yellow triangle and an exclamation mark over it.

What could I have done wrong and how can I fix that?
[Galaxy S I9000 Android Development] stratosk:
Repeat the flashing procedure.

Make sure that the small window showing the connection becomes yellow BEFORE start flashing. Do not check repartition.
[Galaxy S I9000 Android Development] darckengel:
I came back from ICS, and the new kernel works well.

Don't know if it's possible with GB stocks, but in ICS, charging the phone allows to enter into deep sleep status...
[Galaxy S I9000 Android Development] krige:
Wheew... it worked! I had already followed those steps on the first place, and tried once again but nothing. Then I rebooted the PC, tried again and it worked. Why was that?
[Galaxy S I9000 Android Development] stratosk:
It happens sometimes (Windows... :) )

Just be sure that your USB connection with your PC works fine (yellow window).
[Galaxy S I9000 Android Development] manjee:
Hey Stratosk, I think your way of implementing autobrightness is simply brilliant !

By sweeping the notification bar, it allows us to tweak the value around the desired brightness level. Thus I think the lowest value of your autobrightness should be as low as possible (maybe 5 or even 1?).

Edit: oops, I just realized that I'm wrong :-s the autobrightness seems to override the manual setting...

Maybe a variable brightness around the manually defined level would be interesting to explore ?

I may not be clear enough, what do you think of it ?

Btw, I find the 10 as min is a great choice 8)

Thank you for your great work.
[Galaxy S I9000 Android Development] s3icc0:
nice to see autobrightness is here :-) good work man .. have to try
[Galaxy S I9000 Android Development] stratosk:
Lowest value to 1 will be impossible to see. :) IMO 7 or 8 is the limit.

Adjusting manually the brightness will keep the setting IF the external light does not change AND the automatic adjustment was over.

As I said the brightness level will be adjusted immediately with big external light changes.

With small external light changes brightness will be adjusted 1 by 1 step. Finally it will be stabilized to a specific value and will not be adjusted to very small light changes. If you manually tweak the brightness at this point it will be kept until the next big light change.
[Galaxy S I9000 Android Development] darckengel:
Made some tests with changing brutally the exposition or more gradually, it works fine.

Altough, i found the lowest value too bright...

Maybe because i was for some days on another kernel (ics rom) which uses lower brightness values..
[Galaxy S I9000 Android Development] rmean:
Hi,

I'm not sure if this is a kernel issue.

If i turn on auto brightness, it works fine. It's dark here right now, and the screen is really dark too, which is great. But when i turn the screen off and then on again, it gets brighter than it was before.

Anyone can confirm? ;)

Regards

Edit: this is about semaphore auto brightness :)
[Galaxy S I9000 Android Development] rmean:
Delete please
[Galaxy S I9000 Android Development] Alexdream:
wifi problem after converting to EXT4

Hi,

I have in my samsung i9000 the 2.3.6 Rom Stock JPY and Semaphore_kernel_JVZ_2.1.1

I install the app ext4 manager 1.3 and after converting to EXT4 my phone have a issue with the WIFI, stays in obtaining ip address from...

I wanna go back to the RFS partition but I cant the app ext4 manager show me (CF-ROOT kernel was not detected. ext4 Manager May not function property) all options are in grayed.

Please Help
[Galaxy S I9000 Android Development] ramas123:
It seems that Semaphore autobrightness is broken when you go into browser. It becomes very bright in dark room. Too bright compared with samsung autobrightness options.

P.S. Fantastic kernel, well done!
[Galaxy S I9000 Android Development] fylim:
Doing more tests on Wifi Sleep Policy
[Galaxy S I9000 Android Development] Rebel2k:
That's because the stock browser has its own brightness settings and though you must lower the brightness settings to the minimum value in the menu > brightness item. Thus you will benefit of the new driver written by stratosk there too.

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] ramas123:
Ok, thanks, problem solved.
[Galaxy S I9000 Android Development] stoske:
I have a little problem with Semaphore autobrightness settings.

I use gamma setting like 53, 53, 47 and I get greenish display when brightness is on low.

I can adjust gamma settings to higher level, but then colors are washed out.

With default Samsung autobrightness, everything is fine.

Beamed from Dark Side
[Galaxy S I9000 Android Development] stratosk:
That's easy to change, but yesterday night that I was testing this I found this low enough.

Anyway, I think I can make the low level to change through a parameter.
[Galaxy S I9000 Android Development] ryuzaki_eru:
What is the charateristic of smartass governor module?
[Galaxy S I9000 Android Development] Galaid:
Great kernel.

Feature request please: enable swap support.

Thanks
[Galaxy S I9000 Android Development] stratosk:
Bigmem version JW1_2.3.0bm

- 353 MB available RAM (it breaks 720p video recording)
[Galaxy S I9000 Android Development] pantrif13:
Great kernel stratos! Thanks a lot! You made our phones better with each new release! Keep up the great work!
[Galaxy S I9000 Android Development] ~ Myzrael ~:
Hey stratosk i saw galaxian has 344mb. how is that possible? can you do that also in semaphore?
[Galaxy S I9000 Android Development] stratosk:
Hi,

Are you sure it doesn't break anything? When I made a change and went to 341MB. I thought that everything was OK. But then someone reported that a rare video format was not played correctly.

Maybe I will check this. Though it's a little bit difficult to search for changes in a tarball with sources.
[Galaxy S I9000 Android Development] ~ Myzrael ~:
No i don't know, i didn't try it, maybe you are right and something is broken (maybe something not so important). Anyway, in galaxian description there are no statements regarding broken features... :confused:
[Galaxy S I9000 Android Development] gsw5700:
Just testing auto brightness, seems OK, possibly less bright than standard, would it be possible to set brightness values via semaphore manager, eg, low, Med, high or just low and high, the lowest setting would be the same, but the brightness would be more on Med/ high settings. The screen does look a lot better when brighter, and I would use this as I don't struggle with battery life. Thanks again stratosk

Sent using TCP/IP
[Galaxy S I9000 Android Development] cdmackay:
My charging bug also seems to have disappeared in the last week.

No ROM change, kept up with latest Semaphore kernels. Apps updated of course.

So thanks very much anyway...
[Galaxy S I9000 Android Development] dherre65:
What's that?

@ Stratosk, did you ever try the 'lazy' CPU governor? I tried it on Glitch kernel with CM7. It should be more responsive than ondemand and less battery consuming. I still prefer smartassv2 above all though, as it feels waaaaay more snappy/responsive/smooth/etc.

Was just wondering if you knew anything about the lazy governor and what the essential differences are between the lazy and smartassv2.
[Galaxy S I9000 Android Development] pikachu01:
That's because io_is_busy flag is unset when screen is off. io_is_busy will increase battery usage (as it will scale the frequency pretty often).
[Galaxy S I9000 Android Development] dherre65:
Not trying to be rude, but who cares about 4mb?
[Galaxy S I9000 Android Development] ZaneZam:
And that seems to be a good thing! :) Got one more "positive" charge w/o discharge today after ~9 hours charging! Battery was again on 100% and did not drop under (not sure if THIS is really good but anyway *g*) I also checked the battery voltage to see if it is in 100% range and it was about 4200mv that's how it used to be on full charge on my phone. Will test further on with some other settings...
[Galaxy S I9000 Android Development] Nergla:
Just a little feedback. Installed 2.3.0 this morning and during the day I had one warm boot - if that is the correct term - screen is black and will not wake and can hear boot up sound then screen wakes but no pin code screen appears and all is then ok. Have had this before when on speedmod but not for some months whilst using semaphore. No buggy though and may only be unrelated glitch. Also I too noted 100% battery life remaining - normally 98% shows when disconnecting from charge - not complaining just reporting. Many thanks
[Galaxy S I9000 Android Development] ingineru:
According to first post:

"- Semaphore Auto brightness driver (enable through Semaphore Application - disable auto brightness from settings first, for best results set brightness to lowest value from settings)"

I can't find it in Semaphore app...

Also, starting with version 2.2.0 the kernel version is gone from "about phone"
[Galaxy S I9000 Android Development] darckengel:
It's just before the AddOn Tweaks menu, after "disale bootloop detection"
[Galaxy S I9000 Android Development] HiKsFiles:
Downloaded, flashed and testing 2.3.0 no-bm.

Will report back if anything goes wrong but if it's as stable as the previous versions, don't expect to hear back from me anytime soon. :D
[Galaxy S I9000 Android Development] ingineru:
Found the problem:

I flashed it using SGS kernel flasher,something is bugged in it because i was still on 2.2.

Solved it with Odin
[Galaxy S I9000 Android Development] ~ Myzrael ~:
If it's possible why not? Care for details makes this kernel the best one
[Galaxy S I9000 Android Development] DarknessWarrior:
Using semaphore's auto brightness but it seems a bit too dark sometimes. Sometimes the brightness goes below the min brightness on the settings and i can barely see the screen in complete darkness... :/

another thing, i keep getting FCs on the camera when i try the touch to focus...
[Galaxy S I9000 Android Development] Blondasisko:
In my opinion also it is too dark in darker environments, but in brighter it is OK.
[Galaxy S I9000 Android Development] stratosk:
I would agree with Myzrael. Many small tweaks could make the difference. But as I said it needs investigation that it does no break anything.

I have heard about lazy governor but I really don't know any details (or differences with smartass) about it.

But I think I will not add any other governors in the near future. I think we are OK, at the present, with ondemand, smartass and conservative.

I tried to make it a little bit darker than the stock one. I will try to do the lowest value parametric in next version.

@DarknessWarrior

I can't reproduce force closes in camera. Did you have this issue in previous versions?
[Galaxy S I9000 Android Development] chachi:
only aggravating issue I have left with my galaxy is that if I do not ensure "captivate keep alive" is running the damn handset shuts off when it sleeps the screen ...

only started for me about 6 wks ago when I went to the states and bought/used a tmobile usa sim for a few weeks, having now used a uk sim and my cyprus sim on and off the past few weeks it hasnt disappeared despite upgrading from jvt -> jvz with simplicity and updating kernel a few times now to 2.30bm
[Galaxy S I9000 Android Development] DarknessWarrior:
nope, but i'm not sure it isn't because of something else... i don't use the camera that often...

i've tried to reboot but no luck.

my settings are: 2.3.0, no OC/UV, ext4, smartassv2, SIO, chainfire's kernel scheduler, chainfire's VM dirtyness

ONE.PT v9.1 ROM, everything else is pretty much stock.