yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] stratosk:
Please checkout branch mr1-staging for both kernel and ramdisk.

Do your other option apply correctly? Is LiveOC your only issue? You said that you use Slim Bean. Do you use the built-in kernel?

Any messages in logcat?

I can't be sure. 2 to 5 is not much difference. You can also say that it's a coincidence.

Maybe let you device settle down for some hour and retry?
[Galaxy S I9000 Android Development] radicspeter:
Thanks again!! 2.8 Works REALLY FAST AND SMOOTH ON ELITE F7!! +1000

Tapatalk 2-vel küldve az én GT-I9000-ről
[Galaxy S I9000 Android Development] RlndVt:
Thanks for the quick reply.

"git checkout mr1-staging" right? Worked for the kernel, not for the ramdisk. I am building a 2.8.0 kernel now though.

No errors occured, thanks :D amazing kernel work!
[Galaxy S I9000 Android Development] franzyroy:
At the first start, my Wi-Fi didn't connect, I left enabled and restart the phone, when it have rebooted, it was connected. I say it for those who will have this problem! ;)

Thanks stratosk... always also good!
[Galaxy S I9000 Android Development] elitevet:
Stratos, thank you so much for your amazing work and unprecedented responsiveness and persistence. You are, undoubtedly, one of the gems of this community and an inspiring model for many, I am sure.

I already envy the N4 guys and gals who will benefit from the great contributor you're being.

Thanks again.

6PF653773D1374114

sent from AOSP 4.2 powered SGS
[Galaxy S I9000 Android Development] Hayabusa_XDA:
problem swap feature semaphore 2.5.0ts

Anyone here using swap feature with semaphore 2.5.0ts on CM10 or Slimbean?

I'm running SlimBean3.1, obviously with much too many apps / widget, because SB3.1 is not able to handle this load. Directly after boot the system is "flying", wonderful, but after a day or after starting really much mem consuming apps the system is becoming a mess. Ironically good old GB 2.3.6 was able to handle the same load within its normal lags ... strange ...

I'm thus testing ZRAM and SWAP for the last two days and

SWAP feature is simply unbelieable

. :D I used app swapper2 to active at boot and a 1GB swap-partition (256MB would be enough though) on an old/unused Samsung 8GB class 10 sd-card

It's simply unbelievable what good old SGS is able to with enough RAM, and if it's only pseudo RAM via SWAP. It runs stable for hours with the heavyest load I ever dared to put on my SGS. Simply wonderful, and yes I know it will kill my SD-card after a few months (but who cares, this sd-card is only about 10-11€).

As long as phone is active, everything works well. But for the last two nights the phone crashes at night (almost full battery completely drained in the morning). This is very strange as at day during periods of inactivity - even for hours - battery drain is as low as usual (have seen only about 2-8 mA as monitored by "Battery Monitor" app) without any crash.

Has anyone similar experiences or any ideas? :confused: Or what can I do to identify the problem? SD-card is error free.

Is it possible to get a swap-feature enabled version of semaphire 2.6.x (s/without s)?
[Galaxy S I9000 Android Development] djceet:
My phone lags very hard after flashing the new 2.8.0.

Anyone have the same prob?
[Galaxy S I9000 Android Development] :
Thanks. Is SmartassV2 not better than ondemand for a quick and not high battery comsumption? Do you mean auto brightness setting in Semaphore Manager oder CM 10 ? I use CM 10 Stable and the actual Semaphore 2.6.6 is the best Kernel oder an older one ?
[Galaxy S I9000 Android Development] Lorog:
Up guys
[Galaxy S I9000 Android Development] Giap:
Do your other option apply correctly? Is LiveOC your only issue? You said that you use Slim Bean. Do you use the built-in kernel?

Any messages in logcat?

Thanks for follow-up. The build-in kernel of SB 3.1 is 2.6.0. I have changed it first to 2.6.0s and then I updated to 2.6.5 and now to 2.6.6 versions.

Actually, there are other options that are not taken up in NSTools: I select SIO in Sema manager but it remains Noop in NS, I put touchwake delai= 20 sec but it remains =0 in NS. Therefore it seems that NS does not take in account the modifications in Sema manager. I will try to wipe NStools and Sema settings and resetting all.
[Galaxy S I9000 Android Development] Lorog:
Besides, led buttons light doesn't work on miui, why?

edit: sorry in miui rom there is not this option
[Galaxy S I9000 Android Development] djceet:
Please, someone tell me anyting about that-------> "- enable O3 in GPU driver (thanks DerTeufel for idea)" :eek:
[Galaxy S I9000 Android Development] flash-90:
@djceet
[Galaxy S I9000 Android Development] djceet:
ah ok.

and where can I change this?
[Galaxy S I9000 Android Development] Cu8eR:
It is a joke, right? Last semaphore is compiled with this flag, you cannot change anything :D:D:D
[Galaxy S I9000 Android Development] djceet:
hehe......yes it was a joke :o :D

i just read "new gpu settings" in other forum......oh man........but we know it was a joke. ;)
[Galaxy S I9000 Android Development] MrMagic:
What settings are those? Are these the settings that allow the volume to be configured as "Quiet", "Quieter", etc. for each type of call, like speaker, headset, etc.?

If yes, then I would like to keep them, because my SGS is too loud by default and I always set these volumes lower.
[Galaxy S I9000 Android Development] stratosk:
Thank you so much, my friend! Really appreciate your words and your donation!

Many thanks!

I think ondemand is better. Yes, I mean Semaphore auto brightness.

I'm sorry I don't understand your question about the older kernel.

Can you please check that your ROM settings about performance (governors, max frequency) does not apply? This is really very weird.

You may find these settings in Galaxy S advanced app, or in the advanced menu item in system settings.

You could adjust the volume when in-call.

I dropped them, because they introduced to much distortion.
[Galaxy S I9000 Android Development] :
I use CM 10 Stable. Of the semaphore kernel is on the fastest 2.6.6 or an older version such as 2.5.0 or 2.6.0 or even older? Or you can generally always assume that the latest version is best?
[Galaxy S I9000 Android Development] METEMEDO:
Hey guys, i've compared my I9000 Wi-Fi signal strength to my girlfriend's LG Optimus Black and i've noticed that she gets a much stronger signal, like, she gets 2-3 bars where i get 0-1 bar and i even get disconnected sometimes.

Is there a way to improve the Wi-Fi strength?
[Galaxy S I9000 Android Development] stratosk:
Obviously, I will never say that an older version is better. ;)

Everybody is trying to make things better, to improve what he does.

At least, I'm trying to.
[Galaxy S I9000 Android Development] oblikas:
Very nice kernel ! I get this device after a Xperia Arc and I feel the difference.Stratosk,very nice job ! Can you tell me where I can find ur source ? Thanks .
[Galaxy S I9000 Android Development] dark_knight35:
You will find a link at the end of first post.
[Galaxy S I9000 Android Development] stratosk:
Thank you. :)

https://github.com/stratosk/samsung-kernel-aries/tree/mr1-staging
[Galaxy S I9000 Android Development] oblikas:
I have a little question for you...sometimes if i connect phone to charger and reboot,ROM is stuck at Semaphore kernel and keeps rebooting (tried in all ROMs)...and I can't go in recovery too ...
[Galaxy S I9000 Android Development] Giap:
Hi Stratos,

I really need your help for understanding. I have wiped both NStool and Sema manager setting in recovery. I have then rebooted, select the setting in Sema manager, including OC 110 and then I have opened NStools that registerd correctly the new settings. The phone went in bootloops, impossible to stabilize it. I have now reset Sema, but I have always a message "NSTools setting are rejected....." until I open NSTools and have permissions from SU. But then the phone reboots again. What can I do? Suppress OC, other? Settings are applied n the ROM but I can't concile OC with a functional phone
[Galaxy S I9000 Android Development] franzyroy:
You have seen this post?
[Galaxy S I9000 Android Development] leonardoafa:
Can anybody tell me if theres any version with Voodoo Colors for JB 4.2????
[Galaxy S I9000 Android Development] franzyroy:
Not Semaphore but you have the Mackay Kernel.
[Galaxy S I9000 Android Development] Giap:
Of course I read and have you read my answer? I do not use Sema manager and NS tools at the same time. However if I do not allow NS Tools to have SU permissions the phone reboots anyway. What should I do? Freeze NS Tools? I have now reset Sema Live OC to 100% and the problems have gone!
[Galaxy S I9000 Android Development] leonardoafa:
Thank you again franzyrou, but i have I9000B, and theres no Mackay kernel for this variant! :(
[Galaxy S I9000 Android Development] EMnEL:
Unable to access USB storage in recovery mode.

Dear stratosk,

Greetings! Hope all is well with you!

I've always been a big fan of your kernel and have been using it from my 1st custom rom starting from GB. I have a small issue which you can help. I have a strange problem where I'm unable to access the USB storage in the recovery mode while using your kernels for JB. I have tried other kernels as well as other JB roms to check if the problem lies with the roms or the kernels. Unfortunately, it seems that this problem occurs when using semaphore. Any help will be highly appreciated.
[Galaxy S I9000 Android Development] test123456789012:
I have this too.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] senotrius:
dear stratosk, could u please optimise the performance aspect of the kernel.the only current way to play dead-trigger on high quality setting seems to be by using lazeroid script.but the script is not stable for daily use.the great android doesn't free up memory as required.dead trigger requires 150mb to work.which our phone with 404 is unable to provide?!(unless I resort to reboot plus the script)

not going to get into the free ram argument as its pointless(only get 130-180mb free anyway).but surely the ram should be available when its required?!that's what I learned from using lazeroid.it enabled me to play the game with same 160mb free ram.SO definitely the kernel aspect needs tuning.I agree free ram is not everything.

currently the game just shuts itself off after selecting a mission.

overall microlags are present.this is after a clean full ROM+new kernel install sans any script.

is anyone else able to play the game smoothly in best settings.it could be just my phone.

even opera shut itself 5 times now.low ram.what to do.system not clearing off ram as its supposed to.and no background apps are running.
[Galaxy S I9000 Android Development] pikachu01:
Using ThunderBolt! scripts, I can play Dead Trigger without problems. Long term usage is also good as well :/
[Galaxy S I9000 Android Development] carniman78:
Erased. Posted in the correct thread
[Galaxy S I9000 Android Development] stratosk:
Hi,

One more time: please do not use NStools if you don't know exactly what you are doing. Of course, you can use it if you want but you may have conflicts.

1) Uninstall NStools

2) Check your CPU frequencies with CPU spy app

3) You may check if the OC value applies with 'cat /sys/devices/virtual/misc/liveoc/oc_value'

4) If your phone is unstable try to use OC 114.

5) if you are familiar with under/overvolting try to change the CPU voltages

6) Please do not use NStools.

P.S. Please do not to use NSTools. :)
[Galaxy S I9000 Android Development] pikachu01:
Please post them in the ThunderBolt! thread and I will answer it to my best efforts :)

http://xdaforums.com/showthread.php?t=1556013
[Galaxy S I9000 Android Development] senotrius:
thank u.its released for jb?I had used ur script in days of GB.hmm.no reply from the kernel developer.
[Galaxy S I9000 Android Development] franzyroy:
Sorry! :(
[Galaxy S I9000 Android Development] stratosk:
Kernel developer is in his real job trying to earn some money. He tries to answer posts, PMs, emails, Google+ messages in FIFO order when there is free time.

Please for your patience.
[Galaxy S I9000 Android Development] H-Body:
Don't take those people too serious, Stratos! :)

They don't know how to appreciate your great work for all of us!
[Galaxy S I9000 Android Development] radicspeter:
I'm really fans too of your kernel but the 2.8 in F7 elite rom is not working properly...

So i couldn't turn on GPS. And sometimes data is not accessing to internet. Otherwise it's great and i'm sure you will improve it in the next realise of 2.8.

Tapatalk 2-vel küldve az én GT-I9000-ről
[Galaxy S I9000 Android Development] elitevet:
There is no ROM but CM and Semaphore is it's Kernel.

sent from AOSP 4.2 powered SGS
[Galaxy S I9000 Android Development] fmc000:
FYI, I tested the GPS both with a test app and with a navi software using CM10.1 and Sema 2.8 - Fix in 15 seconds! All perfect.

---------- Post added at 11:26 AM ---------- Previous post was at 10:41 AM ----------

Hello stratosk,

just for clarity: is this correct to build the 2.8.0 kernel?

mkdir -p semaphore/output/galaxys
mkdir -p semaphore/output/captivate
mkdir -p semaphore/output/vibrant

cd semaphore
ln -s gcc-linaro-arm-linux-gnueabihf-4.7-2012.11-20121123_linux/bin/ toolchain

git clone -b jellybean git://github.com/stratosk/samsung-kernel-aries
git checkout mr1-staging

git clone git://github.com/stratosk/ics-ramdisk
git checkout mr1-staging

cd ics-ramdisk
tar zxvf jb_combo.tar.gz
tar zxvf jb_combo_c.tar.gz
tar zxvf jb_combo_v.tar.gz

cd ~/semaphore/samsung-kernel-aries
./sbuild galaxys

Can you please write what are the actions you perform to get in sync with 3.0-stable branch and pawitp-kernel branch?
[Galaxy S I9000 Android Development] pikachu01:
Yeah, I'm using it in CM10 currently :)
[Galaxy S I9000 Android Development] Cu8eR:
Semaphore APP feature request:

- add an option - Touchscreen sensitivity - stock, ...

- add OC option - maybe 4 profiles - 800MHz, 1000MHz(stock), 1140MHz, 1200MHz ... - and add a warning popup or a warning text - use at your own risk

- stock values (governor, scheduler) should have a "*" symbol (stock settings in kernel) - I know there is an option to reset to defaults, but it resets everything

What is your opinion? Thank you!
[Galaxy S I9000 Android Development] alb3rtt:
Oc is there.
[Galaxy S I9000 Android Development] HoangTuBot:
Please makes one(Semaphore 2.8.0) for captivate
[Galaxy S I9000 Android Development] prbassplayer:
Give Stratosk time. He always releases for other devices few days after I9000 ;)

Sent from my SlimBean 4.2 Alpha powered Captivate
[Galaxy S I9000 Android Development] senotrius:
That wasnt even the issue now was it?ur the guy who develops the kernel.which is why I posted the experience I got with the kernel here.where else am i supposed to ask for help huh.I'm thankful u put ur spare time into developing.I'm no expert like u.jeez,I can't say an honest opinion now without sounding rude or something to u?wow.

---------- Post added at 09:20 PM ---------- Previous post was at 09:17 PM ----------

Man,did u even try playing the game I said without serious lag?!did I say the kernel sucked or something?chill man.
[Galaxy S I9000 Android Development] stratosk:
Hi, I hope you are OK too!

I've just tested again, and have no problems with mounting usb in recovery in my Linux box.

But it's true that some people have issues in JB. Maybe, you should try to re-install drivers?

If using a script resolves your issue, it simply means that the issue is not kernel related and there is nothing I can do (AFAIK).

I don't play games in my phone, but maybe our device can't handle so demanding games.

I just had a fast and accurate GPS fix on a cloudy sky (AOSP 4.2 by pawitp)

It's seems OK. You may omit the untar for captivate and vibrant if you don't need them.

I manually 'git apply' the patch from kernel.org to stay in-sync with Linux kernel.

I also manually select the commits to apply from CM kernel. I don't patch every change from CM.

About the screen sensitivity, I remove the functionality in JB because it didn't work.

I can't see the usability about the OC. Now you can drag the seek bat to the desired value. It's so simple.

I would agree about your third point, but it would need something more generic for every option.

I didn't say that because you asked for help. I said that because of this phrase: '...hmm.no reply from the kernel developer.' couple of hours after your question.
[Galaxy S I9000 Android Development] Giap:
Thank you Stratos for your patience,

1) Uninstall NStools > I uninstalled

2) Check your CPU frequencies with CPU spy app> I set 114% and it was OK in CPU spy

4) If your phone is unstable try to use OC 114. > After setting Live OC 114 the phone reboots spontaneously

5) if you are familiar with under/overvolting try to change the CPU voltages > I tried to undervolting by 25 but the phone still rebooted

6) Please do not use NStools. > I did not use it before, now it is uninstalled The issue did not come from NSTools conflicts but from OC

Conclusion:

My phone does not support OC. I don't know why. I reset Live OC 100 and the phone works as before.

SGS I9000

Slim Bean 3.1 + real dark slim + superlauncher

Nova launcher

Semaphore kernel 2.6.6s

Semaphore manager 2.2.1

JVU modem
[Galaxy S I9000 Android Development] elitevet:
IMHO you should try some interim steps in over clicking. Start with 105%

sent from AOSP 4.2 powered SGS
[Galaxy S I9000 Android Development] RivalComp:
I think your I/O scheduler not well optimized or something is wrong with your multitask. I think you should flash Semaphore... :D
[Galaxy S I9000 Android Development] fmc000:
OK, thanks. I'm not a developer, I'm just trying to understand the steps I will have to follow once you move from SGS to your well deserved Nexus.

I'm thinking to add the changes related to CWM. What do you think? BTW, what's the CM repository URL you use for kernel 2.8.0 ?

Thanks in advance.
[Galaxy S I9000 Android Development] ZioGTS:
Could you please do us a favor? Show some respect to Stratosk. He's a good developer and a real gentlemen. He's always trying to help each and every user of his great kernel. And he's doing it all for free. Nothing personal, of course, but YOU should be chilling out, not Stratosk. Peace man, take it easy! ;)
[Galaxy S I9000 Android Development] stratosk:
Yes, maybe I need an update. I'm getting old... :)

What CWM changes?

What exactly do you need to do? There are no exact step to maintain a kernel.

Please find the links for CM code in their threads.
[Galaxy S I9000 Android Development] Noumen:
There is a bug with semaphoe 2.8.0 with aosp 4.2.1 ( pawitp)

Using OC 110% with smartass2 result in the following issue:

Cpu 1100 ghz hang on 07 seconds usage ( checked by cpuspy) no matter What application/ game you use

Its like the max cpu frequency is 880
[Galaxy S I9000 Android Development] daxgirl:
Spontaneous reboots into recovery with no OC

Hello dear Stratos and fellow users,

i carefully went through this thread looking for a solution to a problem some of our users have been reporting.

The roms I'm talking about are based on AOKP M1 and the kernels that are used are 2.6.2 and 2.6.2s

The users report experiencing frequent (about once or twice a day) reboots into recovery mode. Most of the time while phone is not used (independent of implementing deep idle - some were and some weren't)

Steps that have been taken so far:

Implementing no OC - no effect

Using default governor and scheduler - no effect

Flashing stock + 512 pit + hard reset and then proceeding to root > cm9 > cm10 - no effect

I'm sorry if someone gave a possible solution and I missed it, but I only found recommendations to reduce OC and go to rather default settings which has already been implemented with no results.

I would appreciate any advice on the matter.

Also, strangely enough, I myself experienced such event only once and it was with an older semaphore version. No repeats for me after upgrading.

Thank you in advance for any advice on the matter or referral to a possible solution.

Best regards :)
[Galaxy S I9000 Android Development] rmsinaga:
Check your Maximum CPU Frequency setting, perhaps it's limited to 1000MHz.
[Galaxy S I9000 Android Development] METEMEDO:
Hey guys, some pages ago i've written about how bad my Wi-Fi strength is.

I would really like to know if there is anything i can do to increase its strength to at least the level of my girlfriend's LG Optimus Black's.

Thanks.
[Galaxy S I9000 Android Development] Sharken:
You have two options as i see it:

1. Turn off 'Avoid bad connections' in the Wifi settings.

2. Downgrade to ICS.

The XDA link below believes that 4.2 will improve WIFI-connections, so it might be worth trying out.

Additionally Wifi Analyzer from Market can give you a reading of the signal strength, much more reliable than looking at the wifi bars.

The problem has Googles attention :

http://code.google.com/p/android/issues/detail?id=34942

XDA link :

http://xdaforums.com/showthread.php?t=1769908
[Galaxy S I9000 Android Development] Cu8eR:
OK, I dont have your problem - I have same wifi streght on ICS and JB (2bars)... Wifi works great, maybe in semaphore app check wifi pm fast
[Galaxy S I9000 Android Development] Senthurpandian.r:
Urgent !!

Will Semaphore 2.8 works in Slim Bean 2.9 (Android 4.1.2)??

I've installed an stuck in Slim Bean logo...
[Galaxy S I9000 Android Development] rmsinaga:
Oh my...

If only you read the instructions in OP, then you'd avoid this mess.
[Galaxy S I9000 Android Development] Sharken:
That sucks.

For Android 4.1 newest version is 2.6.5.
[Galaxy S I9000 Android Development] fmc000:
OK, it didn't work. I set up the toolchain, checked out the kernel and the ramdisk, changed the name of the kernel inside the sbuild.sh script (Semaphore_FC_2.8.1), patched with 3.0.56 from kernel.org and compiled.

The kernel booted but nothing worked, the phone app keep crashing making the phone unusable. I had to pull the battery, reboot in recovery mode, reflash ROM and your kernel and all is good now.

I suspect some initramfs problem as the "git checkout mr1-staging" in the initramfs dir did not work. Any suggestions?

---------- Post added at 09:27 AM ---------- Previous post was at 09:18 AM ----------

Sorry for not making myself clear, I'm not an English native speaker. My goal is to learn how to maintain my own kernel when you decide to leave the SGS. I think that I will add only the CWM changes that eventually the CM team will implement and the kernel.org stable patches.
[Galaxy S I9000 Android Development] herc2k:
can someone post the voltages for overclocking? i cant even go to 101 stable :(

only with stock kernel can go to 120% stable

at the moment using slim bean 3.1 semaphore 2.6.6s bigmem tried other roms but same result not stable when overcloackin above 101%

only stable with stock kernel
[Galaxy S I9000 Android Development] DeusEx80:
No problem here with Live OC 110% (without change voltage) with 2.8.0 and pre-nightly cm-10.1-20121211.

Try to reset OC, and set OC again.
[Galaxy S I9000 Android Development] Cu8eR:
Same problem - 101% OC and higher values cause lags and restarts... with stock kernel I can overclock to 118% without problems... can someone provide us voltage settings or information how to OC with semaphore? :D
[Galaxy S I9000 Android Development] elitevet:
+1

I use exactly same setup and have no problem too.

sent from CM powered SGS
[Galaxy S I9000 Android Development] rkaede:
for me i never touch the voltage settings. how to oc in semaphore? just slide that bar.:D
[Galaxy S I9000 Android Development] DeusEx80:
.... and NEVER use/install NSTools :)

For checking the frequencies, there is Cpu Spy
[Galaxy S I9000 Android Development] elitevet:
...and / or BetterBatteryStats

sent from CM powered SGS
[Galaxy S I9000 Android Development] Giap:
I already discussed about the OC issue with Semaphore kernel 2.6.5 or 2.6.6, see poste #4083 for conclusions, but I had not verified with other kernels. Which is your stock kernel? The in-built kernel that comes with Slim Bean id Sema 2.6.0.