yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] stratosk:
max_br_threshold will be included in next version of Semaphore Manager app.

About the max lux. I changed the checking about the max value (was 3000 now 4000). It's supposed to scale slower to external brightness changes. I will check again.
[Galaxy S I9000 Android Development] :
Tunables (bright, medium, dark) are 3 differently scale of brightness, right? Or i'm wrong?
[Galaxy S I9000 Android Development] Opuz Klass:
Stratos,

Regarding Voodoo Sound, does it? :)

Thanks!
[Galaxy S I9000 Android Development] superkoal:
Semaphore supports voodoo sound, but voodoo sound does not enable you to change in-call volume if you talk about this feature.
[Galaxy S I9000 Android Development] rkaede:
i am amazed how stratos keep on updating this semaphore build.
[Galaxy S I9000 Android Development] Indian Devil:
Touchwake never works for me unless I Set it to 0ms. Anything over 0ms it just won't work. Can anyone please explain what I might be doing wrong.

Thanks

Using Slim latest build if that's relevant.
[Galaxy S I9000 Android Development] 7kartoon:
BRG v RGB kernel problem

[MENTION=3750240]stratosk[/MENTION]

Is this possible for this to be fixed?

Screencast records with inverted colors/
[Galaxy S I9000 Android Development] DerTeufel1980:
This got introduced by cm/pawitp switching to nexus s framebuffer. Pawitp is aware of it, and wanted to fix it since long time. I guess, if it is possible, it's not a simple task

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] 7kartoon:
Ok I understand. But could this be a app problem since with z-screen recorder colors are just fine and only with Screencast (which is better) happens?
[Galaxy S I9000 Android Development] DerTeufel1980:
Maybe I miss read your post. There is a bug, which makes the screen colors always look blue instead of the original color, on some devices.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] 7kartoon:
No you read just fine. The problem is only with screencast. The output video had some colors inverted. Other program z-screen record does not have this problem

Sent from my I9000 - GamerzRom v3

---------- Post added at 11:21 AM ---------- Previous post was at 10:31 AM ----------

@DrTeufel1980

DevilKernel is yours right? I like it very much.

But I cannot seem to find it. This is outdated.

Thank you very much for your work.
[Galaxy S I9000 Android Development] yavu:
@ stratosk

Could we switch between 2 Kernel settings/profiles? By a widget or tile? I would set one for normal usage and one for heavy usage. It would be great if I can switch quickly.
[Galaxy S I9000 Android Development] eejee:
You can try One Power Guard. Though with the intention of saving battery, it offers this kind of switching.

Verstuurd van mijn GT-P5100 met Tapatalk
[Galaxy S I9000 Android Development] yavu:
I want to switch between different profiles with different gouvernor, scheduler and oc on/off settings.
[Galaxy S I9000 Android Development] eejee:
Well then, have a look.

Verstuurd van mijn GT-P5100 met Tapatalk
[Galaxy S I9000 Android Development] tsatomas:
Indeed, this is a very good app, not only for battery buy for overall performance as well. Try it.
[Galaxy S I9000 Android Development] stratosk:
Soon on Google Play:

http://xdaforums.com/showpost.php?p=41226140&postcount=381
[Galaxy S I9000 Android Development] mik101:
Did the app update today break Semaphore Auto Brightness for anyone else?

On a positive note, the built in auto brightness controls are finally working correctly (up until now I had relied on SAB because the CM integrated auto brightness wasn't working at all). I prefer SAB because then the screen doesn't dim before it turns off. Anyone know how to turn that off with the built in brightness control?

Seems to happen on both my captivate on the unnofficial 23sc, as well as my girlfriends i9000 on 24s. We're both back to the built in brightness controls for now.

Im on today's nightly, the gfs phone is on the last nightly before RC1.
[Galaxy S I9000 Android Development] stratosk:
It seems fine here.

Could you please check that the notification light is enabled in ROM's settings.

Also, is the module loaded (lsmod command in terminal emulator)?
[Galaxy S I9000 Android Development] mik101:
Notification light as in backlight notifications? Yes that's enabled in the settings, and in the semaphore app I have BLN instead of CM LED enabed. That is working completely fine, as are my other settings in Semaphore.

lsmod returns

row_iosched 4560 8 - Live 0x00000000

bcmdhd 379900 0 - Live 0x00000000

That is with semaphore auto brightness both enabled and disabled in the semaphore app (2.7.0). (I'm not sure if you're looking to verify that something else shows up there, or if it responds to the query at all).
[Galaxy S I9000 Android Development] stratosk:
No, my mistake. I mean ROM's auto brightness.

You are right for some reason the module does not load from Semaphore Manager.

Thanks for catching this. I will check it.
[Galaxy S I9000 Android Development] javiast:
Same here

Thanks
[Galaxy S I9000 Android Development] Necromancer3:
Just updated Sem manager.

From first glance it looks fine.

max Brightness threshold works (used 1 as dummy value for testing)

But the screen does not dim any further with max lux 4000, and the screen brightness remains the same as with max brightness 3000
[Galaxy S I9000 Android Development] stratosk:
max_lux can be updated to 4000 just to make update to higher brightness values more 'difficult' as you proposed. The actual lux value from the sensor will remain 3000.

[MENTION=535343]all[/MENTION]

I fixed the module issues in Semaphore app. 2.7.1 will be available soon.

I'm sorry for the inconvenience.
[Galaxy S I9000 Android Development] Necromancer3:
I know.

With max lux set to 3000 i get x brightness

With max lux 4000 iam supposed to get y brightness value with

y < x

So as i set max brightness from 3000 to 4000 the screen should become darker, but it doesnt :/
[Galaxy S I9000 Android Development] stratosk:
Once more, I will check it again. :)

If you have time, please also check the code. Maybe, you can catch something there.
[Galaxy S I9000 Android Development] mik101:
Thanks for the amazingly fast update. The updated version of semaphore manager fixed it on both of our phones.

Once again Stratosk, you're the man!
[Galaxy S I9000 Android Development] MAQ7:
stratosk

Thank you for this great kernel.

Can you hack in call volume and include wipe battery stat in recovery?
[Galaxy S I9000 Android Development] stratosk:
I'm sorry. I dropped in-call volume hack. I think that it caused distortion.

About the wipe battery stat, koush dropped because he found it useless, and I totally agree
[Galaxy S I9000 Android Development] Necromancer3:
stratosk can you give me a link to the sema source?

the link on semaphore.gr is to a year old source
[Galaxy S I9000 Android Development] stratosk:
Please find it in OP.
[Galaxy S I9000 Android Development] Necromancer3:
code seems to be fine.

what does this do?

/* Apply low pass filter */
sa_info.update_br = ((sa_tuners.alpha * sa_info.update_br) +
(sa_tuners.beta * sa_info.old_br)) /
sa_tuners.norm;

maybe 4000 is not very distinct-able?

i doubt that because 2000 -> 3000 is noticeable. as its linear, 3000 -> 4000 should be noticeable as well.

maybe try

if (ret != 1 || input < 1 || input > (DRV_MAX_LUX*2 )) //instead of DRV_MAX_LUX + 1000

edit: looks like the change is too small to be noticeable.

with elixer2 i checked the lux, it reported ~80 lux.

with max_lux set to 2000

80*255/2000 = 10.2 = 10

with max_lux set to 3000

80*255/3000 = 6.8 = 6 (difference of 10-6 = 4)

with max_lux set to 4000

80*255/4000 = 5.1 = 5 (difference of 6-5 = 1)

with max_lux set to 6000 i would get

80*255/6000 = 3.4 = 3 (difference of 6-3 = 3)

maybe the incline is not low enough?

with max_lux 4000 the incline is only 75% lower then with max_lux 3000

with max_lux 6000 (DRV_MAX_LUX*2) the incline is 50% lower then with max_lux 3000
[Galaxy S I9000 Android Development] stratosk:
It's a low pass filter. For more smooth changes to brightness.

I'm not sure if Elixir reports the same scale of lux.

The difference is greater for larger values of lux. For example:

2000*255/3000 = 170

2000*255/4000 = 127.5

And if sensor get the max value (3000) the difference is 255 - 191.25. I think it's OK (?)
[Galaxy S I9000 Android Development] Necromancer3:
the question is what lux are we on mostly.

mostly im in buildings/cars so i don't get to 3000 lux.

and when im out, i'd set the max_brightness_threshold before 3000.

this needs to be determined by trial and error, but under 3000 lux i already won't see anything with ~200 brightness.

so somewhere ~2000 lux ill put my max_brightness_threshold, but until then, i want lower brightness.

so the effective brightness we are talking about is much lower then the max brightness, and so the current (4000) incline is barely noticeable. this is restricting.

a 6000 lux is only the maximum restriction, users can always use less.

with a restriction of 4000 i can't use more.
[Galaxy S I9000 Android Development] stratosk:
OK, next version as you wish. :)
[Galaxy S I9000 Android Development] RivalComp:
Then how could I set in-call _microphone_ volume? My phone is ok, but my sister's voice is distorted because it's too loud. Everybody is telling her they barely can understand what she says. She has the same model with the very same ROM, kernel and settings as mine. Under DSP manager there is no in-call microphone setting. With other apps like Skype, Viber the microphone works well. I've tried to find solution but no success. Any advice? Some service menu or something?
[Galaxy S I9000 Android Development] fishears:
Sounds like the problem lies with your Sister's voice rather than the ROM. An easy fix would be to ask her to stop shouting all the time :p

(Sorry, couldn't resist)

sent from somewhere..
[Galaxy S I9000 Android Development] mamoto66:
Bad,bad,bad,Fishears bad...
[Galaxy S I9000 Android Development] RivalComp:
Baaaad fishy... I also can't resist: http://www.youtube.com/watch?v=2_DrW067JmI :D

For the thread: I remember some hidden hell pits of the phone where I could set something like in-call mic sensitivity. No, it's not in the Voodoo app and I don't remember when and where. As ultimate solution I'll revert back to stock to see whether the problem persists or not. If not and flashing back Slim+Semaphore causes this issue I'll refer to this thread about it, ok? (In case if in-call volume is kernel related of course)
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
a nice comeback :)
[Galaxy S I9000 Android Development] Kordius:
sgs+ get 3.4 kernel ._.

why we not ? :c
[Galaxy S I9000 Android Development] slaid480:
An XDA rule:never ask for ETAs;

Devs know what is the best for our devices!
[Galaxy S I9000 Android Development] Starsream88:
Already discussed many times. Search the thread
[Galaxy S I9000 Android Development] Kordius:
I dont ask for etas ; pp
[Galaxy S I9000 Android Development] haseoxth:
Just for ask what will it bring to our device? Or only a version number？
[Galaxy S I9000 Android Development] superkoal:
Basically only a new numer and a LOT of work
[Galaxy S I9000 Android Development] jugster:
Why would you want such an old kernel? 3.9 is the latest, right?

Why aim for silver when you can have gold?

Signature? Signature!
[Galaxy S I9000 Android Development] AusMatt:
Why not use 3.10-rc1 ?
[Galaxy S I9000 Android Development] jugster:
Cmon, would you really consider not using the stable version? Mainline seems risky to me.

Signature? Signature!
[Galaxy S I9000 Android Development] gverma1:
On any 4.2.2 ROM and kernel combination, after 3-4 days without reboot, the phone becomes slow and available RAM drops to around 80mb from about 150mb. Games like Temple Run become stuttery. Is this not solvable? It seems proper housekeeping and garbage collection is not happening. One would say that over a period of time Linux is caching processes for faster response leading to low available RAM, but then why should games and normal UI lag? Any explanation from our esteemed devs? Also, any solution? Thanks.
[Galaxy S I9000 Android Development] Thunder22:
Dude. all you need is to go to aways jellybean rom xylon v. 2.3.3, older version on server or malchos new black beast. Then install this puppy and you should have no problem man. Just make sure to do all 3 wipes plus wipe system in recovery before instilling rom. Trust me , not kernel related this thing is solid.
[Galaxy S I9000 Android Development] stratosk:
As you already know Linux 3.10-rc1 released.

I'm happy because my small contribution is included there :)

https://git.kernel.org/cgit/linux/k...id=refs/tags/v3.10-rc1&qt=author&q=Stratos+Ka
[Galaxy S I9000 Android Development] Rebel2k:
Congrats sir stratosk !

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] ts1506:
Congratulations , and may you contribute lots to the community..
[Galaxy S I9000 Android Development] grinder777:
Noob Question! what is ETA?

tapatalked from lifetab p9516
[Galaxy S I9000 Android Development] jv.batista:
source: http://www.urbandictionary.com/define.php?term=eta
[Galaxy S I9000 Android Development] grinder777:
...??

tapatalked from lifetab p9516
[Galaxy S I9000 Android Development] slaid480:
Nice work dude!keep It Up!
[Galaxy S I9000 Android Development] zeal_007:
Congratulations...! Keep it up..!
[Galaxy S I9000 Android Development] Opuz Klass:
stratosk,

There are issues with devices with low/high mic gain which benefit a lot from in-call volume control. Please consider readd support for that in a way that don't degrade call quality for people who doesn't need that fix.

Thanks!
[Galaxy S I9000 Android Development] 7kartoon:
Sigxaritiria Strato. Kai eis anwtera.
[Galaxy S I9000 Android Development] eejee:
Install Greenify.

Verstuurd van mijn GT-P5100 met Tapatalk
[Galaxy S I9000 Android Development] 5aaled:
Congratulations stratosk, You deserve the best ;)
[Galaxy S I9000 Android Development] 7kartoon:
This won't help. There is memory leak which needs to be fixed. Hopefully soon from the developers
[Galaxy S I9000 Android Development] RivalComp:
In my case I had installed Greenify and set it up correctly. I disabled and freezed all unnecessary apps and services. My hungry and most used apps are DailyRoads Voyager and Waze. My dialer is RocketDial Pro, launcher is Nova Prime. I use Tasker to automatize things and Whatsapp for messaging. All other things are "greenified". All of my running services are fit in one screen in Application settings (including Google and system stuff).

After a fresh start everything is okay. I use the phone, starting and exiting apps, you know. And after one or two days all of these apps and services (including the launcher, Google services, Greenify, Tasker) are continuously restarting and kicking off each other. No, there are NO other running apps just what I can see after a fresh reboot. There is much free RAM (of course there isn't really free RAM because of caches and other things but you can see this free thing on the running apps screen). Phone is unusable for navigation, Waze quits continuously, I have to wait 10-15 seconds for the dialer, the whole system is a mess.

When I check app list, there are no running memory hogs, there IS free RAM at the bottom (100 megs for example). Then I try to long press the button on the recent screen to clear caches but it has no impact on this situation. After all I have to restart my phone and everything gets back to normal for a day... with the same usage.

I have the most clearly flashed ROM you can imagine.

So this memory leak (or how I call it) problem is real. If you use your phone and not just the dialer and contact list there is something wrong with Android.

Beside this thing this is the best ROM/kernel combo I ever had on this phone.

Edit: I know the limits of this phone and I don't run tons of community apps and other background services.
[Galaxy S I9000 Android Development] superkoal:
i experience this memory leak too, but the kernel thread is the wrong place, this is clearly rom related.
[Galaxy S I9000 Android Development] haseoxth:
Seems a little late here,congratulations! You are really a great developer :D
[Galaxy S I9000 Android Development] spambayes:
I can confirm this. Having used a variety of Roms with different kernels and tried almost every tweak available on XDA, some of which helped and some didn't, the phone invariably slows down over a few days' of usage. Only a reboot brings back the new, fresh feeling.
[Galaxy S I9000 Android Development] melinerunen:
Can you try clearing all recent used apps? (Long press home button...)

Some apps doesn't close. Ie Firefox.

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

There is not much help I can offer since, as you mentioned, there are hardware limitations for this device.

Nonetheless, I can offer you 2 things that I use and make the experience much better:

1. You said you are using tasker, I have a profile that checks every morning if the device is up for more than X amount of time (you can decide what your optimal time slot is) and in case the device exceeded this time, it make a reboot ("good" reboot, exiting all open tasks just like when you use the power menu) using the "Secure settings" tasker addon (https://play.google.com/store/apps/details?id=com.intangibleobject.securesettings.plugin&hl=en).

2. You really should try and use the whitelist feature Startosk implemented a couple of versions ago. Alongside with Superkoal app (http://xdaforums.com/showthread.php?p=40404319) it is a great tool to prevent from your navigation app (for example) from crashing all the time.

Hope you'll find this info useful ;)
[Galaxy S I9000 Android Development] spambayes:
I make sure to kill all recently-used apps from time to time using various means to delay the onset of lag and general slowdown. It doesn't make much of a difference. I suppose it ultimately boils down a hardware limitation (we are talking about a phone that's more than 3 generations old).
[Galaxy S I9000 Android Development] Necromancer3:
startosk is the brightness requires updated kernel to reach 6K max_lux?

i have updated sema manager and it looks like its ignoring max_lux values above 3K.

to test it i've set my max_lux from 3000 to 600 --> screen became more bright

set max_lux from 600 to 6000 --> screen brightness didn't change.

set it from 6000 to 3000 --> screen darkend.

?
[Galaxy S I9000 Android Development] ziporpor:
FYI,

Long pressing the home button gets you to a list of recently used apps, not all of the apps that appear there are still active.

Clearing this list does not mean that you close the apps that are still working in the background.
[Galaxy S I9000 Android Development] alb3rtt:
Clearing recent apps does NOT kill the apps running. Going into settings then apps then running and selecting the app you want to stop will kill it.
[Galaxy S I9000 Android Development] Rokostar:
Get the app grenefy its genious.
[Galaxy S I9000 Android Development] melinerunen:
FYI according to one of the recent chancellors in Firefox they tell that this is one way to close Firefox when they remove the close button from the menu key. Also if you are into one app and remove it from the list it will close. Try it :)

Perhaps it's a Rom feature. Idk. I'm using helly bean and it works pretty well. When the device gets slow I clean that list and everything comes to normal.

Sent from my GT-I9000B
[Galaxy S I9000 Android Development] alb3rtt:
Probably a placebo affect. It is simply a list of recent opened apps. It you want to kill/stop the apps, go into settings/apps/running and do it from there.

That's enough talk about this topic.
[Galaxy S I9000 Android Development] 99x:
In cm it does actually kill the app if it is process only and not a service. You can easily test it, for example on my S2, the malistatus app (shows current gpu speed) can be killed by swiping it away in recent apps.
[Galaxy S I9000 Android Development] melinerunen:
I see you still do not believe me so I recorded a little video.

http://www.youtube.com/watch?v=yTIi2gDG64w
[Galaxy S I9000 Android Development] eejee:
Ok. A simple solution for now would than be to let Tasker reboot every night on moments that you are vast sleep :)

Edit: be sure to make a nandroid backup beforehand. It tried it a few weeks ago and it got me in a bootloop. Tried it again just now with the same result.

Edit 2: found the cause: you have to specify an end time a well, otherwise tasker thinks that the reboot profile has to be executed because the start time has passed

Verstuurd van mijn GT-P5100 met Tapatalk
[Galaxy S I9000 Android Development] stratosk:
kernel needs update also.

Maybe tonight, if I'll find some free time.
[Galaxy S I9000 Android Development] ts1506:
Are you going to make any other changes in the upcoming one apart from the max_lux input and Linux kernel update?
[Galaxy S I9000 Android Development] androiduser44:
yes kernel can cook coffee and serve your breakfast and after that it goes working for you...

just wait for release and then read changelog :)
[Galaxy S I9000 Android Development] stratosk:
New version 2.9.25

- Linux kernel 3.0.78

- Enable again in-call volume settings

- Auto brightness: max_lux up to 6000
[Galaxy S I9000 Android Development] Rebel2k:
Brillant!

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] Kordius:
del
[Galaxy S I9000 Android Development] Opuz Klass:
In-call volume control

Thanks for bringing in-call volume control back, stratosk! :)
[Galaxy S I9000 Android Development] Christopher83:
Linaro GCC 4.7 and 4.8 toolchains

Hi Stratosk!

Some months ago (on December 2012) I started to build some customized Linaro GCC and Standard GCC toolchains optimized for Cortex-A8 cpu with NEON vfp technology support, suitable for kernel builds. I think that these toolchains could be used for your device too.

If you're interested, you can find more details and download links inside my thread:

[LINARO GCC] Cross Compiler Toolchains​

Here you can find also other toolchains built for generic Cortex-A cpu and configured with similar settings to those of the latest Linaro toolchains...

The latest toolchains released are (at the moment):

- Linaro GCC 4.8.1-2013.04 Toolchains

- Linaro GCC 4.7.3-2013.04 Toolchains

- Linaro GCC 4.6.4-2013.04 Toolchains

Thanks you for your amazing work!
[Galaxy S I9000 Android Development] androiduser44:
where can i find in call volume options? in semaphore manager i cant find it

im using slim bean v5
[Galaxy S I9000 Android Development] Neel.I:
Not sure,but should be under Advanced menu,in settings
[Galaxy S I9000 Android Development] androiduser44:
thanks

it is under advanced settings :)
[Galaxy S I9000 Android Development] Indian Devil:
Unable to use touch wake unless I set it to 0ms. More than 0ms it won't wake the screen.

Can anyone explain what I might be doing wrong.

Regards
[Galaxy S I9000 Android Development] karol1981:
Stratosk how i must set tunables in autobrightnes ,becouse my phone is't get full brightness in full sun?
[Galaxy S I9000 Android Development] rmsinaga:
Hi stratosk, thanks for the update.

Is there any reason why in-call volume setting distorts the audio quality? Especially when turning on the speaker phone.

Thank you.
[Galaxy S I9000 Android Development] superkoal:
Yes there s a reason, this is exactly why stratosk dropped this feature a while ago.

You can't amplify a signal as much as you want.

If it's digitally amplified it will clip with the maximum signal value, if it's analog amplified it will clip with max amplitude.
[Galaxy S I9000 Android Development] ofer6483:
Just reduce the in-call speaker volume to a normal value.. Let's say 20.
[Galaxy S I9000 Android Development] malcho:
Most of users ask for this to be back.So we can't complain now
[Galaxy S I9000 Android Development] slaid480:
Yes that's right!there is no way to keep asking the OP to remove and add this feature many times!!