yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shaolin95:
I see that the 1400Mhz version 1.4.4 actually has 1440 and 1460 options and I can activate them from the sys folders but not from the init.d one though...any idea why not?

Never mind it works now.

Do you have the voltages for the speeds?
[Captivate Android Development] hansmrtn:
Hey setiron, any chance we could get a 1200mhz kernel for 1.4.4? :D
[Captivate Android Development] crazililazn:
Has anyone gotten 1.4.4 1300 mhz version working?
[Captivate Android Development] majinzen:
1.4.4 tar works great with odin. Is working well on my phone no freezes yet. Headset mic. works!
[Captivate Android Development] geokhentix:
I'm on 1.5.3 XT stable @ 1600mhz. voltages are -50/-50/-50/-75/-75/-75/0/0/0/0 so on so forth. :p Gotta say, disgustingly lightning fast on this setting. Survived 66 passes of StabilityTest, hitting a max temp of 41C.

Great job SetiroN, beer coming your way on the next payroll. :D
[Captivate Android Development] hansmrtn:
@Setiron

Hey dude, can we get a 1200mhz kernel with all the optimizations as 1.4.4? :D
[Captivate Android Development] beerbaronstatic:
I'd like to see a 1200 mhz kernel as well for 1.4.4 if possible
[Captivate Android Development] shaolin95:
Why not just run it at 1200, the option is there.
[Captivate Android Development] hansmrtn:
Not by default though sadly :(. maybe if I change something in the init.d
[Captivate Android Development] shaolin95:
You should be able to change it so that it boots to 1200 max. I just tested the 1400 file and it was not giving me 1400Mhz until I edited it.
[Captivate Android Development] hansmrtn:
What, the init.d?
[Captivate Android Development] junktzu:
1.4.4 1.3Ghz installed and seems to be working fine. Voltage control 2rc2 is FC'ing, should I downgrade to an older version?
[Captivate Android Development] lpsi2000:
Agreed, that would be sufficient

Exactly

Setiron, I think you nailed again with this new version

Thanks
[Captivate Android Development] shaolin95:
I actually edited both the file in the init.d and the the the one in the sys folders. For the init.d you need to mount to rw first then just save your settings to bios from with in the Voltage Controller app.

I might be able to squeeze 1460 with 1.4.4 and it is a heck easier to get 1400Mhz stable on 1.4.4 than the time it took me to get it stable on 1.5x
[Captivate Android Development] hansmrtn:
Yeah. But we need the headset fix in axura too :rolleyes:
[Captivate Android Development] DAGr8:
I guess I am not the only one who cant read CHANGELOGS ... lmao
[Captivate Android Development] lpsi2000:
LOL, I make my business to read the log every time something new is posted
[Captivate Android Development] lpsi2000:
Agreed, what did you uv 1400 to?
[Captivate Android Development] junktzu:
Seems like the Voltage Control FC's were being caused by the scaling_max_freq being set to 1280000 instead of 1300000
[Captivate Android Development] shaolin95:
-50 for 1400 Mhz
[Captivate Android Development] lpsi2000:
Interesting, -50 took but not stable under heavy load (like 15 quadrant runs, 20 linpack runs). However with -25 it ran cool like a cucumber.

That is weird though, because with kernel version 1.4.3 I was able to get 1400 -50 with no issues with load
[Captivate Android Development] hansmrtn:
Welp, I feel like an idiot, cause kernel work is my weakness haha
[Captivate Android Development] junktzu:
Hmmm those UV values make me want to try the 1.5 kernel again...
[Captivate Android Development] crazililazn:
lol i cant even get 1.4.4 1400 to boot x.x
[Captivate Android Development] slider2828:
Hey Shaolin, are you editing the volt and freq script in both the \system\etc\init.d and \etc\init.d\ ad the file in the \sys\devices\.......

When I check the S_VOLT_Freq, there is data in it because of the size of the file, but when I open the file there is nothing in it.
[Captivate Android Development] johan8:
Mine use i9000 stock rom working with 1.4.4 1300.

However, the I/O speed seems 2x slower than 1.4.3

mine is using all ext4.....

1.4.3 I/O : 46xx

1.4.4 I/O : 28xx
[Captivate Android Development] gtg465x:
I realize you're probably working on the stability/performance issues that many are experiencing, but could you make a version with this mem config? Hardcore has already switched to these in his latest version.

These are the stock values from the latest i9000 leak (JPU 2.2.1), which has 339 MB RAM available stock. HQ video recording/playback aren't working on JPU with the current mem config you're using. Thanks!

And jpeg should be set to 0.
[Captivate Android Development] bluerogue85:
sorry if this has already been mentioned..but since theres so many post im just gonna ask again and check back in a few..but ne ways whats the diff bet the reg ver and the ones with an .xt at the end of the kernel files? thanks
[Captivate Android Development] Doug8796:
how do you modify init.d?
[Captivate Android Development] MarlowXim:
I didn't have any issues with the 1.5.X series the only thing that I think was missing from your volt limitation script was the scaling_max_freq. (Didn't use Xan's app everything manual)

Test Conditions

I tested this with 1.5.2 XT when I had set the max freq scale to 1.6 ghz but did not enable the frequency (0 function) it would higher chance of locking up. (Unless I placed it in the refrigerator ha!) Placing the 1.4 ghz limitation it would work the same as 1.4.X. I think this is what was causing most issues. But I do understand you need to dumb it down for most people.

Amazing your maintaining 41 degrees mine gets hotter than that when I tried 1.6 ghz... it was stable in the refrigerator haha.

He's using the new safer mount options for ext4 to lower the chance of data corruption based on hardcores source. That's why your benchmark scores are lower.

It's already in the original post. Basically XT is a faster, less stable, and slightly higher battery consumption compared to the original.Pick your poison :)

You need to read the past posts and or read the sticky posts within the galaxy forums. It's simple once you look at previous examples.
[Captivate Android Development] MikeyMike01:
Is that a typo, or is there actually a v1.4.5?
[Captivate Android Development] PAulyhoffman:
1.4.5

Changelog:

v1.4.5

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

Anyone see 1.4.5 for DL

i may be blind but im not finding it!?

unless it is indeed a typo
[Captivate Android Development] johan8:
Not really.

I have entered to CWM, the default is FAST.

Then I changed it to SlOW, let it fully boot.......

Go back to CWM, change it back to FAST.

This is make sure it is in FAST !

On the other hand, 1.4.x seems not support writeback,

so why 1.4.x is fast in this case ?
[Captivate Android Development] SetiroN:
1.4.5 was a typo sorry, it's 1.4.4

I know, that's what I posted earlier: :rolleyes:

Yet I managed to actually gain an additional Mb, 345MB total. :D

JPU variant

includes modules and mem config extracted from samsung's JPU kernel: DO NOT USE IT ON FIRST BOOT OR YOU'LL GET AN ENDLESS VIBRATING BLACK SCREEN, BOOT ON SAMSUNG JPU AND ONLY THEN FLASH THIS KERNEL
[Captivate Android Development] MarlowXim:
I think it is enabled are you using the right cmd?

busybox mount | grep ext4

look if you have writeback on selected partitions.

Try adding noatime,commit=20,nobh,barrier=0

I didn't have any difference in the I/O benchmark. However I overrided the mount options with my own. That's why I believe it is more changes in the settings for fast and safe options.

You can put the unsafer mount options back, but you'll need to write a script. Also if you look at hardcore's thread it's mentioned that he tweaked mount options to be safer. As well as users reporting the same performance loss as you.

...JPU 1400 build 1.45 build needs internal build number update.
[Captivate Android Development] johan8:
Everything is left in default,

I even haven't install Xan's Voltage Control and haven't uving too much......nothing....

I don't think I have corrupted partitions because it is new fresh flashed with stock rom.

I don't need writeback.

Just flash back to 1.4.3, I/O speed back to 4xxx.

1.4.3 has ultra fast mount !???

Do you think I need tweak in 1.4.4 ?

This what I'm using...

mount|grep ext4
/dev/block/mmcblk0p2 /data ext4 rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered 0 0

/dev/block/stl10 /dbdata ext4 rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/stl11 /cache ext4 rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered 0 0

I/O speed is 26xx
[Captivate Android Development] MarlowXim:
Add barrier=0 and journal_async_commit. Those options are relatively fast from what you've shown. But looking at Hardcore's changes he tweaked the IO scheduler as well. I don't have a basis of what changes, since I overrode them as well.

I looked again at your benchmark. Since it's hitting 4000+ you probably used the ext2 loops. They tend to cheat the I/O tests. You can put those back on, but they don't provide any real world benefits.
[Captivate Android Development] SetiroN:
Look, just switch your partitions to ext4nj, it's not like we're forcing you to use safe options.

v1.4.5 OUT

Frequencies/battery fix
[Captivate Android Development] MarlowXim:
Just right when I was about to flash lol. Good timing
[Captivate Android Development] Yuna:
SetiroN, what wrong with 1.4.4 and 1.4.5 in I/O matter?

I have lower scores in quadrant!

busybox mount | grep ext4

/dev/block/mmcblk0p2 on /data type ext4 (rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered)

/dev/block/stl10 on /dbdata type ext4 (rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered)

/dev/block/stl11 on /cache type ext4 (rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered)
[Captivate Android Development] johan8:
Let's see that's why

1.4.3

mount|grep ext

/dev/block/mmcblk0p2 on /data type ext4 (rw,noatime,barrier=0,data=ordered,noauto_da_alloc)

/dev/block/stl10 on /dbdata type ext4 (rw,noatime,barrier=0,data=ordered,noauto_da_alloc)

/dev/block/stl11 on /cache type ext4 (rw,noatime,barrier=0,data=ordered,noauto_da_alloc)

1.4.5

mount|grep ext

/dev/block/mmcblk0p2 on /data type ext4 (rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered)

/dev/block/stl10 on /dbdata type ext4 (rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered)

/dev/block/stl11 on /cache type ext4 (rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered)

Turn barrier=0 will be better.
[Captivate Android Development] Yuna:
hmm... how to change those options in runtime?

okay, changed:

# busybox mount -o remount,barrier=0 /dbdata

# busybox mount -o remount,barrier=0 /data

no effect
[Captivate Android Development] bts0uth:
Hm, I am using Docs JPU rom and flashed 1.4.5 JPU 1300 kernel.

Home button isn't doing anything. Everything else is working but long pressing home doesn't bring up recent apps and task manager button and it doesn't go back either. Just does nothing
[Captivate Android Development] existz:
First use..

#mount | grep ext4

To see what partitons are ext4 ..then use the following to set it..

#Mount -o remount,barrier=0 /dev/block/mmcblk0p2 /data

Mount -o remount,barrier=0 /dev/block/stl10 /dbdata

It will reset on boot so make a startup script....

I personally use...

Commit=60,barrier=0,journal_async_commit,nobh
[Captivate Android Development] bts0uth:
wtf? did my home key just decide to die today or is anyone else's not working?

I am now using the normal 1.4.5 1300 version on Assonance and my home button does nothing. Not even go back.
[Captivate Android Development] Yuna:
Working perfectly... Looks like your button is dead...

> To see what partitons are ext4 ..then use the following to set it..

Yeap, tried - still score is about the same e.g I/O...
[Captivate Android Development] bts0uth:
Wow. WTF. How did my button work perfectly like 6 hours ago and now it does nothing.

I'm sure there is no fix right? And I bought my phone from craigslist so I can't go to AT&T. I hope to god I can fix it somehow
[Captivate Android Development] shaolin95:
Well, it takes a split second for something to stop working ;) Still I hope is just some odd glitch and that a new flash takes care of it for you cause that sucks :(
[Captivate Android Development] MikeyMike01:
I've had firmware flashes render my Home button useless.

Flash to stock and start afresh.
[Captivate Android Development] bts0uth:
It works on stock thank goodness. Never had that happen in like 150 rom flashes so I was freaking out. Good time to flash Assonance 4.3 I guess lol.

Sorry SetiroN, I figured the only thing it could be was the new kernel but I was wrong! Should have known better :P
[Captivate Android Development] johan8:
By enable journaling and write barries will make your data much safer.

I will like to absorb decrease of performance.

But for mobile, it will be different case, I think.

Maybe Android or the kernel is not stable enough, or the apps is buggy,

I experienced system freeze and FC during high I/O software such as using Google maps and Layers.

The system seems trying hard to keep data integrity during high I/O, but somehow the software doesn't quite follow, then crash...

So maybe it is good to disable some data integrity during mount also is a good idea.
[Captivate Android Development] crazililazn:
Hmm. 1.5.4 doesn't freeze when I use the phone anymore but it still does when I try to change the lagfix. Will give 1.4.5 a spin when I get home :)

Btw, 1200 mhz version of 1.4.5 coming out soon? :o
[Captivate Android Development] BTTNext:
Running 1.4.5-JPU on XXJPU, video is now working great but unfortunately WiFi is still not working.

Looking at the discussions in the i9000 forums it seems like this would be a kernel issue.

Any chance of looking at what's causing it, SetiroN?
[Captivate Android Development] gtg465x:
Oddly wireless tethering does work though. And for clarification, wifi does turn on and see aps, but it won't connect to them. Even tried static ip settings.
[Captivate Android Development] bts0uth:
I keep getting mount not found when trying to change /data using this: "Mount -o remount,barrier=0 /dev/block/mmcblk0p2 /data"

export PATH=/data/local/bin:$PATH
$ $mount | grep ext4
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,nodelalloc,data=writeback 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=1,nodelalloc,data=writeback 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=1,nodelalloc,data=writeback 0 0
$

Could you post your start up script so I can change it to fit me and learn a little in the process?

The system seems to really slow down after a little bit of use on 1.4.5. It was going one at a time loading app data in TiBu. I'm using ext4nj on all three partitions.
[Captivate Android Development] BTTNext:
Yep, same here.
[Captivate Android Development] temp7788:
I love this kernel! I've tried all most every version since 1.2.6fixed.

I know nothing about kernel, I just install it.

When I went to i9000 forum, I saw this thread

http://xdaforums.com/showthread.php?p=8890266

It is about the kernel "SpeedMod". they said:"Kernel HZ value: HZ=500 is smoother, HZ=256 is Samsung default."

Here, I have a question.

What is the default kernel HZ do you use in Setiron. Is it the same with Samsung default one?

I know you rise the maximum clock, take SetiroN_v1.4.5_1300 for example, the maximum clock is set to be 1300MHz. What about the default value of Samsung for this parameter.

Will battery life improved, if I change this "maximum clock"? Or is it the best balance between battery life and performance?

Thank you
[Captivate Android Development] bts0uth:
You guys that don't have wifi working on JPU, did you flash JK3 modem over the JPU modem?

I went the old route of Stock > JG8 modem > Darky rom with JPU modem.

850 band is working on JPU and my wifi connected and is working. Using SetiroN's 1300 kernel
[Captivate Android Development] double RL:
I'm away from home and need a cwm flashable version of the 1.4.5 1300 if anybody can help a brotha out... TIA
[Captivate Android Development] BTTNext:
Just got to campus where we have 802.11g with WPA2-Enterprise and it seems to be working fine here.

At home 802.11g/n with WPA2-Personal it is not working whatsoever.

Once I'm home I'll try to tinker with router settings to figure out what the issue is.

AFAIK whether it's JPU/JK3 modem, doesn't make a difference.
[Captivate Android Development] slider2828:
Hey guys I am using kernel 1.4.5 1300 and it doesn't seem to be reaching 1300 on tests.... It just seems to be 1288 is or so.... Can anyone confirm this?

I am using stability test to look at the speeds when its running its passes...
[Captivate Android Development] crazililazn:
I noticed this too. In Setcpu, it was showing the max frequency as 1200. So i went to sys/devices/cpu/cpu0/cpufreq/scaling_max_freq and it said 1200000. So i edited it to 1300000 and now it works.

However, one thing i noticed on 1.4.5 1300, is that quadrant scores are REALLY low. Im getting 1500 with All ext4 lagfix, when i usually get 1700-1800 for 1200 mhz :/

Also, with 1.4.5 1300, when i go into recovery and look at the lagfix options, only ext4 data and ext4 all show up? is anyone else experiencing this?
[Captivate Android Development] fatttire:
SetiroN,

Have you tried looking at hardcore's recent kernel scheduler tweaks? There have been a lot of chatter on the i9000 forums that it helps GPS:

http://xdaforums.com/showpost.php?p=9587212&postcount=4326

since you have kernel scheduler tweaks already baked in thought i'd let you know about the update. also you do a great job of incorporating updates. thanks.

edit: not making any claims about gps its just something that a lot of other folks are talking about and I thought i'd link it in here since it comes from a major developer
[Captivate Android Development] johan8:
Check my post in previous page, I'm also talking about it.

From 1.4.4 to 1.5.x, it enabled write barriers for better data integrity in writing,

but it is too costly in performance for mobile device, and maybe a bit battery drain.

You may need to write a boot script to remount without write barriers.

Moreover, I'm also using 1.4.5 1300,

just leave it power on and charging with computer usb,

a couple hours later, my phone freeze.......:(

perhaps I better stick with 1.4.3......
[Captivate Android Development] bts0uth:
With JPU kernel, the internal SD mounts as a cd drive on my computer and it says its write protected when I try to copy stuff to it.

External SD mounts normally.

(I think this would be a kernel issue, forgive me if it is an issue in Darkys v5.1 JPU rom)
[Captivate Android Development] crazililazn:
flashing back to 1.5.4 seems to fix it for me :/ even tho 1.5.4 freezes when i change lagfix, it is still better than 1.4.x for me, so will stick to this for now :]
[Captivate Android Development] hansmrtn:
Any way to manually include the headset fix in 1.4.3?
[Captivate Android Development] aleadam:
I remember reading somewhere (could be a Supercurio's post, but I may be wrong) that problems with the lagfix may mean data corruption. If it gets worst, I'd suggest you to go back to stock, master clear, etc, and start all over...
[Captivate Android Development] aleadam:
Besides that, how is darky's rom working on the captivate? You're using the 1.4.5 kernel?
[Captivate Android Development] crazililazn:
Nah... 1.5.3 had freeze problems or crashing shortly after boot and even freezes in recovery mode, like while making a backup.

1.5.4 fixed it a bit for me, but it still freezes while backing up.

However, i have had some freezes and reboots from bad OC/UV settings, so there might be some data corruption :D
[Captivate Android Development] Colton5419:
Confirmed freeze on 1.4.5 while charging via USB
[Captivate Android Development] johan8:
Me too...

:(
[Captivate Android Development] slider2828:
I am on Assonance 4.3 1.4.5 1300 and I have absolutely no problem with it.

I started with Master Clear | JF6 | then the new Assonance which INCLUDES 1.4.5 1300 Full EXT4.... Its sweet...

Maybe try that?

**EDIT

Quadrant: 1509

Linpack: 17.7

NeoCore: 55.7FPS....

Anyone have ideas why I can't edit my freq files? Everytime I edit them, on boot they don't stay. I can't edit init.d scripts because when I open them they are blank, but the file size says here is something there... Help?
[Captivate Android Development] johan8:
Tried remount exactly as 1.4.3

Checked and confirm partitions mounted with no commit and barriers and exactly as 1.4.3

But nothing help !

Quadrant I/O score is 3000 in the max,

in 1.4.3 I/O score in 4xxx.
[Captivate Android Development] XGX5309:
1.3GHz 1.4.5 BLN won't turn off. It says disabled, but it isn't. Anyone else seeing this, or do I need to reflash a kernel/ROM?
[Captivate Android Development] slider2828:
I am ok.....................
[Captivate Android Development] XGX5309:
Interesting. Are you on a JK3 ROM?
[Captivate Android Development] johan8:
Assonance's Quadrant scrore also just 1509 ?

Somehow Assonance is not suit for me, I like the original bootup/shutdown animation but it cut it, and too much preconfig customization.
[Captivate Android Development] slider2828:
You can change the boot up customization.... The Quadrant scores are mainly the type of lagfix ext4 ALL that is implemented.... If I had a choice I would go back to 1.43 but I need the wired headphone fix in the 1.4.5 kernel... OH welllz
[Captivate Android Development] johan8:
Yes, I mainly mention about the I/O throughput.

Even I have remount and disable all journaling and write barriers the performance still low.

Test one more day with 1.5.4, if it is not stable then maybe I will go back to 1.4.3 because I don't need headset.

If you need headset but don't need OC, you can use xcaliburinhand reoriented, it is quite stable.
[Captivate Android Development] Dzmitry:
On JPU rom's internal sd card is detected as CD DRIVE
[Captivate Android Development] cruiserbax:
@Setiron, you rule for making a kernel to work with JPU on captivate!
[Captivate Android Development] SetiroN:
Set ext4nj and ext2 loops if you care so much about quadran't pointless I/O score.

If you wish to cahnge mount options you have to do it with tune2fs in recovery mode, but I'm not gonna guide you through it.

Why? I have yet to head of a phone unable to handle 1300MHz...

1.4.x only supports a single additional frequency step at 1300/1400MHz, nothing else.

the scaling_max_freq is built in at 1200MHz in 1.5.x unless specified differently. As I mentioned earlier, setting it higher than enabled frequencies at boot is dangerous because that frequency gets applied for a fraction of a second on boot.

Wi-Fi is working perfectly here. I'll make a small change to eventually circumvent issues you may be having.

Read the OP. HZ=500. Kernel HZ has nothing to do with clock frequency, it's another matter entirely.

It's not my fault if you guys don't delete init scripts before downgrading.

Read the OP, it's already implemented.

Known issue caused by using JPM based kernels on JPU. Nothing can be done until samsung releases updated sources.