yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Val D.:
I don't see any noticeable performance differences with KSM enabled so no need for me to mess around with scripts.
[Captivate Android Development] ghoster76:
If it doesn't have advanced point, why KMS appeared like a function on Performance Setting?

Or just a joke of developers, you don't like this but the others like it
[Captivate Android Development] Val D.:
What I said is that

I don't see

any noticeable performance differences

on my phone

, therefore

I'm not going

to spend more time on this issue. If you feel it is critical for you, then go ahead and find a solution that works

for you

. I found my solution already. zRam also appeared at one point, but it actually slows down Captivate. Try it enabled/disabled and see for yourself.

As I mentioned earlier in one of the threads, every single byte software after stock Samsung ROM is a free advantage for Captivate users. I can point a problem that I see

on my phone

, but I don't feel in position to request any special fixes/changes from the developer. This guys already spend a lot of their free time to make us happy. And

I'm happy

with what I have after stock ROM.
[Captivate Android Development] cannondaleV2000:
I might be able to modify the app from stratosk source. No garentee though
[Captivate Android Development] laughingT:
actually, system tuner app has an option to apply tweaks via init.d, no need for java knowledge. the app supports voltage and oc tweaks, sys control, etc. you can choose to apply via init.d or on boot completed.

sent via carrier pigeon, jungle drums and smoke signals.
[Captivate Android Development] Val D.:
Hmm... restored my Slim3 backup and flashed 21sc kernel. Now KSM setting is sticking after reboot. Previous ROM was Xylon 2.3.3, wasn't working there.
[Captivate Android Development] Nick0703:
Can you do something for me please? Can you go to "/sys/kernel/mm/ksm/" and open the "run" file and tell me what value is in it? Is it a "0" or "1"? Thanks!
[Captivate Android Development] Val D.:
I'm currently running Xylon 2.3.3, kernel 21c, KSM enabled after boot, and /sys/kernel/mm/ksm/run value is 1.
[Captivate Android Development] ghoster76:
KSM don't enable is causing by this Rom, I'm running newest Devil kernel and have the same issue like Semaphore kernel
[Captivate Android Development] Val D.:
This particular ROM Xylon 2.3.3 + Nick0703's Semaphore is causing my phone to run faster than any other Captivate ROM I have tried on XDA. And I have tried them all, one by one. I don't care much about kernel settings, I do care about what I see on the screen. And there is a visible difference in UI speed compared to many other much popular ROMs.
[Captivate Android Development] ngochuy:
Any updates for this kernel? Semaphore already released a new version.
[Captivate Android Development] Nick0703:
I'll update it tomorrow if I have the time.
[Captivate Android Development] Nick0703:
New Update 2.9.23c

New update is up. JB_2.9.23c

Changelog:

- Linux kernel 3.0.75

- UHID built as module

- UHID implementation (thanks to pawitp and n8r for merging it to Semaphore)

- CWM 6.0.3.1

- Updated ROW parameters (Thanks to kasper_h)

- Use XZ compression method for both Kernel and Ramdisk

- Fix Memory Leak

- More under the hood tweaks. (Check Github for more detail on commits for Apr 19, 2013)
[Captivate Android Development] mrsubway:
I'm running this Kernel with Slimbean and phone is butter. The Voodoo color with suggested settings in op is beautiful.

Sent from a heavily modded Cappy from parts unknown. Slimbean/Semaphore. FTW.
[Captivate Android Development] spacecase-25:
I'm having trouble enabling ZRAM. I've turned it on (18%) in performance settings, but zram status (app for showing zram stats) shows no data and my devices still runs out of memory causing the home screen to restart after leaving apps. Any ideas? Thanks.
[Captivate Android Development] Nick0703:
I think there is a bug with the Zram not being properly enabled from the performance settings. I'm gonna take a look at it.
[Captivate Android Development] cannondaleV2000:
What ROM are you running
[Captivate Android Development] spacecase-25:
slimbean
[Captivate Android Development] cannondaleV2000:
zram

hey anyone haveing trouble with zram here are some scripts in the zip below.DO NOT FLASH EXTRACT FIRST THAN push to /system/etc/init.d and than abd shell get su shell and chmod the correct permisions. if you want modifyed scripts with custome sizes pm me and il make them as i dont want anyone makeing them wrong and than complaining about zram not working
[Captivate Android Development] spacecase-25:
When I launch zram status I get "invalid int: "17592186064896"
[Captivate Android Development] Nick0703:
I'll post a different script in the afternoon. Check if that one works.
[Captivate Android Development] cannondaleV2000:
Its working fine for me. Just adb push to init.d folder and set correct permission
[Captivate Android Development] mik101:
Edit. It has been fixed already. :)
[Captivate Android Development] spacecase-25:
Finally got around to partitioning my SD card for swap, and all I can say is "LOOK AT ALL THE THINGS RUNNING IN THE BACKGROUND"
[Captivate Android Development] sleeper994:
I have class 4 sd card, how is swap gonna work on that???
[Captivate Android Development] mindphaser2k9:
Will work quite bad.
[Captivate Android Development] ih8legal:
Which one should I use with the PAC MAN ROM the s version or the normal version?
[Captivate Android Development] Nick0703:
You can use any version that you want. But if you're using the "s" version then you'll need to flash HugeMem libs also.
[Captivate Android Development] Nick0703:
New Update! JB 2.9.25c

2.9.25 (14/05/2013)

- Linux kernel 3.0.78

- Auto brightness: max_lux up to 6000

And also future update might come a bit more slower now as I changed device. I gave my Captivate to my mom so hopefully she'll lend me it in the future to test new versions.
[Captivate Android Development] ih8legal:
Deleted
[Captivate Android Development] Kyuta Syuko:
Why not ask for volunteer testers who know how to use logcat?
[Captivate Android Development] Nick0703:
Can you be one of the volunteers?:)
[Captivate Android Development] m1batt1:
I could be.
[Captivate Android Development] Kyuta Syuko:
I'm no good with logcat unfortunately and I generally don't have the time to devote to really pushing my phone and looking for bugs/issues sorry.
[Captivate Android Development] mik101:
Goo.im seems to be having some issues from here.

Any chance anyone backed up the 2.9.25sc? The one without voodoo color ideally. I thought I had a copy on my SDcard but I must have been mistaken.

Thanks guys.
[Captivate Android Development] dave71670:
Try this. Hope it is OK with op that I posted here.
[Captivate Android Development] mik101:
Awesome thanks! If nick has an issue with it I'm sure hell just ask you to remove it. Reposting helped me out. :)
[Captivate Android Development] Nick0703:
Lol I have no problem with it. :)
[Captivate Android Development] aliver.dun:
hI Nick,

I saw the kernel 2.9.26 is come out at I9000 forum,so can you help to make unoffical one for our captivate ,thanks a lot...BTW,I use your kernel all the time and it is so awesome and stable...
[Captivate Android Development] Nick0703:
I'll try to compile one today.
[Captivate Android Development] aliver.dun:
Thanks a lot,man..
[Captivate Android Development] Nick0703:
It looks like the latest version isn't compiling for me. I'm getting some errors about the additional CPU governors (Wheatley and IntelliDemand)......
[Captivate Android Development] aliver.dun:
i believe you can do this as you are the best ~
[Captivate Android Development] mrsubway:
Damn Governors! They sit in the State Capitol and abuse Devs! Attica! Attica!

Sent from a heavily modded Cappy from parts unknown. Slimbean/Semaphore. FTW.
[Captivate Android Development] eduardo_b:
Where are other governors

Flashed current (2.9.25c) over Slim version, wiped cache/dalvik, but don't see additional governors using Semaphore Manager. That said, should I just stick with Conservative for best battery (with noop)? Is it okay to use other kernel apps, such as Trickster or setCPU with this kernel instead? Battery on my two S3s better than on this S (which I only use for music these days).
[Captivate Android Development] Nick0703:
Yeah, you won't be able to see the additional governors via Semaphore Manager. You will need to use another cpu tool app for that. And yes those apps should be good.
[Captivate Android Development] Nick0703:
2.9.26c

New update is up!
[Captivate Android Development] aliver.dun:
you are one hero,,,:thumbup:
[Captivate Android Development] They Drew First Blood:
Re: music

Enabling Deep Idle will help the most if you only use the device for music. Take a look at the latter three links in my signature: "Tweaks", "Battery" and "Governors/Schedulers" for a nice look at governor and usage options. Conservative governor is not that great for battery-saving, it turns out. Personally I like SmartassV2 and noop. I listen to a lot of music too, and run wifi and some games but nothing else.
[Captivate Android Development] eduardo_b:
You running this kernel, official Semaphore or...with Semaphore Manager or...?

I can't find an I897 kernel that has many of the governers/schedulers common to S3 kernels. There's one governor, nanolunch, on dkp kernel for S3 that really is excellent for battery with screen off.
[Captivate Android Development] They Drew First Blood:
Re: governors/schedulers

I don't know how many developers are active in both communities, so there are going to be kernels that are unavailable for Galaxy S; and also some of those kernels are for multi-core devices only anyway. Nick was having trouble compiling recently so in the meantime I had been running ts1506's latest kernel (also based on Semaphore) but now I am on this 2.9.26c version (thanks again Nick :good: ). I use both Semaphore Manager and NSTools- sometimes they conflict with each other but they are fine for the moment. Some of the governors are visible in Semaphore Manager and others in NSTools; if the governors section is grayed out and inaccessible in NSTools just do this: using Root Browser or similar app navigate to /datadata/mobi.cyann.nstools/ and update the permissions on preload.prop file to rw-r--r-- and the governors will then appear in NSTools.

---------- Post added at 04:41 PM ---------- Previous post was at 04:10 PM ----------

Probably should not use both though... I realize I have a different governor set in each...I think NSTools is the one that is applying correctly so I am going to disable Semaphore Manager for the time being
[Captivate Android Development] eduardo_b:
Okay, I've removed Semaphore Manager (and Trickster, which I replaced it with) and installed NSTools. Had to fix prop to see governors, but your recommended SmartassV2 isn't to be found. Is that only in official Semaphore (if even there)? Also don't see deep sleep, although I have DS Battery for that, so I suppose I don't actually need that option in kernel tuner (I think Semaphore Manager does have it).

I'm not super into tuning kernels for battery because the differences are typically minimal for screen off, and UVing can make things worse by slowing down processes, plus any instability that results in FCs uses 2 to 3 percent of battery for reboot. My S3s get between 0.6% and 0.7% per hour with screen off (along with wifi, bt, data turned off). I don't think I've gotten close to this with S, but I could get closer with governor/scheduler that function best with screen off and music on...as you note.
[Captivate Android Development] Kyuta Syuko:
Because they're compiled as modules some governors such as SmartassV2 can only be selected using Semaphore Manager. Also you can only adjust LiveOC using Semaphore Manager afaik as well as tweak a few other options (other then voltages since Semaphore Manager isn't setup to support step OC) so you should reinstall it.

I'd also like to state that I've heard some say Deep Idle may cause sleep of death so be aware of that.
[Captivate Android Development] Val D.:
We'll never get close to S3 idle power consumption with our 3y old hardware, no matter how optimized the kernel is.
[Captivate Android Development] They Drew First Blood:
Re: governors

Apologies for any confusion... yes, I ended up seeing NSTools did not show SmartassV2- as I had posted that I was trying out lulzactive which Semaphore Manager did not show and had not checked NSTools. Over the past few days I had initially gone back to the combo of Semaphore Manager / Voltage Control Lite, searching again for these types of apps that are comprehensive. It is tough because I have used NSTools for such a long time due to its access to both ARM and INT voltages- occasionally I would have to tweak 100MHz voltage slightly higher, to avoid the Sleep Death in Deep Idle state that Kyuta Syuko mentions. You can enable/disable Deep Idle in both Semaphore Manager and NSTools, under CPU tab for both apps. After setting SmartassV2 in SemMan and verifying with Voltage Control, I cleared NSTools data in the recovery menu, rebooted, restored NSTools, and it now shows SmartassV2 among the governors. I agree with your tuning/FCs comments, and I use DS Battery Saver as well and it works great at Aggressive setting. I only have to turn DS off momentarily if I am downloading something, else it kills wifi when the screen goes off.
[Captivate Android Development] aliver.dun:
hi nick.

the version 3.0 for 9000 is out,can you help to port it to our device....thanks..
[Captivate Android Development] Nick0703:
Yes, for sure I'll update it.:)
[Captivate Android Development] They Drew First Blood:
Re: 3.0

Nick goes above and beyond just porting, he builds it from source. If you are itching to run the 3.0, stratosk released it for the Cappy yesterday afternoon a few hour after Nick's post.
[Captivate Android Development] Nick0703:
Stay tuned guys. A massive update is coming.
[Captivate Android Development] mrsubway:
It'll be worth the wait as usual!

Sent from a heavily modded Cappy from parts unknown. Slimbean/Semaphore. FTW.
[Captivate Android Development] Nick0703:
If everything works out to be good, I'll release them tonight. But I'd rather do some testing first as new stuff got added etc... I want to make sure that they work perfectly.:good:
[Captivate Android Development] Nick0703:
New Update. 3.0.0c

New version 3.0.0c

Changelogs:

- gpu: pvr: Update to DDK 1.8@2198402

- net: wireless: bcmdhd: Update to version 5.90.195.104

- cpufreq: ondemand: Drop early demand

- UHID built as module

- CWM: upstream updates

- new version AromaFM 1.90 (thanks to amarullz)

Changes by sUsH667 (many thanks) :

- base updated to aromafm 1.90

- deleted all languages except english

- deleted all iconsets

- deleted all fonts except roboto

- added german language

- added iconset "generic" from older aromafm-version

- added preconfigured config

- added bookmarks for often used folders: /system, /sdcard, /emmc, /sdcard/Download

Custom Features:

- Linux 3.0.85

- BrazilianWax CPU governor

- Adaptive CPU governor

- Hyper CPU governor

- InteractiveX CPU governor

- Lioneheart CPU governor

- OnDemandX CPU governor

- Lagfree CPU governor

- V(R) IO Scheduler

- FIOPS IO Scheduler

- Remove BFQ Scheduler

- Dynamic FSync

- Massive update to IO schedulers

- SLQB memory allocator
[Captivate Android Development] ih8legal:
Quick question is it possible that a kernel can affect your cell signal either positively or negatively?
[Captivate Android Development] tork0112:
I may be wrong, but I notice differences in mine, between using different kernels.
[Captivate Android Development] Nick0703:
Hmm, I don't think that a kernel can affect your cell signal. I do know that changing the modem will affect your cell signal either negatively or positively.
[Captivate Android Development] tork0112:
Strange. For whatever reason. I tend to get better signal, in the same place, with semaphore vs devil kernel.
[Captivate Android Development] ih8legal:
In that case are there any modems available for the captivate? And which one in your experience has worked the best?
[Captivate Android Development] Nick0703:
This thread might help you. http://xdaforums.com/showthread.php?t=1227717

And for me I used the I9000UGKG3, but it really depends on your location. YMMV.....
[Captivate Android Development] whisky23:
Just to be sure...3.0.0c is on kernel 3.0.85, not 3.0.84? That would explain why it's not playing nicely with Slimbean 4.2.2 Build 8, which is on 3.0.84, as is the original 3.0.0c.
[Captivate Android Development] Val D.:
SC version is for Slim ROMs.
[Captivate Android Development] whisky23:
Yup. I'm aware of that. My question was on the kernel version as the latest unofficial semaphore doesn't work well with Slimbean 4.2.2 build 8.
[Captivate Android Development] ~wolverine~:
nevermind
[Captivate Android Development] Val D.:
What doesn't work well?
[Captivate Android Development] whisky23:
Lag. FCs. Reboots. This is before any OC. Didn't have any of these problems until v3.0.0c (or sc). Will try the previous version, though that is on kernel 3.0.80 while the latest slimbean's semaphore is on 3.0.84.
[Captivate Android Development] murphy504:
Rapid battery loss on CM 10.1 4.2.2 Nightly
[Captivate Android Development] mik101:
It's just your setup or a rogue app, and without more information we can't help you. Mine only uses about 2% per hour idling using this kernel and last nights nightly.

Just to warn folks. The latest Nightly posted Aug 14th are CM10.2 = Android 4.3, so watch your version numbers. At this time I don't know if this kernel will work with anything newer than the Aug 13 nightly (10.1). So NANDROID backup people if you're going to try!

Going to try it out in a bit and will report back.
[Captivate Android Development] cannondaleV2000:
Won't work on 4.3 needs updated ramdisk and selinix support and a few other things
[Captivate Android Development] mik101:
Thanks for the heads up.

Has anyone here tried the 10.2 nightly in general yet? I didn't see an unofficial thread like in the i9000 forums. Maybe the 10.1 thread just hasn't been renamed yet. I haven't been on here too often lately.
[Captivate Android Development] murphy504:
I did backup so no big prob there. I'm on the Aug 10th nightly. I always have: bluetooth &gps off, don't use mobile data, brightness always on its lowest as much as possible, network on 2G, yadda yadda (all the obvious battery saving stuff). Cell standby always takes up most of my battery life (Baseband KK4 drops often but works) & I don't tweak anything with the cpu. But after about 20mins on the kernel my battery dropped 10%. I use my phone basically all day & it overheats all the time. Only social media, free calling and texting apps are installed.

So any guidance with a kernel that saves battery life would be appreciated. I can give more info on whatever you need.
[Captivate Android Development] mik101:
Yikes, with so many things off I'm not really sure what to point at. I use the KG3 baseband, but obviously the best for each carrier/area is going to vary there. I'm on wifi 90% of the time, data set to 2/3g automatic and I use 120mhz-1320mhz w/smartassv2 governor. Normal use the phone lasts about 8 hours without a long of long idle periods (my number above would be just idling), but it depends on how much im flipping on the screen to thumb through facebook. I don't do a lot of voice calling either.

Trying out the 10.2 nightly right now. It will be nice once all the details are ironed out. With all the effects turned on the poor cappy definitely struggles. No real surprises. A few minor tweaks in appearances here and there, focal will be interesting once it locks up less. I'm going back to the 10.1 nightly from last night so I can go back to my configuration above. At least for now.
[Captivate Android Development] Darian71:
Just installed and running the 8-15-13 nightly 4.3.Seems alot smoother and very responsive. Am waiting to try this kernel as I don't know if it will work with 4.3. My cappy also got quite warm running this kernel on 200/1200mhz. And now on this latest nightly from Cm she's running pretty warm with the same mhz settings. Hence the hesitation to try our favorite kernel. Please let me know if anyone has tried. About to try out focal and other things. Oh, can anyone tell me what the SElinux setting is for? It has a Permissive and Enforcing option by clicking the name 3x:good:
[Captivate Android Development] prbassplayer:
Hehe SELinux is the biggest pita that's what it is.
[Captivate Android Development] mik101:
Semaphore for the i9000 is now at 3.1 including support for Android 4.3 (CM10.2 etc.) ;)
[Captivate Android Development] Nick0703:
An update should be up within the next few hours. :)

EDIT: Having problem booting up. Will have to check again
[Captivate Android Development] ajeesh vijayan:
nice work...waiting for unofficial 3.2.0c for pacman..not asking for ETA..
[Captivate Android Development] Nick0703:
JB4.3 Test Builds

THIS IS A TEST BUILD!

Alright guys, so I made another test build and I couldn't test it on my captivate as I'm away from home. So if this doesn't boot or can't get back into recovery, you'll need to get into Download Mode and flash a kernel through there.

Report back to me if it's working.

EDIT: NOT WORKING.
[Captivate Android Development] Nick0703:
Can I get a feedback please? Like is it working or not?
[Captivate Android Development] elbonnor:
Gonna flash now. Will report back.

---------- Post added at 04:54 PM ---------- Previous post was at 04:31 PM ----------

Wiped cache and dalvik cache and flashed over latest Slim 4.3 weekly. Stuck at Semaphore logo, cant boot into recovery. Odin'd official Semaphore to get back running.
[Captivate Android Development] Nick0703:
Alright, thanks for the feedback. I'll look into it.
[Captivate Android Development] brezulja:
Hi, i am using Slim beam 4.3.1 which verson of unofficial Semaphore do i need? Non of the download links work?
[Captivate Android Development] Nick0703:
Poll added to the thread. ;)

Waiting for the results now.....
[Captivate Android Development] mindphaser2k9:
Thank you very much, I can say my phone never was so fast and responsive before as with this kernel, 1200oc+ZRAM :good:

I have voted for VC but seems that feature is not too requested by others. I think VC colors are better but those green blinks make it not so desirable and now CM colors look good enough for most users. So not sure if it really worth of your efforts.

What do you think about in-call volume hack instead, it was present in Semaphore some time ago (but broken)? It could be very helpful because in-call volume on Captivate is usually weak.

Also what do you think about Audience chip support (for HW noise reduction and to support Captivate modems like UCKK4 with much more volume and sound quality)? the latest kernel supports that is there http://xdaforums.com/showthread.php?t=1294477. Though I know it would be heavy to implement, so not mean to rack you with that, just want to ask your mind. Also what do you think about call recording?
[Captivate Android Development] mrsubway:
Re: [KERNEL] Unofficial Semaphore JB 2.9.9c

Have to wait until my 64gb beast comes in the mail. My poor little 16gb SD card is full!

Sent from a heavily modded Cappy from parts unknown. Slimbean/Semaphore. FTW.
[Captivate Android Development] Kyuta Syuko:
64Gb hmmm I thought the Cappy only supported up to 32Gb...
[Captivate Android Development] Nick0703:
No problem man, I'm glad you liked it. And yeah, I already compiled a Voodoo version and I'm currently testing it, all I can say is that I love it. I found a really good setting for it which offers the perfect colour without the green screen flash. And about the "In-call volume hack" it wasn't really "broken", it was creating some noise distortion so Stratosk disable it. Personally it was working fine for me, I'll compile another version with it turned ON.

But for the Audience chip support since I don't have the source code for it, I can't take a look it.
[Captivate Android Development] Nick0703:
Same here, I thought the Cappy can only support up to 32Gb?