yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] nereis:
Does the UV table look off?

Looks like semaphore manager is setting the UV to the top five steps.

Not sure if this is suppose to be functioning like this, or should we use another app to set UV?

I have Live OC 124 but max scaling freq capped to 992Mhz, and 1275mV was stable for this step when on original Semaphore. Not sure if the current setting might be making my phone unstable?
[Galaxy S I9000 Android Development] ts1506:
I have already mentioned to use NSTools to control voltage and OC, Semaphore Manager sets for the top 5 steps.
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
hey ts

I am sorry but what are these

3. Optimized AES and SHA1 routines

4. CPU Unaligned Access
[Galaxy S I9000 Android Development] ts1506:
Point 3: Adds a seperate optimized assembler for AES and SHA1 for ARM Processors. This increases TCP throughput and performance for AES/SHA1 tunneling.

Point 4: Allows data access in which the alignment is done using CPU than by software. It is faster in theory, dunno how much of it will translate practically.
[Galaxy S I9000 Android Development] ts1506:
From next kernel version onwards , it is recommended to use a modified NSTools to control kernel instead of Semaphore Manager.

Semaphore Manager is causing several conflicts , and I am not in the mood to add the extra governors into it, so NSTools it is.

I will add init.d scripts for controlling features missing from NSTools.

Unfortunately, this will mean that SAI Service cant be used at all.

You can use those via Semaphore Manager, but then, the NSTools app and the scripts must be removed first.

I will also put out some kernels based on CM for testing soon. These will be easier to control.
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
the cm kernels is a really nice step :)

good luck
[Galaxy S I9000 Android Development] ts1506:
CyanCore Kernel 2.7.0 uploaded and attached to OP

Changelog

1. Added BFQ IO Scheduler

2. Added FIFO IO Scheduler

3. Added ZEN IO Scheduler

4. Enabled TUN by default

5. Default governor Lulzactive

6. Block and ROW improvements

7. All governors and IO Schedulers built into kernel

I have also attached modded NSTools by fishears for kernel control.
[Galaxy S I9000 Android Development] tsatomas:
Is this modded nstools good for other kernel (Mackay or Sema) or just for cyancore?

Edit, tried on Mackay seems ok
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
For all
[Galaxy S I9000 Android Development] idCyber:
[MENTION=4823985]ts1506[/MENTION] : you said to uninstall Semaphore Manager and use NSTools with your new kernel because if we use SM alone or in combination with NSTools, the kernel might not work as it should. But I have 1 Question : How can I enable/disable bigmem and set SDCARD Read Ahead, tweak the governors without having Semaphore manager installed as there are no options for that in your modded NSTools?
[Galaxy S I9000 Android Development] ts1506:
You can tweak the governors in NSTools, for bigmem, see the script in OP.

I will upload the SD read ahead soon, forgot about that.

You can use everything except SAI.
[Galaxy S I9000 Android Development] AbOoM:
i flashed the last version today ,, v2.7.0 on the c-rom mix v22 and baaam .. no booting !! show me just the cyancore image and reboot again :S and some time go to the recovery ! :( i was using all default setting , live oc 120%

Edit : the first login was normal .. after 5min of usage i got a fc on whatsaap i did a reboot and ... :(
[Galaxy S I9000 Android Development] ts1506:
Is your overclock stable? Maybe you used tweaked voltages by semaphore manager? If yes, then reset semaphore manager settings and use NStools to placevoltage and OC correctly.
[Galaxy S I9000 Android Development] AbOoM:
no i dont use a tweaked voltages :S i did a dalvik cache also reset semaphore setting but still hav the same probleme :S ... damn :S i did a reflash to the rom for fixing this and go back to semaphore kernel !
[Galaxy S I9000 Android Development] Blackherted:
Thanks TS... i think i might try it soon :) can't you add the moded nstools to the newest cyancore kernel? (the zip itself) like fishears did?
[Galaxy S I9000 Android Development] ts1506:
I will add it to the zip from next version.
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
In data/app please
[Galaxy S I9000 Android Development] ts1506:
Okay, no problem.
[Galaxy S I9000 Android Development] .:Crack:.:
Hi TS,

After testing every kernel 2.6+ I could not manage to find out when 100MHz works. Seems that it starts to work after some uptime but after a reboot doesn't work again..?
[Galaxy S I9000 Android Development] ts1506:
Are you sure that it worked before 2.6 ? Then I will have to check the Normal OC code, but sorry, after I return.
[Galaxy S I9000 Android Development] .:Crack:.:
Pretty sure.

But as I said, on 2.6.8 it worked after ~30h and I was surprised. After a reboot it stopped working... Can anybody confirm this?
[Galaxy S I9000 Android Development] idCyber:
Ty for the info. In NSTools, the Governor setting is grey and faded and it says not available and I can't find a way to tweak the governor (like I did in SM) that I've selected in System Settings-> Performance. I've tried to fix permissions in recovery. Is this normal ?
[Galaxy S I9000 Android Development] Blackherted:
Yes it is. CWM doesn't fix it... download fix permissions app from the google play and use it on ns tools.. worked for me :)
[Galaxy S I9000 Android Development] gverma1:
Download app Fix Permissions by Stericson from Play store. Use it to fix Nstools. You will be able to change governors then.
[Galaxy S I9000 Android Development] ts1506:
Go to recovery > mounts and storage , then mount datadata and fix permissions.

Or , using a root browser , browse to /datadata/mobi.cyann.nstools , change permissions of preload.prop to rw-r--r--
[Galaxy S I9000 Android Development] idCyber:
ty, now all the settings appeared :D (sorry i can't hit the Thanks button guys as I'm limited to 8 per day)

Sampling down factor resets from what I set (4) to what it wants 15-20-39 step after I exit NSTools but all other settings stick . I've fixed the permisssions using root browser, tried with fix permissions app and by mounting data, datadata, system in recovery and fixed permissions from there.
[Galaxy S I9000 Android Development] ts1506:
Sampling down factor isnt meant to stick. Semaphore Manager only shows the starting value , NSTools constantly updates it.

Sampling down factor changes depending on CPU load and Sampling down max momentum.

The value you specify is the starting value.
[Galaxy S I9000 Android Development] .:Crack:.:
This is a feature by stratosk. It calculates how high the sampling down factor should be by using sampling down factor + a value set as max momentum (default 16, so the sampling down factor will be between 4 -your starting value- and 20 -4+max momentum-. )

If you don't want this feature, just set max momentum to 0 :)
[Galaxy S I9000 Android Development] idCyber:
ty, I learn more every day :D

Edit: thanks button limit per day reset
[Galaxy S I9000 Android Development] .:Crack:.:
Works now, don't know why... Afraid of rebooting

Edit: Did you change anything with the LMK lately ? Seems like whitelist does not work anymore will test since when . The correct PID is set but my launcher still redraws.
[Galaxy S I9000 Android Development] ulysse75:
just installed and fix permission.... Luzactive is not default governor.... still on demand...

just f.y.i.
[Galaxy S I9000 Android Development] Cu8eR:
Any benefits from cyanogenmode kernel? If yes, what?
[Galaxy S I9000 Android Development] DerRomtester:
Read OP!!!
[Galaxy S I9000 Android Development] habylab:
Updates? Non? Some good picks out there, but of course there are always are!

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S I9000 Android Development] alb3rtt:
He is on vacation.
[Galaxy S I9000 Android Development] ts1506:
What do you need anyway?

No significant changes have appeared recently, Linux kernel is latest, everything works.

Sent from my GT-I9300
[Galaxy S I9000 Android Development] ts1506:
CyanCore Kernel 2.7.5 uploaded and attached to OP

Changelog

1. Updated Linux Kernel to 3.0.82

2. Reduce Logger RAM Allocation

3. Disabled Gentle_fair_sleepers
[Galaxy S I9000 Android Development] didhiy:
are you sure kernel v3.0.82? it still 81 in kernel.org

...maybe it's still -rc1 review
[Galaxy S I9000 Android Development] ts1506:
Ya its that one. It's gonna become final today.
[Galaxy S I9000 Android Development] .:Crack:.:
Just found a weird bug :D

LiveOC 125% + 1100MHz step results in weird actual freqs. Most of the time my phone is at 351MHz and sometimes jumping to 87MHz, 250MHz and 500MHz
[Galaxy S I9000 Android Development] didhiy:
Congrats, you made it official before greg kh did by 9 hours or more ;)
[Galaxy S I9000 Android Development] ts1506:
Haha lol :p
[Galaxy S I9000 Android Development] DerRomtester:
What does final mean?
[Galaxy S I9000 Android Development] ts1506:
New kernel 2.7.6 ready.

I am too sleepy to upload anything now, you can get a gist of the changelog by seeing the commits in github.

Will upload in the morning (lol , its almost 4 AM now , thats morning enough).
[Galaxy S I9000 Android Development] .:Crack:.:
Nice, did you also sync with semaphore .26 yet? :)
[Galaxy S I9000 Android Development] ts1506:
The updated recovery is not yet pushed to github.

The updated ondemand code is causing conflicts with other governor's code (can fix it , but needs time and patience, so didnt include it now).

So , I guess it is still .25.
[Galaxy S I9000 Android Development] ts1506:
CyanCore Kernel v2.7.6 uploaded and attached to OP

Changelog

1. Lagfree Governor added

2. Lazy Governor added

3. Lazy Governor tweaked for better performance

4. Ondemand Governor tweaked aggressively

5. Deadline tuned for flash devices

6. Selective Live OC

7. MFC Memory Usage changed to match normal mem one

8. CPU Freq Update fix for DVFS Events
[Galaxy S I9000 Android Development] NDeaz:
Stupid question, but can you expalain what is it? :cowboy:
[Galaxy S I9000 Android Development] ts1506:
Selective Live OC - Say you select low limit 400MHz and up limit 1000MHz , and use Live OC 110% , only 400-1000 frequency will be overclocked , the rest will remain without Live OC.

The 2nd one fixes issues with certain frequency not used due to DVFS locks.
[Galaxy S I9000 Android Development] Facebooook:
Hi ts1506

I am on mackay rom with stock kernel. And now i want to change it with your kernel.My question is....

1should i have to clear init.d script folder thats came with rom ?

2 how to control kernel because mackay rom has its own app(mackay setting) and you recommand nstool.
[Galaxy S I9000 Android Development] ts1506:
1. No need

2. Use NSTools. Make sure to reset Mackay Settings before.
[Galaxy S I9000 Android Development] derboedi:
Happy birthday, ts1506! :victory:
[Galaxy S I9000 Android Development] ts1506:
Thank you... :)

New ROM coming up.
[Galaxy S I9000 Android Development] ficko_98:
[MENTION=4823985]ts1506[/MENTION] which governor you recommend?

And happy b-day!!! :)
[Galaxy S I9000 Android Development] Famzz:
Its your birthday ts! How come no one told me? Happy birthday man. I still remember the day I saw your cyanaosp v0.1 thread (and was the third to post on it :D). Now look where you are, building a kernel, releasing awesome ROMs :crying: they grow up so fast.
[Galaxy S I9000 Android Development] compacity:
Today ur birthday sir?

Happy Birthday and May God Bless U
[Galaxy S I9000 Android Development] KSLevel11:
Happy birthday TS ;)

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 Android Development] Occasus:
+1 :D
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
Happy birth day man

Now you're 17 good luck with your future :D
[Galaxy S I9000 Android Development] phil_greg2001:
Happy birthday TS :cowboy:

Is it possible to use ZRAM script with BB9 ?

Bye
[Galaxy S I9000 Android Development] ts1506:
Possible on any ROM as long as using CyanCore.
[Galaxy S I9000 Android Development] jv.batista:
I remember reading something somewhere about nstools not being able to change governator but I can't find it anymore...
[Galaxy S I9000 Android Development] Famzz:
Re: [JB 4.2][KERNEL] CyanCore Kernel v1.1

No. Haha. Lol just joking.

You can't use it because fishears has different partition layout to kernels.

Awesomenesss!!!
[Galaxy S I9000 Android Development] saschc:
AW: [JB 4.2][KERNEL] CyanCore Kernel v1.1

Ok, I know, but I was not sure because ts1506 posted in FISHEARS 4.2.2 thread about this new kernel thread he started
[Galaxy S I9000 Android Development] METEMEDO:
First of all, thank you very much for all of your work.

Now i have a suggestion:

There is a tweak (that i never tested) called Loopy Smoothness that seems to fix the overall responsivity of the phone by setting the process priority higher for the really important stuff, like receiving calls and such. Could you include it on the kernel (if it is actually good, i don't know).

And now i have a question (sorry for posting it here):

If i set the limit background processes, will it kill only user-processes or all the processes, like SMS and Phone listening? Is it stable?

I'm asking this because my phone becomes sluggish at times and battery starts to drain.

I think that the more apps we have installed, the more "auto-starts" (or sevices) we will have in the background.

Multi-tasking is nice, but sometimes i wish i didn't have it.
[Galaxy S I9000 Android Development] ts1506:
1. Loopy Smoothness is a init.d script , with nothing to do with kernel. But it doesnt improve performance in JB , cause ADJ cant be set via VM tweaks, they are hard coded in services.jar

2. Limiting background processes is not recommended, they tend to cause more lag.

3. Try using Autostart Manager and disable the receivers.
[Galaxy S I9000 Android Development] ts1506:
New CyanCore Kernel 1.2 released

Changelog in 2nd post.

Currently Kernel has 397MB minimum RAM.

I have a option to remove a few stuff (KSM,ZRAM and SWAP) and gain back 1MB more RAM , so its upto you. As it is 1MB doesnt go a long way.
[Galaxy S I9000 Android Development] empulse92:
get 1 mb ram and loose some cool features that could be included? sir, this isn't a fair deal :laugh:
[Galaxy S I9000 Android Development] ts1506:
Even I dont prefer loosing KSM. After enabling KSM , 1MB of RAM is lost , making RAM 396MB , and I disabled kernel debugging to gain back 1MB of RAM.
[Galaxy S I9000 Android Development] Tsipo:
Re: [JB 4.2][KERNEL] CyanCore Kernel v1.2

Thanks for making all these nice features possible on the best SGS Kernel (semaphore)! Just one question regarding SWAP: How can we enable/disable it, or set the size, partition etc?

Thanks in advance...
[Galaxy S I9000 Android Development] monish1995:
am using Mackay right now and

Changed values and Set OverClock , my phone got stuck and rebooted , i checked the changed settings and i cud see tht they reverted back to old values ,
[Galaxy S I9000 Android Development] pamarakos:
+1

Plus where is the performance governor?? :)
[Galaxy S I9000 Android Development] blusydays:
Hi, can you add Voodoo color to your Kernel, or make two versions, one with VC and another without ?
[Galaxy S I9000 Android Development] ts1506:
I have compiled the performance and powersave governors as modules instead of inbuilt governors , you can load them via a insmod command.

I did this cause I see no practical usage of these governors.

Try using Swapper2 . I personally didnt try SWAP , so dont know whether it will work fine or not.

I will look into it later.
[Galaxy S I9000 Android Development] Facebooook:
Re: [JB 4.2][KERNEL] CyanCore Kernel v1.2

Thanks for accepting my reqest regarding swap.

how to live oc above 120 level by semaphore app.
[Galaxy S I9000 Android Development] ts1506:
Use NSTools , the modded fishears version.
[Galaxy S I9000 Android Development] stratosk:
We use powersave in lpm mode when the phone is off in the charger.
[Galaxy S I9000 Android Development] pamarakos:
Re: [JB 4.2][KERNEL] CyanCore Kernel v1.2

Benchmarking only:)

You have said you were using performance this way before so from back then I did the same:)

Anyways...thanks!
[Galaxy S I9000 Android Development] ts1506:
Ah well , I will include them , and build one today.
[Galaxy S I9000 Android Development] ts1506:
CyanCore 1.3s uploaded . Same as CyanCore 1.2s but with a few corrections in the code and re-enabled Performance and Powersave governors.
[Galaxy S I9000 Android Development] Cu8eR:
So SWAP is disabled by default, am I right? Because many of us dont use SWAP... I dont like it
[Galaxy S I9000 Android Development] arjiegodz:
ts these are the needs i think in order to modify the kernel so that it would be compatible for our fone. can u help us about this? If this isnt the one. just say so

kernel

https://github.com/didhiy/android_kernel_samsung_aries

ramdisk

https://github.com/didhiy/ramdisk-sc02b
[Galaxy S I9000 Android Development] solar666:
Yes, some pages back. You need to fix permissions on the nstools app
[Galaxy S I9000 Android Development] arjiegodz:
happy bday ts!!!!
[Galaxy S I9000 Android Development] .:Crack:.:
Hey TS,

accoring to github the row-iosched.c you are using isn't the latest. You can find the updated version in the source of faux123's and franco's mako kernels. Hope you have enough time to update!

Selective liveoc has a bug from what ive tested... e.g. set target low to 400mhz: using liveoc 124% this results in 496mhz+ and 200 mhz. these 200 mhz sometimes jump to 248mhz and then jump back to 200 eventhough they should always be 200 (not liveoc'd)

other than that the kernel is running fine as always! thanks.
[Galaxy S I9000 Android Development] ts1506:
I will have a look at ROW updates , thanks for info.

Selective Live OC code seems okay , still I will check with other kernels.
[Galaxy S I9000 Android Development] .:Crack:.:
No problem!

Well it's not a big problem for me, I just set target low to 100MHz, effectively disabled selective LiveOC. Just wanted to inform you!
[Galaxy S I9000 Android Development] Arkanoide:
I'm sorry if this was already said, can i use semaphore manager to manage CyanCore kernel ? Or only nstool ?
[Galaxy S I9000 Android Development] habylab:
Either!
[Galaxy S I9000 Android Development] ts1506:
Use NSTools modified one, it is attached in OP.

Dont use Semaphore Manager, it lacks all the options.
[Galaxy S I9000 Android Development] Arkanoide:
Your kernel doesn't work with the liquidsmooth v2.6 (maybe it is my phone ^^). My phone freeze just after the boot and reboot in recovery. I don't know why, maybe it is link to the script to manage the ram. (http://xdaforums.com/showthread.php?t=2273317)

I set the config in semaphore manager to default before the flash.

I come back to semaphore because of the problem.

Anyway, thanks for your kernel ;)
[Galaxy S I9000 Android Development] ts1506:
Delete Semaphore Manager , delete Fly On script.

In recovery , wipe init.d , wipe NStools settings , wipe Semaphore Manager settings.

Flash Kernel , clear cache and dalvik cache.

Reboot.
[Galaxy S I9000 Android Development] Arkanoide:
With the wipe init.d, it works ;)
[Galaxy S I9000 Android Development] Wolffeh:
How do I enable bigmem? It's not an option in NSTools. TS1506 mentioned a script in the OP which I assume is this?

#!/system/bin/sh

# CyanCore Module loader script

# CIFS

# insmod /system/lib/modules/cifs.ko

# Logger

# insmod /system/lib/modules/logger.ko

# UHID

# insmod /system/lib/modules/uhid.ko

# USBHID

# insmod /system/lib/modules/usbhid.ko

# Xbox Pad

# insmod /system/lib/modules/xpad.ko

# Mouse

# insmod /system/lib/modules/mousedev.ko

# FM Radio

# insmod /system/lib/modules/radio-si4709-i2c.ko

# config.gz

# insmod /system/lib/modules/configs.ko

# Bigmem

# echo 1 > /sys/kernel/bigmem/enable

What do I do with it, and where do I place it?
[Galaxy S I9000 Android Development] ts1506:
Uncomment the last line, save the file in init.d with rwxrwxrwx permissions.

Reboot twice
[Galaxy S I9000 Android Development] ts1506:
Wow, lagfree governor is really smooth, check it out.
[Galaxy S I9000 Android Development] compacity:
can be used with fly on script?, i thought maybe it will clash. n can this core be use in infamous aokp? think i might try it, but dont wanna brick it, wanna rest from flashing with odin, sorry if i ask too much
[Galaxy S I9000 Android Development] ts1506:
Kernel can be used on any 4.2 ROM.

It should work with Fly On , but I dont recommend it.
[Galaxy S I9000 Android Development] ts1506:
CyanCore Kernel v2.8.0 uploaded and attached to OP

Changelog

1. Updated Linux Kernel v3.0.83

2. Fixed ZEN.

3. PVR Microkernel Trace debug disabled

4. Updated PowerVR Driver to DDK 1.8@2198402

5. Optimized O3 Flags

6. Improved ASync I/O Latency

7. Deadline tweaks

8. Interactive tweaks

9. ROW updates
[Galaxy S I9000 Android Development] KSLevel11:
How is the performance of new GPU driver?
[Galaxy S I9000 Android Development] Alberto96:
I just see some little improvements in 2D Performance. 3D is still the same.
[Galaxy S I9000 Android Development] osm0sis:
Hi there. Cool to see another device is benefiting from the work we've been doing over on the Galaxy Nexus and Nexus 7, but if you're going to include the tweaked scheduler values researched and tested by the "Franco's Dev Team" tuning collective, then please also provide credit. That's all we ask. :good:

Please also provide credit on your other kernels where you've used them. Keep up the good work. :)
[Galaxy S I9000 Android Development] ts1506:
Sure, I will update the credits when I get to my computer. Sorry I forgot to do it earlier.

Sent from my Lumia 510 using Board Express
[Galaxy S I9000 Android Development] mishulake:
Please sens us a link!
[Galaxy S I9000 Android Development] ts1506:
Link to what ?
[Galaxy S I9000 Android Development] Qkret:
hmm i think a link for CyanCore 2.8.1 :)
[Galaxy S I9000 Android Development] ts1506:
CyanCore 2.8.1 is nothing but 2.8.0 compiled with a newer toolchain version, thats why its not released.
[Galaxy S I9000 Android Development] ts1506:
CyanCore Kernel updated to 2.8.3

Changelog

1. Updated Linux Kernel v3.0.84

2. Dynamic FSync support added

3. Fixed calculation of Load_freq

4. Ondemand updates from Semaphore

5. RCU updates

6. Small fix to SQLB

7. Optimized GPU compile flags

8. Wifi Driver updated

9. Compiled using Cortex A8 Linaro 4.7.4 2013.06
[Galaxy S I9000 Android Development] herc2k:
hi can u make a version like devil kernel ? more ram but without video and camera function?
[Galaxy S I9000 Android Development] Qkret:
great idea :) but more work
[Galaxy S I9000 Android Development] ts1506:
No, not at all. Camera is a basic need for me. In 439MB version , video playback , and in general , games dont work too.
[Galaxy S I9000 Android Development] herc2k:
like devil you can activate the 439 mode when you want and deactivate
[Galaxy S I9000 Android Development] FREEKR:
Dude you rock!

The dynamic fsync is the improved version of faux123?
[Galaxy S I9000 Android Development] ts1506:
Yes, the latest code from faux123.
[Galaxy S I9000 Android Development] Bejda:
Would have to be tested by provoking a crash/freeze and force reboot maybe?

You remember reports on Helly Bean thread and all, I wonder if it's ok for everyone now with that "fix". And anyway would be interesting to see if it behaves well on such situations.

I'll try anyway, as I was having issues when it happens but nothing bad it won't hurt me to test.. The hardest part is to provoke the crash (antutu maybe..tried already?..maybe those antutu crashes were related to fsync first?)
[Galaxy S I9000 Android Development] ts1506:
Devil still uses the old code.

If you can give me an idea of how to "cause a crash" , then I would be happy to test. Antutu works fine .
[Galaxy S I9000 Android Development] nereis:
Quite easy actually, I got data corruption from a few versions back playing with uv while stress testing.

Apparently software decoding 720p videos is really hard work for our phones.
[Galaxy S I9000 Android Development] ts1506:
Few version back of what ? CyanCore ?

CyanCore didnt have Dynamic Fsync in the older versions , only in 2.8.3.