yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] mindphaser2k9:
Do you mean you just increased it in system settings and hear the difference? Or do you use init.d script?

I've tried both, set values to 3 (this should be very-very loud) but I didn't hear that in-call volume was increased. I use Captivate and AOKP JB ROM, maybe this is the case?
[Galaxy S I9000 Android Development] stratosk:
Yes, that's what I mean.

I usually call my provider's automated services, put the phone call in background, open the in-call settings and I change them.

I can hear the difference during call.
[Galaxy S I9000 Android Development] mindphaser2k9:
Yeah, this way it works!

But somehow it is not persisted for me. I mean I tried to call my provider's automated services, put the phone call in background, open the in-call settings and increased them, I hear that volume increased. So far so good. But next time I call, I hear the volume is default again nevertheless settings still show maximum value of 3. Also for me all adjustors can increase/decrease ear volume, I mean I change Bluetooth volume and hear that earpiece volume is changed though I don't use BT (though this is not a problem for me but maybe this can help to figure out what happens).

Can you please check if volume persists for you (I mean not settings but what you hear)? And if everything is ok for you, what would you suggest me to check?
[Galaxy S I9000 Android Development] sucre213:
I wonder which cpu governor consumes least battery while listening music?I suppose not interactive.. Anyone give me some advice? thanks in advance
[Galaxy S I9000 Android Development] Starsream88:
Read this http://xdaforums.com/showthread.php?t=1369817

It's interesting :good:
[Galaxy S I9000 Android Development] sucre213:
I have read this and i understand each governor , but still confused which governor is best for music,

i tried on demand and yes,most of time is at minimum, but it kept at 800 MHZ for some time too ,while using smartass2, most of time it use 200 or 400MHZ
[Galaxy S I9000 Android Development] ryuzaki_eru:
Is deep idle working fine now?

Inviato dal mio GT-I9000 con Tapatalk 2
[Galaxy S I9000 Android Development] deeppans:
Keep your good work

Stratosk,

Using your kernel from ICS, damn good. On AOKP build 5 OCed 110% doing great.

A (very) small donation from me. (Yet to get this month's my paycheck )

Confirmation number: 97069611E08098604.

Keep your good work.
[Galaxy S I9000 Android Development] johnsin5393:
How can I get 390/391mb ram in semaphore without break 720p? Thank you
[Galaxy S I9000 Android Development] sucre213:
390 won't break 720p recording

only 404 ram with bigmen patch will break the recording
[Galaxy S I9000 Android Development] mindphaser2k9:
If 390mb ram breaks 720p for you, flash this patch http://xdaforums.com/showpost.php?p=30619870&postcount=755
[Galaxy S I9000 Android Development] roshan2989:
just flash 2.4.4s in CM10(22/10)..and the sound was to slow...even using vodoo sound..is there any fix...?
[Galaxy S I9000 Android Development] elandune:
great work!!!

but.....................................what an ugly logo!! :D
[Galaxy S I9000 Android Development] johnsin5393:
which semaphore version can get 390mb actually?
[Galaxy S I9000 Android Development] test123456789012:
Read this posting on deep idle: Klick

and this one about battery consumption of the various governors: Klack
[Galaxy S I9000 Android Development] ugoms:
S version
[Galaxy S I9000 Android Development] sucre213:
Just enable bigmen in 2.4.4

2.4.4s is for cm10 with bigmen patch

or slimbean
[Galaxy S I9000 Android Development] BoBoGrEy:
Hello guys...

I don't know if this has already been answered but in last Semaphore versions I lost vibration on Viber messages...

I tried in SlimBean, CM10 and Mackay with 2.3.0/2.4.0/2.4.4 and the sympton is the same...If I use other kernel it works...

Do u guys have the same problem?? Any solution??

Thanks in advance..,
[Galaxy S I9000 Android Development] ryuzaki_eru:
No one knows?

Inviato dal mio GT-I9000 con Tapatalk 2
[Galaxy S I9000 Android Development] sucre213:
Mine is very strange

When i just turn on the phone ,then leave it there for a moment, it shows some value in stats

However,the stats number never increase anymore

even after a whole night
[Galaxy S I9000 Android Development] mindphaser2k9:
DeepIdle shouldn't work when a phone sleeps. It should work when the phone is active but screen is off, for instance when you listen music.
[Galaxy S I9000 Android Development] adytum:
Not exactly sure what you mean, deep idle has always worked perfectly for me, and still does.

Sent from horseback.
[Galaxy S I9000 Android Development] ryuzaki_eru:
I mean that many people had problem with deep idle.

Inviato dal mio GT-I9000 con Tapatalk 2
[Galaxy S I9000 Android Development] stratosk:
You are right. I can confirm that something's wrong there.

I will check it. Though, I'm too lazy to fix it, if it is not something obvious... :)

Thanks so much, my friend! Don't worry, it's not "(very) small". Believe me, it's more than enough and much appreciated!

Thanks, but I love the new logo. I like the fact that It's symbolic and minimal.

Yes, some people still have (and will have) issues with deep idle. Just try it, if you will have problem just disable it.
[Galaxy S I9000 Android Development] mindphaser2k9:
Thanks in advance I will cross my fingers in hope that you will make something about that :fingers-crossed:
[Galaxy S I9000 Android Development] ryuzaki_eru:
How come some people has problems and others does not?

For me deep idle crash sms app and delete all my messages.

Inviato dal mio GT-I9000 con Tapatalk 2
[Galaxy S I9000 Android Development] przemek211:
few questions about Semaphore.

First of all. Really great development, I appreciate :)

However, it's a pity that kernel doesn't support two-way call recording (semaphore could be still the first for I9000 :) )

Moreover, is there any explanation about features? I'm sorry, but "TUN", "CIFS" don't say me anything. Actually, most of features tells me nothing. CPU's options are probably not for me, but should I use the scheduler? What about WiFi PM Fast? Fast charge (why on own risk and how it is better?)

And one other. On the Semaphore's webpage (FAQ section) we can still read about voodoo color and green flash small issue. I think it was much better than stocks quality. Why it is not longer supported?
[Galaxy S I9000 Android Development] Jimmy_X:
After couple of days testing. Yes deep idle is working just fine.
[Galaxy S I9000 Android Development] stratosk:
Deep idle is a feature that was ported from GB kernel and even Samsung didn't use it (or use it on latests version - I can't recall, I have to check this). So, it's somehow incomplete or buggy? There are many reports from SODs (device don't recover from deep idle).

I don't know why it works for some people and not for other.

Anyway, it's the first report I read in this forum that deep idle make an app crash. Please don't use it, if it causes issues for you.

Thanks for your comments.

I'm sorry, not in my plans to implement support for 2-way call recording.

About your question about the features: I admit that many of them are undocumented in the site (or the documentation is poor or outdated). I do my best to document them, but as I always say my free time is limited.

I always prefer development from writing documentation (although, I try for it). No offence at all, but I believe that when you flash a custom kernel in your device, maybe you should put some effort to search about the different features that it offers, and experiment with them. There is plenty of information in this thread and this forum.

Anyway, thanks for your feedback, in my plans to write a documention about the features.

For TUN and CIFS please read this http://www.semaphore.gr/how-to/use-modules-and-scripts

About different schedulers, you can safely experiment to find the most suitable for you (or leave the default one)

WiFi PM_FAST: WiFi driver have 2 different modes of operation. PM_MAX (saves battery) and PM_FAST (better performance). When the screen goes off PM_MAX is used. When screen on PM_FAST is used. You may select the PM_FAST option in Semaphore Manager if you want to have PM_FAST on both cases.

Fast charge makes the device to pull max current from USB and it charges faster. I thought that it might be risky, thus the warning. Nobody reported issues so far. Please note that selecting this option does not enable the feature itself. It just enable support for fast charge. You need to enable explicitly from your ROM settings (or a widget).

Finally, I was never fun of Voodoo Color (and colors generally :) ). CM colors are fine for me, so I never implemented VC in ICS and JB kernels.
[Galaxy S I9000 Android Development] ZioGTS:
Stratosk is amazing. He just wrote a great guide for his kernel in a single post, and still says sorry because his kernel lacks documentation. Isn't this more that enough? Most devs will never write half as much and still be convinced they provided all the details... Thanks Strat! :thumbup:
[Galaxy S I9000 Android Development] przemek211:
Thanks for your reply @stratosk

2WCR is important feature for many people, e.g. in business contacts. I'm just curious why you are not going to implement this, but obviously it's your decision.

You are right that people who flashes kernels shouldn't have a problems with find these informations. However when I was looking I just got lists of feature or advanced questions, not simple explanation. My advice is just simple comment in Manager (like about WiFi PM here) or even in the first post of that topic.
[Galaxy S I9000 Android Development] ryuzaki_eru:
Maybe depends on ROM? BTW i can be the first user on this forum, but in another places there are peoples with deep idle problem.

Maybe the crash is caused from deep idle because i have almost 9.000sms. I don't know if other users have a lot of messages like me.

Inviato dal mio GT-I9000 con Tapatalk 2
[Galaxy S I9000 Android Development] superkoal:
+1

I love it too :)
[Galaxy S I9000 Android Development] Ramanjit81:
Great work Stratosk.

Hello Stratosk.

I completely agree with other posters that you very helpful indeed. I do not intend misuing your liberty, but may I suggest that you put the above info in the OP and or your website so these questions are not asked of you again.

May be it will save some of your time.

Thanks once again for the brilliant kernel and even better support.
[Galaxy S I9000 Android Development] Helloworld294:
You should flash via Odin froyo stock with repartition ticked

Sent from the beast that ate my sisters iPhone 4S.
[Galaxy S I9000 Android Development] johnsin5393:
Hi, stratosk. I thought the mms app crashed and get messages deleted may not related to kernel, cuz this issue had been happened and get reported by some other Samsung mobile users in my country and all over the world. Most of them suppected this issue may related to the ussd get hack on Samsung mobiles.
[Galaxy S I9000 Android Development] diddsen:
@stratosk

you wrote that deep idle is ported from gb... so what concretely does this or shoud do?
[Galaxy S I9000 Android Development] snapper.fishes:
I just noticed that the minimum clock speed is locked to 240 MHz if I don't use the additional option in semaphore manager app. Why does this happen? I am using 120% live OC and deep idle.
[Galaxy S I9000 Android Development] test123456789012:
On JB the clock is locked at 200 as long as the GPU is aktive, read: as long as the screen is on. Should go down when you turn off the screen.

Check with CPUspy.

Regards

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] Bejda:
Check deep idle guide and faq in OP ;)
[Galaxy S I9000 Android Development] stratosk:
Actually, my phone doesn't seem to have this issue. There is a link that you can check it:

http://securitywatch.pcmag.com/none/303097-dirty-ussd-hack-wipes-samsung-phones-is-yours-vulnerable

Anyway, this hack wipe your phone and not only mms app. I think the issue maybe in the huge database with > 9000 sms.
[Galaxy S I9000 Android Development] ryuzaki_eru:
In fact i have almost 9000 sms.
[Galaxy S I9000 Android Development] sjod8998:
It's over 9000 smssssss !!!!....

sorry, I could not resist ... :o
[Galaxy S I9000 Android Development] johnsin5393:
I've no idea with this actually but those who get sms wipe & lost problem I don't get their notice have lot sms in phone storage.
[Galaxy S I9000 Android Development] Malkemid:
can anybody write down a complete and centralized guide for kernel? such as the functionality of every option...or some advice to use the kernel...it would be very useful and there is no need to ask more and more questions
[Galaxy S I9000 Android Development] stratosk:
I just finished a first version. I will try to enrich this.

http://www.semaphore.gr/how-to/use-semaphore-jb
[Galaxy S I9000 Android Development] sucre213:
According to what Stratosk said

fast charge is not enabled when i toggle it in kernel manager?

So how to actually enable it ?

Is there an app or something?:p:confused:
[Galaxy S I9000 Android Development] Michel38280:
Tanks a lot for those useful informations :good:
[Galaxy S I9000 Android Development] hertzschi:
In settings, rom control,toggle buttons just add fast charge and you get the toggle in the notification area ;)
[Galaxy S I9000 Android Development] michal04.90:
but this is about AOKP, and how about cm10? does it support fast charge?
[Galaxy S I9000 Android Development] Starsream88:
Hi stratos, i have some questions please :)

I'm using interactive governor and im OC to 120%, can i set hi speed frequency of interactive governor to 1200000 instead of default value (800000) ?

I think it will improve performance cause my max cpu frequency is 1200Mhz

Thanks
[Galaxy S I9000 Android Development] jonnyb16:
awesome writeup strastosk, thanks alot!
[Galaxy S I9000 Android Development] stratosk:
For more aggressive governor, you may try it. Else, set it to 960000 (because you OC 120%).
[Galaxy S I9000 Android Development] ugoms:
Awesome job stratosk:thumbup:
[Galaxy S I9000 Android Development] RlndVt:
Stratosk, please reconsider swap. I love your kernel but have come to find that using a tiny bit of swap with the CM10 kernel gives me such a smoother experience.

It would be amazing if you would support this!
[Galaxy S I9000 Android Development] test123456789012:
SOD

Hi Stratosk,

I think I had a SOD today, or maybe the phone was simply off. Kmsg is attached. I OC'ed to 120 when it happened, tuned it down to 114 now. No DI, smartassV2 and no modules loaded. It continuously writes something about bluetooth, maybe it's related.. Maybe you can take a look at it.

kind regards!

EDIT: I'm on 2.4.4s :)
[Galaxy S I9000 Android Development] mindphaser2k9:
I have tried to use swap being on Devil kernel several times and can say that my experience is ambiguous, sometimes it causes huge lags (and zram too).

Currently a memory management in Semaphore is about perfect, much better than on last versions of Devil, and I disagree to have swap if it makes it worse.
[Galaxy S I9000 Android Development] Zeduaz:
Stratosk please I have a one small question - i use MIUI latest build and with Semaphore kernel 2.4.x dont work any video playback on any different players or dpi's (480,720 - i dont use bigmem). On stock kernel of this rom there is no problem with playback. Do You have any idea where is the problem? Thanks a lot!
[Galaxy S I9000 Android Development] RlndVt:
Devil kernel is a lot slower than Semaphore, so if you would want to compare, you would need to compare between Devil with and Devil without. Using the CM10 kernel which, in my experience, is faster than Devil, swap has helped me a lot (compared to semaphore).
[Galaxy S I9000 Android Development] stratosk:
I'm sorry, but I don't think so.

Please allow me to disagree about smoothness. Swap was not made to make a system smoother. Swap was made to give the opportunity to a RAM demanding application to be able to run on a system with limited amount of RAM.

For example suppose that your system have available RAM 200MB. If you want to run an app which demands 250MB or RAM will be impossible to run.

Also is used to have many apps running concurrently in your system. Then the kernel will move pages of memory from RAM to storage. This step demands an I/O operation. I/O operation, for example a copy to SD, are always much slower than RAM operations.

It IS impossible to have smoother experience due to swap.

One more example, your PC (Windows or Linux or Mac) uses swap. Try to open as many applications as possible watching the available RAM.

You will see that once the available RAM will be limited the system will lag as hell. At this point your OS performs swapping.

The only gain is that you can have multiple applications running at the same time. This is very nice feature in my PC, but I don't need it on my phone. What is the point to have 10-15 apps opened in background?

Hi, I just check the kmsg. Unfortunately, I don't know what happened. As you said maybe it's related to BT. But, just to be on the safe side try to use LiveOC 114 to check this.
[Galaxy S I9000 Android Development] test123456789012:
Okay, I will see what happens. Thank you! Another user wrote that it doesn't matter how much you OC but rather the steps would be important. Can you confirm that 114 is a safe bet? (Knowing that every phone is different)
[Galaxy S I9000 Android Development] HaTeNL:
But starting apps from /data is slower then part ram and part emmc. I feel it too, swap helps a lot in smoothness.
[Galaxy S I9000 Android Development] RlndVt:
Thank you for taking the time to respond but please read my rebuttal:

Firstly I'm not going to argue the 10-15 apps part because I feel that that is too fickle and I partially agree.

However I would like to mention that pre-swap, I could not listen to music (poweramp), browse the web (chrome) and switch back to my launcher(SSLauncher), without one of them being unloaded from RAM. Now that I use swap, I can smoothly exit my browser, check some widgets on my launcher, send a whatsapp, change my music, and then go back to chrome to find my webpage still fully loaded!

Secondly, you are right, loading from RAM is always faster than from any other location. But applications naturally get unloaded from RAM and then need to loaded, an IO from /data. With swap however, the app is still active, and gets awoken from emmc and /data simultaneously which is faster than solely from /data. (Especially with a quality SD-card.) Also the loading from emmc is a smaller IO operation than starting the application from /data again.

Finally, it's not a forced option, but a choice. One many would love to have.
[Galaxy S I9000 Android Development] stratosk:
Are we talking about smoothness or about how fast an app is opened? Anyway, I'm not pretty sure that an app will load faster in your example.

Suppose this situation: phone has available 20MB and you need to open an app that _uses_ 40MB of RAM (it doesn't mean that the app size will be 40MB in storage). Also, suppose that in case of using swap half of the reserved memory is still in RAM and half is on swawp. You start the app.

1) the phone does not use swap.

The system will kill 1 or more apps to free RAM and then it will start the app. The app will reserve 40MB of RAM. Killing apps is fast. Kernel just marks pages of RAM as unused. Memory reservation is also fast.

2) Phone does use swap.

The system will search for memory pages (that are reserved) and are used from apps that are not critical at this time. It will find memory pages of 20MB and it will copy (write) them to SD. Remember writing is always slower that reading. Then it will read 20MB of data from SD and place it in RAM.

The only gain in 2nd case is that the app is already initialized. If app is doing a lot of staff when it first runs, this will be omitted.
[Galaxy S I9000 Android Development] pxrave:
but you can simply activate this function from cm source

so give the users the opportunity to enable swap

....i agree with statosk that swap can produce some more lagg but its very annoying that some app's get closed if you only write a message or other light ram stuff e.g. listen to music or browse at the web...

swap prevent our low ram phone to close that app's

for exaple i have 8gb ram on win

but win use about 1gb for swap because all app's use the swap file (normal behaviour)

if you use linux it is the same ;)
[Galaxy S I9000 Android Development] mindphaser2k9:
I use 108 because higher values cause reboots with my CPU/GPU. Maybe 114 is safe for you but it is not guaranteed.
[Galaxy S I9000 Android Development] test123456789012:
Guys, it's his kernel and all that he's done so far was pretty good, wouldn't you agree? If you want something like swap, zram etc. you can always go for devil. But why would devil be slower, considering all those shiny options? maybe bloat?

If one must enable something like swap, then rather go for zram, or, this I would find very cool, ksm.
[Galaxy S I9000 Android Development] HaTeNL:
So it's just a matter of which you prefer.. I prefer fast switching between apps (so apps which are already initialized); which is multitasking.

I don't really feel a difference between opening 'new' apps, nor with closing them, so I think it's a win for using swap :)

I don't know how hard it is to implement swap, or if there are disadvantages when it's supported, but disabled. It's up to you to implement it, for how I see it, it's better to have it supported and let people decide to use it.

I have spoken.

Ofcourse I also agree with the guy above me ;) Devil is slow, because of the bloat. I just thing swap is not one of them, because it works really good on stock CM10 kernel (and Mackey) and does not slow it down. I don't agree in preferring zram.
[Galaxy S I9000 Android Development] stratosk:
I use 114, since I implemented LiveOC in Semaphore. Never use other value and never had issues (in my phone with my usage) of course.

Implementation of swap is very very easy. This is the change in kernel configuration:

-CONFIG_SWAP=n

+CONFIG_SWAP=y

I think the majority of people don't really need this feature. I believe Android LMK does it's job.

As you said, I could just enable it. I could just implement different schedulers and governors. But, I just want a minimal kernel. I spent many days (and do this again and again) to remove unnecessary features from kernel configuration. Why Linux uses this amazing configuration system? It could just include every feature in one huge kernel. One have to find the optimal configuration according to his needs.
[Galaxy S I9000 Android Development] test123456789012:
Speaking of features.. SlimBean has two options under performance/kernel setting that seem to work with semaphore: KSM and zram. Is that true? It seems that both settings give me more free RAM than without.
[Galaxy S I9000 Android Development] stratosk:
KSM and ZRAM are disabled in Semaphore.

I don't know if Slim team enabled these features. They build inline Semaphore in their last version.
[Galaxy S I9000 Android Development] test123456789012:
Thanks for the quick reply! May I ask why KSM is disabled? Seems like a pretty intelligent way to conserve RAM. Or does it use too many CPU cycles?
[Galaxy S I9000 Android Development] stratosk:
I would say that we will start a new cycle in our discussion. :)

All these methods, KSM, ZRAM, Swap are intelligent ways to conserve RAM. Each method from a different angle.

I don't say they are crap. They are made from genius people that contribute to Linux kernel. And I fully trust each method.

But, I will say it once more, I want minimal kernel. I prefer to run 1-2 less apps concurrently from having one more running kernel daemon eating some CPU resources.

For months we are discussing that we want butter JB, smoothness, fast system, battery efficiency, we are changing partition layout and we are trying to extend SGS life. IMHO, we don't need these features on our old device.

If I will realize that I need these features to daily run my SGS, I will stop Semaphore for SGS and change device immediately. :)