yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RKight:
I'm running Perception 4 with 1.4.2 (1280 MHz) and it's working great. I'm loving this combo. :D

Edit: I should note, the way I did this was flash to JF6, then master clear, then flash Perception. Before I even booted for the first time, I installed my mods and the 1.4.1 CWM update zip. When 1.4.2 came out, I just flashed the CWM update zip straight over 1.4.1. It's been working without a hitch.
[Captivate Android Development] gtg465x:
No one has answered this still.

To those saying it's fine, have you tried running some 3D games like Need For Speed or Reckless Racing for any period of time at stock voltages? I have to tweak the voltages to get those games stable at 1280 but my voltage tweaks reset every time I reboot. The fact that voltage settings don't stick is my main problem with the latest kernel.
[Captivate Android Development] jhernand1102:
Its been answered in this thread...You have to copy the file it create to the correct directory...It creates it in the wrong place...
[Captivate Android Development] gtg465x:
Thanks. The solution should probably be posted in the first post. Kind of important to have a working voltage settings app when releasing an overclocked kernel. Personally I think these kernels just shouldn't have overclocking enabled by default. It should be something you enable after installing the kernel. That way those of us whose phones don't run at the overclocked settings/voltages wouldn't run into these sorts of problems right off the bat.
[Captivate Android Development] MarlowXim:
There isn't really any correct settings since each batch of chips yields different tolerances. But be sure to make a nandroid backup first before tweaking the voltages, you don't want to lose any important data if you corrupt your partitions. Personally my settings are:

100mhz -100mV
200mhz -100mv
400mhz -100mV
800mhz -150mV
1000mhz -175mV
1280mhz -100mV

Although alittle tip make sure the voltages for each stepping are higher than the previous. Processors don't work well from jumping from higher voltage to a lower. Example:

100mhz = 850mV
200mhz = 825mV

It's simply a permissions error. You have to make the directory writable /etc/init.d alternative is use a file manager that can make it writable.

Using adb shell

# su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/init.d

Then save your settings using Xan's voltage app.
[Captivate Android Development] SetiroN:
This kernel is made for the i897. Go over the i9000 forums and grab one specific for your phone.

Seriously, is it so hard to read the freaking red warnings in the first post?

Am I supposed to care? Nobody's asking you to include my kernel. Matter of fact, I don't even like that you do, so refrain from posting useless messages.

Not only you've been exploiting other people's work for months, claiming non-existent performance and stability supremacies for basically standard roms, you even have the guts to come and bash on it.
[Captivate Android Development] Sebring5:
This post earned you a donation. You deserve it. My apologies if you have been slighted in the past.

Designgears provides a valuable service. He reaches out to a different group than you. Perception Build #5 is out now with v1.4.2. I guess he figured out a way around the issues.

I'm using Killer23d's Doc_V1.2_Bell I9000UGJK3 Captivate Edition 11/25/2010 and looking for the next update for CyanogenMod 6.

Thanks for the work you do. It is very important to me as well as others and very well done.
[Captivate Android Development] Yuna:
I can confirm - i am flashing 1200 kernel, but in quadrant i can see Max Freq 1280... but still no SoD issues :) e.g sleep of death
[Captivate Android Development] warri:
/agree quadrant shows 1280... no Sleep of Death Or rebooting issues here. Only issue i have is with charing:
[Captivate Android Development] sjavvaji:
ok...with the 1.4.2 kernel...you do not need to flash the separate kernels to get wcdma 850 right...it is integrated and just have to enter the nmber?...sorry i have been out of it for 2 weeks now since i bricked my captivate and had to make a jig
[Captivate Android Development] MikeyMike01:
That has everything to do with the modem.

If you flash the new Bell modem it will work as intended without fiddling.
[Captivate Android Development] krazyphire:
Loving the kernel SetiroN! Works perfectly fine using tay's lite rom. Battery life is awesome with the new JK3 modem keep it up!

EDIT: To the people having issues if you flash roms that are as stock as possible such as Doc's or tay's you reduce the chances of internal conflicts that lead to all the issues you have. Along with reading the first post of course before flashing :)
[Captivate Android Development] Sulphur4724:
Actually, I did. And did the steps before flashing Axora 4 which included the 1.4.1 kernel. Didn't figure I needed to go through the whole thing again since I hadn't reflashed 1.3.5 nor implemented any of the lagfixes with 1.3.5 since I had gone through the steps outlined in the red text.

I was just tryin' to help out and maybe post a bug you hadn't seen. Hope you have a better day bro.

Peace.

Oh. btw i did move the uv settings file, it still didn't read it. Not tryin' to have a pissing contest here, just thought you'd like to know.
[Captivate Android Development] joeshmoe08:
Can anyone confirm which modem has better battery life (jpp or jk3)?
[Captivate Android Development] SetiroN:
You're misinterpreting: who does or doesn't use my kernel is out of my jurisdiction, Linux kernels are distributed under GPL license, I was just pointing out that I don't like it, which as far as I know I'm still in liberty to say.

His comment was completely uncalled for, it was rude and obnoxious. If he's allowed to come here and behave like that, then I'm allowed to answer to tone, especially considering the kind of person he is: what I said might have been jerky but it was the plain truth.

About the 1200 variant being clocked at 1280, I must have erroneously compressed the wrong zImage. As soon as I get home I'll reupload it.
[Captivate Android Development] Noonski:
I see that a previous warning has been given by a Fellow Moderator.

I will close the thread temporarily, so I can read a bit through it and seen if and where I need to take action.

I will reopen the thread afterwards.

But first I will make myself a Cup of Joe and watch the first episode of Misfits forcing everyone to not being able to post to this thread in the mean time. I think that for now this is a wise decision.

If I take away the tones and harsh words spoken.

What remains in the simplest form is that Setiron has stated he doesn't like that this kernel is being re used in a specific way.

He is in his right to ask for it not to be directly included.

GPL does make it hard to actually enforce this.

Luckily Having respect for each other is also a Golden XDA Rule.

Having a Kernel cooked in by default into a ROM that is not your own, does not help the development of the kernel.

Setiron can not go and check some one else's thread for issues with his optimized kernel.

I have an optimized kernel baked into my Rom, which means I have a duty to bring any issues posted by users in my ROM thread to the Kernel Thread (Richard Trips Sense Desire UVOC kernel).

And in this case Richard Trip doesn't state that he does not want cooks to use it.

What I also see in some Rom threads is that the cook supplies a link to a different optimized kernel with a link to the kernel thread.

This way less experienced and less likely to post users are protected from themselves having a more stable ROM.

I believe this is a good solution for DG to use on his Perception build.

(separate Download link with link to thread that asks for feedback on that thread)

If the above method would have been used to begin with this thread would have been a lot cleaner.

I will not go through all 120+ pages to clean up this thread.

(Misfits is kind of cool)

But if Setiron feels there are specific posts that can be deleted to bring more normalcy back to the thread.

He can report those With the information "Pleaser delete without action to user"

Or send me a complete list of the Post numbers to delete.

I will add a few infractions to a few users without direct repercussions (Unless I find a user has had other refractions before)

The thread is re opened, but any more bull**** while I'm still working on it will result in a 3day Ban.

I also do not need to hear if you agree or disagree with my decision/solution.

Unless you are Setiron or DG and do it through a PM.
[Captivate Android Development] crazililazn:
>< I did exactly what it says in the OP, but I can't get 1.4.2 1280 kernel to save UV settings. I mounted it as R/W and it still won't work :/

I just did a straight flash over 1.4.1, resetting UV settings before the flash, and I can't get it to work. 1.4.1 was able to apply the UV settings on boot, so is it just a bug with 1.4.2? Also, when I use Root Explorer to look into the etc/init.d folder, the S_volt_scheduler is there, so this just makes me even more confused. It's like UV script isn't being read on boot, even though it is there :(

Anyone can help on this?
[Captivate Android Development] bts0uth:
1.4.2 is working perfectly just like previous releases. I have tried the XT version a couple times and for some reason when I open Vignette it just freezes on initiating camera and I have to pull battery. As soon as I flash back normal 1.4.2 it opens instantly. Seems odd that XT version would somehow affect vignette not opening. I couldn't find any issues other then that.

SetiroN your work is amazing and I've been a fan since your first release. Your kernel is obviously the best option any captivate user has.

Posted from my Captivate running Axura beta 4 with SetiroN's SuperOptimized kernel 1.4.2
[Captivate Android Development] MarlowXim:
It has something to do with the rom. I think your using Axura a Jk2 based rom. 1.4.2 XT does not execute the init.d directory scripts in JK2 but it works on a JK3 based rom. Odd bug I found. You should be okay using 1.4.1 it seems compatible with that version. It could be rom related haven't managed to figure it out yet.
[Captivate Android Development] shaolin95:
Or you can just not use the kernel and keep the one that came with your Rom or do you own, seriously.
[Captivate Android Development] gtg465x:
It was a suggestion that would benefit less experienced users. I was able to get the issues worked out, but others may not be able to and might screw up their phones. Am I not allowed to make suggestions?
[Captivate Android Development] crazililazn:
Nope. I'm using Perception Build 4 which is a JK3 based rom :( but yes, 1.4.1 worked fine, so i will fall back to that for now.
[Captivate Android Development] cruiserbax:
+1, if person x is not savvy enough to work through such stumbling blocks then person x should probably not be flashing it, BUT with that said we all know that person x WILL try to flash it. If you have OC/UV disabled be default that just means they will run into issues trying to enable that stuff instead of when disabling it. so the problem will still be there one way or the other when it comes to inexperienced users.
[Captivate Android Development] gtg465x:
There are clearly a couple issues that are not due to user error. Setiron accidentally uploaded the 1280 variant as the 1200 variant and oc/uv settings don't seem to be persisting after reboot on some ROMs when they did on 1.4.1.
[Captivate Android Development] joeshmoe08:
Which has better battery life: jpp or jk3 modem?
[Captivate Android Development] MarlowXim:
I'm using Jk3 as well but i'm not using his rom. I'm using my own custom rom. Try docs rom I believe he made a port to captivate on jk3. See if you get the same issues.
[Captivate Android Development] gtg465x:
I just think it would reduce the number of complaints. At least if users didn't run into problems until they tried to mess with oc/uv settings they would know it was their own fault and not a problem with the kernel. For some of us the stock voltages set by this kernel are too high and our phones freeze before we even get the chance to set appropriate voltage settings. It's up to Setiron in the end. I was just providing a suggestion.
[Captivate Android Development] crazililazn:
Reflashing everything >< Ugh, I'm not a fan of restoring all my stuff, so I think I will just wait this one out since 1.4.2 does not have any big changes that I may want or notice :]

Thanks for the suggestion tho :]
[Captivate Android Development] cruiserbax:
I don't ignore sound logic or reason and that makes sense, I still stand that there will always be those complaints/questions from inexperienced users but in-fact what you said is true, the point about getting to a place where you can set the OC/UV settings at all is enough to agree. anyways I think it's to early, I shouldn't post before 1000 lol
[Captivate Android Development] SetiroN:
Correct v1.4.2 clocked at 1200MHz uploaded.
[Captivate Android Development] double RL:
Personally, I have been getting really good battery life since switching to the JK3 modem. I had an issue with call quality earlier this week and the phone not releasing towers properly but it went away after a modem reflash. I just flashed the 1.4.2 xt kernel last night and all still seems good. So far the JK3 is really good imo. I can toggle 3g off with it and not lose WCDMA 850 for good.
[Captivate Android Development] cruiserbax:
Love the toad! and Futurama! oh and also your work! The best (for me) Kernel out there!
[Captivate Android Development] gtg465x:
Anyone have the 1.4.1 builds they can upload? Would like to do some testing. I still can't get uv settings to stick after reboot with JK3 despite setting correct permissions on the init.d folder and making sure the correctly set file is located there. Thanks.
[Captivate Android Development] SetiroN:
Try the updated 1.4.2. :)
[Captivate Android Development] smokestack76:
I think most are in my 4shared.
[Captivate Android Development] KaLiBLeeK:
Oddly enough, I just flashed 1.4.2 over 1.4.1 (the 1280 versions); I had gone to the Voltage app and cleared settings before flashing, but I forgot that I had to manually move the UV script on 1.4.1...and my UV settings were still in there after 1.4.2 was flashed. Haha. I'm assuming the app just cleared the original script that had to be moved manually, and my file remained in the init.d folder. Not sure if that's helpful, but yeah.

Only issue I've run into is the custom bootanimation isn't working for me now; tried putting the zip back into system/media after flashing 1.4.2...no dice. Just a black screen. Gonna delete that file now and reboot to see if I get the stock Samsung one. But aside from that, I seem to have upgraded with no ill effects...*knocks on wood*
[Captivate Android Development] gtg465x:
Hmm, after rebooting I still see the correctly set S_volt_scheduler in the init.d folder, but when I open the voltage settings app (1.98b) it shows stock uv settings and based on freezing, the uv settings are not getting applied on boot. Any suggestions?

edit: Same thing with 1.4.1. So it seems something changed in this regard since 1.3.5. With 1.3.5 the uv settings would load on boot just fine. Guess I will just continue to apply my uv settings after every reboot, but I would really appreciate it if you could help me out or look into the issue. Thanks.

Only see 1.4.2 there.

edit: Found 1.4.1 on multiupload.
[Captivate Android Development] gtg465x:
Can someone who believes their custom uv settings are sticking after reboot please post their S_volt_scheduler file in /system/etc/init.d

I suspect it will be the same as mine but I want to make sure.

On my phone the 1.4.x kernels just aren't setting the uv values in /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table even though my S_volt_scheduler file is in the init.d directory and seems to be correct.

-Thanks
[Captivate Android Development] SetiroN:
It really does sound ROM related.

Can you post your /init.rc and /sbin/post-init.sh?
[Captivate Android Development] gtg465x:
I'm beginning to think so.
[Captivate Android Development] Killemalll:
I have been running 1.4.2_1200 with the AOSP rom for 2 days now. I didn't even notice it was actually clocking at 1280Mhz until it was posted here. No issues at all, super fast and rock solid. I didn't need to mess with any UV settings.

Thank you SetiroN for the great genuine development work! Absolutely worth a donation!
[Captivate Android Development] designgears:
@SetiroN:

Could this be kernel related?

v1.4.2

This was tracked back to SuperPower. Disregard.
[Captivate Android Development] krl66:
SetiroN, thanks for your hard work on this kernel. You're doing an awesome job and I'll be sending a little donation along to help brighten your day with an extra beer or two.

No real problems with any of your kernels on my end, but on XT my custom bootanimation didn't work and I saw subjectively faster battery drain. Just an FYI, not really an issue.
[Captivate Android Development] DOAlaboratories:
The superoptimised 4_3_4 kernel in the i90000 boards is overclockable to 1.4ghz, is there any possiblity of making a variant of this kernel that supports that freq?
[Captivate Android Development] l7777:
I can't say for sure that it isn't, but I can tell you that with my setup, I have no trouble charging while powered off. Did it last night just to check. Woke up in the morning and had no kernel panic, just the normal charge animation saying 100%. I have seen it reported before though.
[Captivate Android Development] deakinsjello:
I don't see this on di11igaf's latest ROM w/ 1.4.2.
[Captivate Android Development] johan8:
Tested XT and other, both Samsung and user bootanimation are working.

You can put bootanimation.zip in either /system/media or /data/local

I prefer /data/local so you don't need to remount /system to rw.

And don't use zip with compression.
[Captivate Android Development] shaolin95:
This would be SO awesome! I hope it can be done. :D
[Captivate Android Development] designgears:
I am testing it right now...
[Captivate Android Development] peachpuff:
Hmm for some reason i cant copy files with root explorer with the 1.3.5 kernel, the cp command is not found. Flashed back to the 1.2 kernel and cp works, anyone else notice this or is it just me?
[Captivate Android Development] tbong777:
Curious to see if you have this bug....

Happened without fail on every Build 5 ROM flash with the 142 correct and without any external Setiron kernal applied..

Flashed twice from stock to make sure it wasn't something I was doing.

I initailly flashed 5 over 4 with lagfix disabled and thought maybe that was the cause. By the third flash I could duplicate the Kernal Panic everytime,

Build 4 with 142 1280 charges fine.....
[Captivate Android Development] Haloruler64:
I charge fine both on and off with every kernel 1.2 to 1.4.1. Never even seen a kernel panic. Both Cog and Bacon.
[Captivate Android Development] DOAlaboratories:
I dunno if raspdeep still has the source up, and laststufo hasn't released the source for his kernel just yet though... but it'd be sweet to see it. My phone has one of the better OC chips so I wanna take full advantage of it :D
[Captivate Android Development] johan8:
What is the difference between XT and the other ?

In XT (1280kHz), Quadrant score is 15xx~18xx

In 128 (1280kHz), Quadrant score always 18xx

Don't know if it related to actual performance,

and don't know which is better.
[Captivate Android Development] johan8:
This is for i897 mod to i9000.

Not for real i9000.
[Captivate Android Development] gtg465x:
FINALLY found the fix in another thread!

Looks as though it probably does depend on which ROM you're running. In my case, renaming S_volt_scheduler to S_98_volt.sh fixed it. My uv settings are now loaded at boot! Not sure why having it named S_volt_scheduler worked on your 1.3.x kernels and not on your 1.4.x kernels, but all is well now.
[Captivate Android Development] bamonkey:
yep. saw the adb method but being a slacker just renamed in root explorer and it took after the reboot.. super thanks!
[Captivate Android Development] momulah:
Best UV settings

I have used -50 for all except 1200 and 1280 those are -25 and everytime I use 3d gallery the phone freezes. Perception 4 build and diligafs v2.0.1!! After it freezes and I pull battery all my launcher pro settings are messed up screens missing icon shortcuts changed etc. I would love to have this working as smoothly as everyone else. Any help appreciated. Setiron great job and progress you are much appreciated.
[Captivate Android Development] existz:
Any chance seeing the ext2/3/4 lagfix and battery tweak (laptop mode) added in? I've disabled journaling manually but sucks doing it every time I format .. would love to see your 1.28ghz xt kernel mixed with hardcores k10a
[Captivate Android Development] momulah:
Hey can you explain your UV settingsinyour sig? Are those starting from 1280 going down to 100? Is that stable going through 3d gallery? And should scheduler be bfq and limit max clock to 400Mhz?
[Captivate Android Development] existz:
Yea its going from 1280 down.. and yea its 100% stable for me, you may or may not get the same results .. and I have max clock set to 1280 and I use noop instead of bfq
[Captivate Android Development] momulah:
Thanks I'll try again. Which lagfix are u using. Is that ext overkill? Do I just choose ext overkill or I need to manipulate those settings. Im trying to get my phone stable so I'll duplicate your settings if you dont mind.
[Captivate Android Development] existz:
Im using ext4 overkill with no-journaling mode.. there's a guide by hardcore that explains how to disable journaling on ext4 in the i9000 forum.. it does make it more acceptable to data loss, the risk is up to you..make sure to backup.. however I've been running for 2-3 days now with no issues.. but again, my settings may or may not work for u..

My results with setirons 1.28ghz XT with ext4 overkill no-journaling and noop with all tweaks on is 18mflops and 2200 in quadrant ..
[Captivate Android Development] momulah:
Thanks! Is it hard to disable journaling?
[Captivate Android Development] existz:
Nah not really, just follow the guide word for word, he explains what commands to use, took about 10min max to do it
[Captivate Android Development] GustavTheLion:
Ever since flashing this I have a mic issue, people can't hear me during calls- could that be the kernal I'm not too sure, sorry if this is a silly question
[Captivate Android Development] bts0uth:
Any idea why vignette just doesn't work with XT version? It freezes the phone until you battery pull

Regular 1280 version works great

Posted from my Captivate running Axura beta 4 with SetiroN's SuperOptimized kernel 1.4.2
[Captivate Android Development] aleadam:
Temperature measurement?

Is there any temperature sensor in the captivate?

Now I'm running at 1.2 GHz and heavily undervolted so it's running very cold and smooth, but without undervolting and with overclocking the back starts heating up some times. I was just wondering whether that could be the reason why some people are having lots of f/c.
[Captivate Android Development] Yuna:
Can you post your settings?
[Captivate Android Development] shaolin95:
I use this:

http://www.androlib.com/android.application.com-sanels-temppcpu-Bmpp.aspx
[Captivate Android Development] aleadam:
That app that the dev says "do not download" and has been pulled from market? :confused:

I think I rather stay in my confident and secure ignorance... :p

@Yuna: I don't know who are you asking to... if you asked me for the volt settings, they are 75 75 100 125 125 125 as seen by /sys/devices/system/cpu/apu0/cpufreq/UV_mV_table
[Captivate Android Development] RKight:
I'm running build 5 with the 1280 version of the 1.4.2 kernel and I haven't had any issues with charging, while powered on or off.
[Captivate Android Development] shaolin95:
Wrong version just do a search for Temp+CPU V2 on the market..really not that hard. ;)
[Captivate Android Development] aleadam:
LOL I searched in the forum, I googled it... what I did not do is to search the market for an app! :p

Thanks.