yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Dani897:
Maybe nothing, try linpack. Quadrant isn't reapply accurate though I don't know what would be didn't in the kernel that would influence the score. I can tell you eclair gets better scores than froyo if both have a lag fix and different froyo builds can be all over the map with quadrant scores on the galaxy phones. I had a score of 2600 in eclair but linpack was barely 9.x at 1224mhz on unhelpfuls kernel . Now I get a quadrant score of 1800-2300 depending on lag fix and can get 18.1 in linpack running at 1280mhz.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] johan8:
Tks for your info.

Actually the score doesn't matter to me, but just wondering is it slower than previous version.

But the main problem is 1.5.3 keep freezing ....

Rolling back to 1.5.2 :(
[Captivate Android Development] crazililazn:
1.5.3 froze while changing the lag fix.... wow....

This thing is buggy as hell... Hope there is a fix soon...
[Captivate Android Development] shaolin95:
Nobody can tell your for sure OCing wont kill your chip because each one is different but such an OC is not unheard off and on the Cellphone world my opinion is that most CPUs are capable of a lot more than what they are run at but carriers control the speed to avoid battery life complaints.

I have been OCing since I got a T bird 1.4 to 1.70 back in the day...never ran a CPU at stock after that and never killed one, just a mobo but that was OCZ ram booster's fault!

So just watch those temps and run a stability test to make sure all is good, if you dont feel is too hot and are willing to take the risk and need the speed then go for it.

I do it mostly for emulators and benching, I could run slower and still feel pretty much the same for other tasks so with the voltage controller you always have the choice to push harder when needed....like a nitrous boost! :D
[Captivate Android Development] slider2828:
My phone hates 1.5.3 and .2..... Back to Assonance 1.43..... spent countless hours and nothing stable.... grrrrr.

It has defeated me... I shall wait...
[Captivate Android Development] johan8:
Based on my own experience,

Slightly lower performance in 1.5.x compare with 1.4.x with same clock speed.

1.5.3 is unstable.
[Captivate Android Development] kennethpenn:
My phone has stable OC at 1.6 GHz with Assonance. I make sure to turn off the screen and let the phone boot up without messing with things. The time when it is easiest to crash is "Media scanner running" time. So just let it sit and turn off the screen so the CPU works less. It'll boot in and then boom! you've got a stable 1.6 GHz kernel.

What's the difference between

setiron1.5.3xt.zip

and

setiron1.5.3.zip?
[Captivate Android Development] MikeyMike01:
Cooking 1.5.3 into my ROM and it's giving me all sorts of freezing issues. Came here to see what's what and I see others are having similar problems.

Going to try 1.5.2.
[Captivate Android Development] Yuna:
/me moved to Reorineted kernel.
[Captivate Android Development] slifer315:
1.5.2 is working great on your rom although I get sleepdeath when I undervolt to the same voltages I had on 1.4.3.
[Captivate Android Development] Jay120171:
The CWM version this has keeps freezing up at various points on me.
[Captivate Android Development] MikeyMike01:
1.5.2 didn't fare much better.

I'm giving xcaliburhand's a shot, to see if that's better/worse/same.
[Captivate Android Development] SetiroN:
Hardware damage from just overclock is highly unlikely. Sure, the lifespan might lower but we're talking of a fraction of 10 years.

Overvolting exacerbates the issue but we're sill far from having realistic problems.

Don't confuse wattage with voltage, anyway undervolting too much crashes everything WAY before possibly causing any damage.

Of course if you're not comfortable, 1200MHz can be more than enough. Most phones don't allow undervolting enough over that frequency causing too high battery consumption.

In 1.5.4 initial boot and recovery frequency has been lowered from 1200 to 800, that should sort it.

Make sure not to have a max clock higher than your stable frequency in Voltage Control's boot settings or the phone will crash as soon as the OS is loaded (some kind of bug causes max frequency to be selected for a fraction of a second).

I can't reproduce the issue...

make sure to remove any user script before flashing, then setup voltage control (don't forget to set max clock there) and go edit /etc/init.d/S99_freq_scheduler.sh according to your preference. Upon reboot, everything should be set.

I'm not planning to, /system conversion is nearly pointless from a performance perspective and additional features offered from the modified CWM are too good to give up.

Those settings are stored inside the kernel code, it shouldn't be possible to remove them...

Overall quadrant scores are as useful

You need to buy the advanced version and check out the single subsystems scores to have a perspective. Anyway the score could be lower because of changes made to improve battery life, I'm going back to 1.4 values in 1.5.4, check it out.

1.5.2 is pretty much identical, try the new version.

Make sure not to have a max clock higher than your stable frequency in Voltage Control's boot settings or the phone will crash as soon as the OS is loaded (some kind of bug causes max frequency to be selected for a fraction of a second when the boot script loads).

v1.5.4 OUT

- initial boot and recovery frequency lowered from 1200MHz to 800MHz

- reduced voltage change delay

- frequency jumps set up more like 1.4
[Captivate Android Development] MikeyMike01:
Flashing it now.
[Captivate Android Development] DAGr8:
well I did JF6 , and yea I spoke to ppl I seme to be the only one who has to do this manually , Iwas considerign gopin bacl tpo 1.43 since it phone was flying for me at that speed , you got me curious now will flash 1.54 NOW
[Captivate Android Development] MikeyMike01:
Still refuses to boot.

Any ideas?
[Captivate Android Development] SetiroN:
With default init scripts you should definitely be able to boot... are you sure you didn't have too high a frequency set as max in Voltage Control's script? Try that while in recovery:

> adb root
> adb shell
# cd /system/etc/init.d
# mv S99_volt_scheduler.sh ../

reboot

And eventually copy S99_volt_scheduler.sh back to init.d from /etc when you're able to boot, but don't forget to save a working max freq.

If that's not the case, first thing that comes to mind is FS corruption, especially if you were not using a journal...
[Captivate Android Development] MikeyMike01:
Perhaps there's a problem in the method I've used:

Starting from 3.1, I did the following:

Substituted zImage file

Added startup scripts to /system/etc/init.d/

Added "set_perm 0 0 0777 SYSTEM:/etc/init.d/S99_freq_scheduler.sh" to update-script

Flashed, hangs during boot animation.

P.S. I'm not trying to upgrade, I'm trying to make the next version of my ROM.
[Captivate Android Development] DAGr8:
hey you probably forgot to add the files form the system directory ?
[Captivate Android Development] MikeyMike01:
I added both of them in their respective locations.
[Captivate Android Development] Jay120171:
Well I flashed to stock via Odin, flashed doc's ROM, booted, flashed this kern, booted, rebooted to CWM and froze at different places when trying to apply a=ext4.

Hope this helps.
[Captivate Android Development] johan8:
I'm using advanced version,

but I'm not a hardcore fan of scoring, it is just for reference.

However for that amount of dropping I would like to know what's going on.

Going to try 1.5.4, thanks a lot for the great kernel!:)
[Captivate Android Development] eSPyeL:
Same situation here. I pulled the battery and rebooted to cwm and used adb to make sure I didn't still have any voltage control app settings. I didn't. Rebooted with logcat running. Phone came up but something FC. I couldn't tell what it was. I'll check the logs and see.
[Captivate Android Development] MikeyMike01:
Changing this line:

set_perm_recursive 0 0 0755 0755 SYSTEM:etc/init.d

to:

set_perm_recursive 0 0 0 0777 SYSTEM:etc/init.d

instead of adding another line seems to have fixed it. It boots anyway.
[Captivate Android Development] johan8:
1.5.4 TESTED,

Using default 0 0 0 0 0 0 0 0 1 1 1 1 1 1 S99_freq_scheduler.sh

still FREEZE after bootup.

What's wrong....

1.4.3 is good and stable

1.5.2 is ok, but sometimes freeze after connected with Kies

1.5.x freeze after bootup
[Captivate Android Development] majinzen:
1.5.4 I'm only freezing when powered off but on charger. After it charges for a few seconds, screen freezes and I have to pull battery.
[Captivate Android Development] MikeyMike01:
The USB is definitely messed up.

**** it, back to 1.4.3.
[Captivate Android Development] johan8:
Please add headset fix into 1.4.3.

This will be the best.

Thanks a lot.
[Captivate Android Development] bts0uth:
USB is messed up?

Wtf, I am not having any problems on 1.5.3 or 1.5.4. Boots up fine, nothing happens weird in recovery. I can O/C to 1400 stable with U/V at -25.
[Captivate Android Development] johan8:
Good for you.

what rom you are using ?
[Captivate Android Development] bts0uth:
I was using di11igaf's Rom v2.5 with 1.5.3 and it was fine.

Now im using Axura 2.1 with 1.5.4 and no problems.

If your having problems, are you sure you deleted any old voltage and overclock scripts before updating? I made sure I did before I went to 1.5.3 and never had issues.
[Captivate Android Development] Jay120171:
I can get it to boot with various ROM's but it does take a while to boot initially even after the launcher is loaded. I also got a FC on Launcher Pro one time. I started from a fresh Odin to stock so there are no leftover anything's. CWM seems to freeze at various places when trying to change the ULF settings. Sometimes it gets as far as the backup step but freezes while backing up. Have you been successful in changing ULF settings?
[Captivate Android Development] bts0uth:
On 1.5.4 I applied a lagfix just fine and enabled all tweaks and rebooted and had no issues. However, I just started a backup and it froze halfway through backing up system.

I did a backup on 1.5.3 though and it never froze. I am gonna go back to it for now since it worked good for me.
[Captivate Android Development] mikewong27:
I could not even complete the backup phase on 1.5.3 and 1.5.4. But I was able to install 1.4.3 without any issues.
[Captivate Android Development] illdroid:
hey

I was following that conversation :)

so after all it's a permissions problem...

did you try not changing that line at all?

why does that directory/file needs "others" (777) write permissions?

isn't this very dangerous?
[Captivate Android Development] johan8:
I have also tried delete init.d after updated to 1.5.x

states_enabled_table is 0 0 0 0 0 0 0 0 1 1 1 1 1 1

but nothing help.

I use stock i9000 rom.
[Captivate Android Development] MikeyMike01:
It froze every time I plugged the USB cable in, so I reverted back to 1.4.3.

Hopefully 1.6 brings some welcomed stability.
[Captivate Android Development] arffer:
That explains it!

No worries, thanks for the (soon to be) fix!
[Captivate Android Development] opcow:
Yeah, checked it and 3 button still worked. Reverted to 1.0 and my home button is working correctly now.
[Captivate Android Development] KaLiBLeeK:
I unwisely flashed the 1.0.1 update without a full battery. Haha. Went from 40% battery to 9% on reboot. Gonna recharge all the way and wait for the next update, and see if I can get JFS to stick.

Regardless, this kernel is AWESOME. Many thanks!

Sent from my Samsung Captivate (XDA-App)
[Captivate Android Development] bts0uth:
Wow, so happy to wake up and see SentiroN is updating the kernel :)

bootanimations and JFS fixed, woohoo!

BLN will be fixed in no time I bet and then what else is there to add?

Nothing I can think of. This may just be the Ultimate kernel :)
[Captivate Android Development] airbillion:
So far this modem (jj4) is working great, good reception and battery seems ok. Not sure about battery though, because I am overclocked and have been playing with the phone a lot, but so far it seems good.
[Captivate Android Development] bts0uth:
Have you by chance been in a car or traveled anywhere yet while using JJ4?
[Captivate Android Development] rob989_69:
Ok, I know it's been mentioned here but I'm running Cog 2.3b, loaded this Kernel and everything is redonkulous.

Except reception... 3G is fine, I can hear people fine, but I'm getting complaints from people I call that I'm hard to hear. I only loaded the kernel, not the zip posted a while back. Any thoughts?
[Captivate Android Development] id10terrordfw:
You're probably using an i9000 based kernel with a Captivate modem. THis has been known to cause issues.
[Captivate Android Development] bts0uth:
Holy crap, I switched to jfs overkill from ext4 no rfs.

My quadrant score was in the 1700s with ext4 and now with jfs overkill...

This kernel is great!

Posted from my Captivate running Doc's JPO v7.5 rom with SetiroN's i9000 SuperOptimized, ULF, OC/UV, 340Mb, Re-Oriented kernel v1.1
[Captivate Android Development] airbillion:
No, not yet. Ill update when I do.
[Captivate Android Development] KaLiBLeeK:
Has anybody got their boot animations working? I replaced the zip in the /system/media/ folder, but it didn't take. Same i9000 screen, then blankness.

Tried putting a copy of the bootanimation.zip in the /data/local/ folder also, as mentioned in the Android Scribble thread, still no dice.

Sent from my Samsung Captivate (XDA-App)
[Captivate Android Development] amwbt:
How's the battery life with the JPP Modem?
[Captivate Android Development] bts0uth:
I took one from the thread in theme section and just placed bootanimation.zip in system/media

It worked fine

Posted from my Captivate running Doc's JPO v7.5 rom with SetiroN's i9000 SuperOptimized, ULF, OC/UV, 340Mb, Re-Oriented kernel v1
[Captivate Android Development] id10terrordfw:
Without undervolting I hit 10% used in one hour while on lunch. It was heavy use.
[Captivate Android Development] amwbt:
So that's pretty good?
[Captivate Android Development] joedon3:
This thing is FAST! I don't think I'll be upgrading for quite a while. Thanks SetiroN!
[Captivate Android Development] id10terrordfw:
For me, yeah it really is. Average before this was 15% or so.
[Captivate Android Development] rraquib:
How do you undervolt with this this kernel. What setting files do I need to change?
[Captivate Android Development] LuckyX2:
I'd like to update on my voodoo color comment. I flashed back to xcaliburinhand's kernel and it still didn't look as good as it did with tayutama/xcaliburinhand so I'm led to believe that it's something about tayutama's rom that gave the screen a softer look. Or rather something with killer's doc rom that gives it a harsher look.

So the short of it is, I don't think your kernel is the problem. Sorry for the false alarm.

Oh and rraquib, you can just use the voltage control apk that was posted about 10 or so pages back in this thread.
[Captivate Android Development] wesc011:
So I used the Voltage control app in the OP and set it for -75 -100. I also set it to boot with the cfq scheduler. However, every time I reboot the values go back to 0. What am I doing wrong?
[Captivate Android Development] DAGr8:
ya the usb issues seem to be diffrent form one user to another ..

I never experienced it .

1.43 was the bomb , I still doitn get why echo lines wont work in my case .

I meanit took me a while to figure it out when I was on 1.43 since it had to be add manually but now its all in by default just put a 1 instead of a 0 my the table file nvr gets updated afte a reboot ...
[Captivate Android Development] shaolin95:
Doesnt your newest ROM have 1.5.4? I am having fun with 1.5.3 myself so I think I will skip the update since mine is all fine so far.
[Captivate Android Development] shaolin95:
So far I think you are the only one reporting a stable 1.6Ghz so care to share your settings etc? What linpack are you getting also?
[Captivate Android Development] DAGr8:
wait obviously its not stable if he has to wait for it to stop scanning , stable means the phone can perform like it normaly does .
[Captivate Android Development] shaolin95:
If he can do everything else fine like quadrant, neocore, everthing else...I can live with waiting for scanning..cant you? ;)

I actually have seen my phone act weird if I try to use it too quick when booting up even at stock speeds but on the other hand, being the only one reporting 1.6Ghz, no offense but I need to see it to believe it. :D
[Captivate Android Development] slider2828:
I want to see if he have god i9000 in his hand hahaha.. I am guessing at 1.6, he is probably 25- 28 megaflops? That would be crazy.
[Captivate Android Development] shaolin95:
I would expect 24-25 maybe...I have not being able to get it stable enough to do it yet :)
[Captivate Android Development] BTTNext:
Updated from 1.4.3 to 1.5.4. Device routinely freezes about 30 seconds after lock screen shows up. This sucks :(
[Captivate Android Development] slider2828:
Agreed I am sad too.... I want the wired headset!!!
[Captivate Android Development] bts0uth:
Sadly, 1.5.4 and 1.5.3 are freezing on start up with no scripts in init.d and then randomly starting up and rebooting after a few seconds.

I previously had no problems but I flashed a new rom and these new kernels arent stable any longer.

I will use an older version until SetiroN gets it worked out. I hate losing the ext4NJ lagfix though. Hopefully a new stable version will be out sooner then later
[Captivate Android Development] MarlowXim:
If your having any issues, with freezing/lockup issues on boot try this solution. It may work, since I don't rely on Setiron's internal scripts. Also try the XT variant seems more stable for me than the regular. (Not sure why perhaps KSM checking for duplicates in memory pages.)

Insert one of these lines in your volt script. I think the default install in cwm is S99_freq_scheduler.sh. Use adb in recovery mode. Should be valid for 1.5.2+

Limits frequency stepping to a maximum 1.0 ghz

echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

Limits frequency stepping to a maximum 1.2 ghz

echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

Limits frequency stepping to a maximum 1.4 ghz

echo 1400000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Captivate Android Development] DAGr8:
here is the nj procedure ( no journalling for EXT4 partition ... )

http://xdaforums.com/showthread.php?t=851407
[Captivate Android Development] TheYar:
Just to add to the log:

I found 1.4.3 to be the fastest and smoothest Captivate experience to date, even with signficant uv.

I've flashed all 1.5 and 1.5.X versions, paying careful attention to scripting and permissions, and with various oc/uv experimentation, and have consistently encountered freezing/acore crashing, and shortly afterwards, a failure to boot.

The longest I could ever get a 1.5.X to hold steady was overnight, and then it died shortly after I turned the screen on the next morning and would not boot again. This was after stock, master-clear, flashing a favorite old stable ROM, flashing 15X, ext4 with no backup/restore, capping the freq at 1.0 and leaving uv at 0 0 0 0 ..., and re-installing apps fresh from Market with no restores from TiBu.

1.4.3 is still the best though, srsly.
[Captivate Android Development] shaolin95:
You realize that this is true for your cellphone but does not mean it will hold true for everyone else's right?
[Captivate Android Development] lpsi2000:
LOL, well I am saying if it works on your cell phone and it is going to work on mine:p

It the mean I am using 1.5 for now.
[Captivate Android Development] BTTNext:
Agree with you 100%
[Captivate Android Development] BTTNext:
SetiroN, apparently the XXJPU offers much better performance and overall is just a lot better. Is updating the base to XXJPU something you would look at?
[Captivate Android Development] shaolin95:
Setiron would it be possible to have a kernel with only one speed like 1.6Ghz? My idea if of course so we can truly test the CPU at 1.6Ghz and find out if any voltage is able to make it stable then we can work on finding a way to make the transition steps so that it remains stable...

Right now it is way too hard to try to get 1.6Ghz because we do not know if the issue is jumping from 1.4 to 1.6 or the voltage difference between the jumps or should I enable all freqs instead...way too many variables.

Just an idea of us avid OCers trying to squeeze all this CPU has.
[Captivate Android Development] lpsi2000:
+1 That is exactly what we were doing prior to 1.4.X and 1.5.X. I guess it was becoming too much work for Setiron to keep the various versions. But I like the idea.
[Captivate Android Development] shaolin95:
I am sure this will be a lot of trouble for Setiron but it would be nice for us fighting to get to 1.6...we will know for sure that if it fails it is not going to happen instead of wondering if a different combination of voltages and steps will do it....Well maybe it wont be so hard since all we need is just one kernel running only at 1.6 so there are no speed jumps.
[Captivate Android Development] johan8:
1.4.3 is the best for me so far.

stable, and fast (maybe just the score)

I hope there is a standalone headset fix I can apply after 1.4.3,

or 1.4.3 come with headset fix.
[Captivate Android Development] SetiroN:
I'll be temporarily dropping v1.5 development due to lack of time, debugging issues I can't reproduce is horrendously inefficient.

For now there'll only be 1300 (which every phone should be able to handle) and 1400MHz variants. That's the price to pay for losing frequency customization.

Shaolin: if you can't manage 1.6GHz (an extreme clock only a phone in a thousand is gonna be able to use) on 1.5, there's no reason to believe a kernel with just that frequency would change things. I already tried when I released 1.4.3 first and there's no way unless you bump voltage to unsafe levels.

A JPU-compatible version is almost ready, I've already managed to extract the ramdisk from samsung's new kernel and only have to debug dedicated memory settings to allow video playback (we're probably gonna lose a few MB).

v1.4.4 OUT

added workaround script inside the update.zip to execute voltage control boot settings directly from the program's data dir, eliminating the necessity to remount /system

gained an additional MB of RAM thanks to kernel size optimization

implemented Xcaliburinhand's wired headset fix

optimized RAM utilization (minfree tweaks)

updated CWM to include Hardcore's latest additions

slight menus reorganization

updated optimization scripts (now including battery optimizations, GPS tweaks, CIFS support)

built-in support for ext2, ext3 and ext4 no-journaling (you will see a "configuration changed" screen if you manually disabled journaling - select "No, enter recovery mode" and switch ext4 to ext4nj)

built-in support for ext4 mount optimizations (writeback mode)

HZ=500, PREEMPT_VOLUNTARY
[Captivate Android Development] shaolin95:
Not quite sure what this is...sorry can you explain that part?
[Captivate Android Development] johan8:
Woo!

You are so great !

I will love to use 1.5.x, but don't know how to make it stable with me...

For you information here is my i897,

ROM i9000-JPE, CSC:JPD, JK3 modem, it is complete new flashed, no other mod or patch used, just used 1.4.3.

After applied 1.5.x, phone freeze after media scan finished.

Reboot the phone after freeze, then the phone will work in this reboot....

but if connect to kies, it will freeze after usb unpluged....
[Captivate Android Development] bts0uth:
1.4.4 1300 keeps giving a errror when flashing it. Cant chmod the voltage script in init.d and then installation fails.
[Captivate Android Development] hansmrtn:
Ohh, where is 1.4.5? Looks fu**** sweet! :D
[Captivate Android Development] BTTNext:
I can report that running 1.5.3 with DDJP6 did make the device freeze within 30 seconds of boot up.

However, 1.5.3 with XXJPU is running awesome so far. Hopefully this helps with debugging.

Very excited for the XXJPU-based kernel!