yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] yahyoh:
@stratosk may i ask noob question why u removed normal OC :) , i just noticed after selecting 1.2 oc my device reboot it self hmm then i opend nstool and found 120 live oc :laugh::laugh: i just used 1.1 for now

btw everything running blazing fast with 2.0.5 on latest cm10 nightly :highfive:

---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------

fastergps is way better u can choose ur region :cool:
[Galaxy S I9000 Android Development] stratosk:
I didn't remove it. I've never used it since I first build ICS kernel.

I just found it more elegant solution for OC.

I also have reboots using 120%. I always use 114% with absolutely no issues. And IMHO it's the same (maybe a little bit faster) that normal OC to 1200 because of bus OC.
[Galaxy S I9000 Android Development] yahyoh:
yep live oc faster than normal oc but i think with higher live oc like 120 voltages need to rise a bit or maybe the device can't take that much of live oc idk , on normal oc i can use 1.4 without reboot but i don't want to fry my cpu :D:D

ot : i was walking on nexus s forums and i saw Trinity kernel version that have 240 bus speed ( 140 live oc O_O ) with 1100 normal oc can any device take that much of ocing :D
[Galaxy S I9000 Android Development] pbecks1963:
@stratosk

I am planning to try (once more) to move from ics to cm10. Last time (after i flashed semahore 2.05) things didn't work out so well. (see previoius posts)

Does 2.05 have "bootloop-detection" ? (like in your ICS-kernels) If so, how long should i (how many bootloops) wait before the detection kicks in?
[Galaxy S I9000 Android Development] stratosk:
Yes, it has bootloop detection. Unfortunately, there is no guarantee that it will work always.
[Galaxy S I9000 Android Development] jacobuscuracao:
nothing. I even did a clean install of Cm10 with factory reset, then load 2.0.5

maybe it's the tropical wave that's passing over (no heavy weather yet, but we do have more wind and it's dark-ish)
[Galaxy S I9000 Android Development] stratosk:
I never used or implement OC to higher values than 1200. You maybe right about voltages.

Anyway, I feel that LiveOC 1140 is pretty good and safe.
[Galaxy S I9000 Android Development] jv.batista:
Just installed cm10 and semaphore 2.0.5 and the gps works fine. just got a fix in 17s and less than 1 min to get 10 meters accuracy..
[Galaxy S I9000 Android Development] christiano88:
240 bus speed = 120% live OC, not 140 (stock is 200, 40 mhz more means 120%).
[Galaxy S I9000 Android Development] yahyoh:
hmm thanks :cyclops:
[Galaxy S I9000 Android Development] ImSo3K:
2.0.5 supports CM10 818?
[Galaxy S I9000 Android Development] stratosk:
Yes, it does.
[Galaxy S I9000 Android Development] thestudent00:
yes

edti: to slow ^^. I tried semaphore now since yeterday for the firt time. Its really fast and no issues so far. Will see i i will stay or not. I think didle saved me today a lot of batterylife. I heared msic for more than 5 hours. And its gone from 60% to 43%. Thats nice. I hear a llot of music with my old sgs and with latest stock kernel it doesnt last so long. Thank stratosk for this amazing work.
[Galaxy S I9000 Android Development] jst_tsj:
Could someone suggest me a fastcharge widget compatible with semaphore kernel?
[Galaxy S I9000 Android Development] stratosk:
New version 2.0.6

- CWM: upstream sync (now with 'mount USB storage', mounts both internel and external SD) thanks to Koush

- CWM: fixed clearing dalvik-cache

- upstream sync (thanks to pawitp, jt1134)

- Fixed showing charging animation

- mount /system with barrier=0

WORKS ONLY ON CM10 BUILD 20120817 OR LATER
[Galaxy S I9000 Android Development] albertobom:
Thank you :)
[Galaxy S I9000 Android Development] pmos69:
If you went with barrier=0, you might as well go with nobh also for /system.

Barrier=0 is already one step up in the danger zone, compared to the relatively safe writeback mode. nobh is about as safe/unsafe as barrier=0 on battery backed devices like these phones.
[Galaxy S I9000 Android Development] purpleraintoxicity:
Yeah, what he said :p
[Galaxy S I9000 Android Development] dashqa:
Please tell me the difference between barrier=0 and writeback?
[Galaxy S I9000 Android Development] bhu1:
Re: [KERNEL] Semaphore JB 2.9.15

Stratosk, can you add the feature where we can double tap screen to wake it? Many Galaxy nexus kernels have this feature. Would be really helpful.
[Galaxy S I9000 Android Development] Midomad:
Re: [KERNEL] Semaphore JB 2.9.15

You mean touchwake?

It's already supported by semaphore kernel!

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] stratosk:
I think he doesn't mean touch wake. I will try to check it.
[Galaxy S I9000 Android Development] Rokostar:
AW: [KERNEL] Semaphore JB 2.9.15

never heared about this features but it sounds nice and Stratosk is always good for a surprice.
[Galaxy S I9000 Android Development] jugster:
Re: [KERNEL] Semaphore JB 2.9.15

I think he means what is known as sweep2wake as implemented by bricked kernel or pgm mod for galaxy nexus. Basically it let's you perform certain actions while your screen is shut down but the digitizer is active. Apparently the digitizer on some devices can still be on while the rest of the device is in deep sleep which means not much battery is lost. What is gained though is the ability to swipe or double tap screen to wake device up.

I think, particularly on old devices where some buttons are beginning to fail, this is a sweet feature to have.

The jury is still out on if it is at all possible on this device though.

Signature? Signature!
[Galaxy S I9000 Android Development] ts1506:
Re: [KERNEL] Semaphore JB 2.9.15

I don't think sgs can go into sleep with the digitizer on , because in touch wake a wakelock is used for the specified time by the kernel and that is what keeps the digitizer awake. If you increase the timer to say 4 hours or so, it could potentially act as the feature described but battery drain would be immense.

This was actually discussed a few months back as far as I remember.
[Galaxy S I9000 Android Development] grinder777:
AW: [KERNEL] Semaphore JB 2.9.15

We have! It is called touchwake... to find in semaphore manager!

md p9516 - root -waiting for cwm -- thnx2all
[Galaxy S I9000 Android Development] Rokostar:
AW: [KERNEL] Semaphore JB 2.9.15

hey bro just read the last posts from the members then you know that im not talking about touchwake!!!!!!!!!!!!!!!!!!!!!!!!!
[Galaxy S I9000 Android Development] jugster:
Re: [KERNEL] Semaphore JB 2.9.15

Yes, but sweep2wake is an entirely different beast than touch wake. Touch wake may be implemented with wake locks because the time frame it is used in is pretty small. But for sweep2wake you need something more clever. It can potentially be hours or more until you unlock the device. I have followed this forum pretty closely and I have seen no reports of what you are talking about. Could you please point me to them if they exist? You might still be right though. I just don't hope so :)

Signature? Signature!
[Galaxy S I9000 Android Development] ts1506:
I was talking about our phone. SGS cant enter deep sleep when the digitizer is active. In GNex , the digitizer didnt affect sleep.

But I hope stratosk will think up something clever
[Galaxy S I9000 Android Development] jugster:
Re: [KERNEL] Semaphore JB 2.9.15

Sorry to ask again, but do you _know_ that or do you know that because of how touch wake is implemented?

Is there a piece of code or a document or something you can convince me with (preferably not related to touch wake) that makes that a fact.

I'm pretty sure that the other devices that this works for wasn't intended to have this working in the first place.

Signature? Signature!
[Galaxy S I9000 Android Development] Rokostar:
AW: [KERNEL] Semaphore JB 2.9.15

Guys do you ever try the app proximity screen off ? This app has the same funktion like these new feature you talk but it works over the distance sensor. I use the app sometimes. Stratosk maybe you can implement that feature in the semaphore kernel app ?
[Galaxy S I9000 Android Development] ts1506:
Sorry , no such definite proof. But a certain feature was discussed some time ago here , in which a feature more or less like permanent touchwake was discussed. Some guy put the refernce to the Gnex's digitizer running while device is asleep , and here stratosk said that to keep SGS's digitizer awake , a wakelock is a must.
[Galaxy S I9000 Android Development] thETImo:
Re: [KERNEL] Semaphore JB 2.9.15

It's a splendid app. It would be great to have that feature inside the kernel natively.

Sent from my SGS Classic

via banana split.
[Galaxy S I9000 Android Development] stratosk:
Well, I didn't say that. But anyway, I will try to check how it works.
[Galaxy S I9000 Android Development] Rokostar:
AW: [KERNEL] Semaphore JB 2.9.15

Thats awesome but can you please check the app proximity screen off mybe you can include that in your kernel app some more members want that too.
[Galaxy S I9000 Android Development] jugster:
Re: [KERNEL] Semaphore JB 2.9.15

If you want some inspiration, there is a sweep2wake implementation for the nexus 4. Seeing as you'll be getting that device soon (I hope) it might be extra interesting. I think the source is available in the Bricked kernel.

Signature? Signature!
[Galaxy S I9000 Android Development] sandman303:
Re: [KERNEL] Semaphore JB 2.9.15

guys help i flashed this and now my phone wont boot! noooooooooo:(
[Galaxy S I9000 Android Development] superkoal:
Are you on Android 4.1?
[Galaxy S I9000 Android Development] Starsream88:
Re: [KERNEL] Semaphore JB 2.9.15

Go to Download mode and try to flash a different kernel using odin (compatible kernel of course, depending on your android version and partition layout ...)
[Galaxy S I9000 Android Development] everb00b:
I have a question about the IO Sched.

As CM moved to ROW, is it significantly battery friendly rather than SIO?
[Galaxy S I9000 Android Development] jugster:
Re: [KERNEL] Semaphore JB 2.9.15

There are use cases where it is more friendly to the battery than SIO. The opposite is also true. Your mileage may vary.

The point is, except for my excellent answer, it is impossible to answer that with the information you have given.

Signature? Signature!
[Galaxy S I9000 Android Development] Fiize:
Hey guys! I was wondering what your experiences are

with KSM? Do you guys keep it on all the time? Or are

they any perceivable difference in performance when

turning it on? your thoughts...
[Galaxy S I9000 Android Development] test123456789012:
AW: [KERNEL] Semaphore JB 2.9.15

As far as I know KSM settings don't have any effect on semaphore, because semaphore doesn't support it.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] strainhunter:
Semphore doesn´t even have the option for KSM in settings to enable it, as far as i remember.

It think the zRam setting isn´t there, too.

So, no experience with them while on Semaphore^^

Greetings, Strainhunter
[Galaxy S I9000 Android Development] Rokostar:
Semaphore do not Support KSM, ZRam or Swap. I belive he explained that he want a simple Kernel which is not overload with unnecessary settings.
[Galaxy S I9000 Android Development] dark_knight35:
AW: [KERNEL] Semaphore JB 2.9.15

@Stratos What do you think of implementing Westwood+ ( http://c3lab.poliba.it/index.php/Westwood)? And do you think the 3.4 kernel port for S plus has some goodies for us ( http://xdaforums.com/showthread.php?t=2165341)?
[Galaxy S I9000 Android Development] Rokostar:
AW: [KERNEL] Semaphore JB 2.9.15

What is Westwood ?
[Galaxy S I9000 Android Development] Fenvarien:
AW: [KERNEL] Semaphore JB 2.9.15

A TCP Congestion Algorithm that modifies TCP Reno. A lot of kernels for the GNexus provide the possibility to choose between several TCP Congestion Algorithms. Westwood seems to work very well with good performance.

Read more about this here: http://en.m.wikipedia.org/wiki/TCP_Westwood
[Galaxy S I9000 Android Development] stratosk:
I wonder how much traffic we have on a phone to need an advanced TCP congestion control algorithm.

For example I use the FIFO network scheduler since day 1 in Semaphore (maybe it's the only kernel which uses the simplest one). Nobody complained about network traffic issues.

About the 3.4 kernel. Maybe it will not have noticeable differences in features but obviously we would have many benefits since it's later version.

But I would not risk to rebase Semaphore to 3.4 without second thoughts. I don't say something bad about the work of the developer who made the upgrade, but I would like to be sure about the origin for such big changes.
[Galaxy S I9000 Android Development] Fenvarien:
AW: [KERNEL] Semaphore JB 2.9.15

It makes sense for Tethering. If you tether a lot you can definitely feel a difference between the different TCP Congestion Algorithms.
[Galaxy S I9000 Android Development] stratosk:
Thanks. Did you try? Any suggestions?

(I doubt that I will include Advanced TCP congestion control into Semaphore, but you never know :) )
[Galaxy S I9000 Android Development] Turtuga:
stratosk pawitp say this

http://xdaforums.com/showpost.php?p=39116724&postcount=3507

is possible you take a look in this problem please
[Galaxy S I9000 Android Development] stratosk:
Re: [KERNEL] Semaphore JB 2.9.15

I will check it my friend but I would say that I don't think it's kernel related.
[Galaxy S I9000 Android Development] Turtuga:
ok thanks for your time ;)

you are amazing
[Galaxy S I9000 Android Development] VyRuZ_:
Re: [KERNEL] Semaphore JB 2.9.15

Hello guys!

I've been running on the incredibly stable Semaphore kernel for quite some time now and I feel it's time to go overboard with my i9000.

I'm using PAC ROM, with Semaphore .13, smartassv2 tuned and sio, hugemem, 114% live OC. Phone is as stable as it can be.

Can someone help me in reaching a higher frequency, with the corresponding voltages? What tools should I use, what guide should I follow?

Thanks in advance for any help! :)
[Galaxy S I9000 Android Development] :
In overclocking, in general, there isn't any guide for reach max stability; your experience does.

Try to set normal voltage, then go up with frequencies. Play some games, run antutu benchmark for testing stability; after that, if you are stable, go down with voltages: if your phone reboot, increase voltages, that's it.

Every phone have an own stability; on my phone i am stable with 105% oc and the voltages in my signature; with another i9000, with my backup, crash only with 105% oc.

It's luck :victory:

EDIT: it would be interesting to overclock with differently scheduler; anyone tried this in past?
[Galaxy S I9000 Android Development] ts1506:
Scheduler doesnt affect CPU. Maybe you mean governor. In crazy OC situations ( for me , 120% ) , a governor which switches through frequency slowly , like conservative , is more stable than one which swictches fast , like ondemand. But that beats the purpose of such a high OC , cause phone is more responsive with ondemand @ 114% than conservative @ 120%.
[Galaxy S I9000 Android Development] :
Thanks for reply :)

Nope, mean scheduler, but governor have more impact to CPU (like you said :) )

So, this is my bible for governor.

I try to go deep, because (it's only my opinion) i think that different schedulers works differently; and maybe a scheduler work differently (simple) than another. Have you any link to learn how schedulers works?

Sorry for my english, maybe i have to learn first, and after that scheduler behaviors :D
[Galaxy S I9000 Android Development] The Tox:
i Flashed 2.6.5 for CM - JB 4.2.1 with success

but i found only 3 governor

Performance / powersave / ondemand

i thought that there is more like smartassv2

andI/O schudler there is only : NOOP ?!
[Galaxy S I9000 Android Development] dark_knight35:
AW: [KERNEL] Semaphore JB 2.9.15

Use Semaphore Manager instead of performance settings.
[Galaxy S I9000 Android Development] ts1506:
For starters , you should flash 2.9.15 for JB 4.2.1 .

And for the rest , use Semaphore manager.
[Galaxy S I9000 Android Development] The Tox:
thank you ( i'll press it ;) )

can you tell me what's the best governor / scheduler etc to get performance and battery life

---------- Post added at 06:11 PM ---------- Previous post was at 06:09 PM ----------

i installed 2.9.15 earlier but the phone didn't want to boot

i read on the first page that 2.8 is for JB 4.2 and 2.6 is for 4.1

i'm using CM 10 ( 4.1.2 )
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
so you are using 4.1.2 not 4.2.1

and for the scheduler / governor there are no specific ones for battery save you try your own mix :good:
[Galaxy S I9000 Android Development] ts1506:
You just posted that JB-4.2.1
[Galaxy S I9000 Android Development] The Tox:
sorry , my mistake ^^
[Galaxy S I9000 Android Development] yavu:
AW: [KERNEL] Semaphore JB 2.9.15

Interactiv + Row is the best combination for me.
[Galaxy S I9000 Android Development] kaarburo:
I find it very powerful SmartassV2 + CFQ
[Galaxy S I9000 Android Development] dark_knight35:
AW: [KERNEL] Semaphore JB 2.9.15

I use sio and ondemand, but that was already discussed so often.

---------- Post added at 07:13 PM ---------- Previous post was at 06:50 PM ----------

Okay, that makes sense. I've read that Dorimanx uses ext4 improvements from 3.6.x kernel. That could give us a better performance, too.
[Galaxy S I9000 Android Development] s3icc0:
Thank you ... again and again ...

Hey Stratosk,

thank you again for your great kernel and for your hard work for Galaxy S users and linux comunity.

I have been using (since ICS) your kernel with 114live OC and smartassv2 but today I switched to ondemand and no OC ... just defaults and it is great again ... cant believe it.

hope yoou will find us some new cherry picks to keep galaxy even better :)

I am looking for new phone but unluckily I have no money recently :( but definitely it will be something really opensource and probably the same you will have :)
[Galaxy S I9000 Android Development] Neel.I:
off-topic

If OEMs every check out these threads,they'd know how many purchases are influenced by developers.

May be they ought to give away handsets to people like Stratos,who truely deserve one :)

How I wish they'd embrace open-source too! :(

/off-topic
[Galaxy S I9000 Android Development] alb3rtt:
I wish too. I LOVE the specs of the S4, they are so perfect for my needs yet because they are becoming like Apple and not embracing open source, i will probably not buy one. I learnt my lesson with my old phone, the Galaxy 3 (i5800). It had a beastly CPU which could run @1.4ghz FULLY STABLE (compared to 667mhz stock) but a weak as hell gpu and practically NO sources available. It still does not have fully working 2.3.7. I really dont want that again so i will buy a phone with great open source, probably a Sony because i need an sd slot (sorry nexus).
[Galaxy S I9000 Android Development] Neel.I:
It was sad to read about Sammy's approach on S3,and just yest CM developers posted about not being too keen on S4.Seriously,don't know why they are shying away towards being so closed.

Nexus were the only devices worth noticing but then,Nexus 4 :\

Totally agree with you on the expandable memory slot.

I guess only Sony is playing its cards right these days.A Sony Nexus would be a killer combo(Far from being fulfilled dream!)

Lets hope Moto springs up a surprise for us this May!
[Galaxy S I9000 Android Development] grinder777:
AW: [KERNEL] Semaphore JB 2.9.15

+1

Moto is building beautiful phones again, last time... Think they are coming back!

md p9516 - root -waiting for cwm -- thnx2all
[Galaxy S I9000 Android Development] jelennn:
Stratosk help please!

I have SlimBean 4.2.2 v2 and Semaphore 2.9.15s.

Always after two days of using the phone my I9000 is very slow, have a log of lags and sometimes in more heavy apps I have freeze phone. I have a fresh install SB. I don't have any speciall apps, scripcts.. My settings in Semaphore Manager is standard. This situation is normal? What I can do?

What I should set in semaphore manager? What is the best settings in this app Stratosk? I want fast, stable and longtime of use I9000.

What do You think Stratosk about it: http://xdaforums.com/showthread.php?t=2158329 ?

Or maybe this: https://play.google.com/store/apps/...vbS5zbWFydHByb2plY3RzLlJBTU9wdGltaXphdGlvbiJd ?

One of this should be help?

Thanks!
[Galaxy S I9000 Android Development] khankk42:
Re: [KERNEL] Semaphore JB 2.9.15

when i reboot my phone it uses all the ram i mean out of 409 Mb rom it uses 404 Mb rom how can i fix it is it rom problem or kernel problem

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
Re: [KERNEL] Semaphore JB 2.9.15

Do you have so many apps installed +300

---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------

I think this was discussed on SB thread and a reboot should get your phone OK without lagging
[Galaxy S I9000 Android Development] Lucius1972:
Re: [KERNEL] Semaphore JB 2.9.15

Maybe a stupid question but if I change the governor and/or scheduler, is het recommanded to flash dalvik and reboot or can it be done " on the fly"?
[Galaxy S I9000 Android Development] TenBelowZero:
AW: [KERNEL] Semaphore JB 2.9.15

You can just change governor/scheduler, no need to do anything else.
[Galaxy S I9000 Android Development] sandman303:
Re: [KERNEL] Semaphore JB 2.9.15

Hi sry for the late reply , I was on android 4.2 and I flashed a kernel but it didn't work.....thanks
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
Re: [KERNEL] Semaphore JB 2.9.15

Give some useful info like which ROM which use and which version of kernel you flashed none can help you in this way
[Galaxy S I9000 Android Development] superkoal:
After a reboot also the media scan and a few other apps are doing their startup routines, you should wait a while until your phone has settled.

If it stays this way you should check your active apps.

Usually you should have 100-150 mb free ram, depending on your ram management and your running services.

Remember that your system using the ram available is not always a bad thing!
[Galaxy S I9000 Android Development] yavu:
But you need an app like a task manager to see the real free ram, because over system settings you don't see the right one.