yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] SetiroN:
v1.4 OUT

- raspdeep's OCUV updated to v217

- implemented fastscaling for 100-400MHz frequencies

- added 1280MHz variant (UV setting for 1200MHz applies to 1280MHz, so reset it)

- ULF updated to pre-0.4, modified to support bootanimations

- fixed potential /system corruption

- integrated JK3 modem in CWM flash package

- kernel version updated to reflect frequency variant (#140-1280 / #140-1200)

- BLN has issues

***UPGRADING TO V1.4***

As you might be aware, supercurio discovered a potential corruption bug present in Ultimate Lag Fix based kernels: v1.4 fixes it, but precautions are necessary when upgrading.

The fixed kernel might not be able to read your previous /system partition so following either of these procedures is VERY HIGHLY recommended:

Solution #1

- BACKUP with Titanium Backup and CWM

- Flash the specific fix kernel made by supercurio (odin version / CWM version)

- if the phone boots fine, go ahead and flash v1.4

- if you get stuck on the bootlogo or the phone boots but everything disappeared, flash back to v1.2.6/1.3.5 and try solution #2

Solution #2

- backup with Titanium Backup

- copy the v1.4 1200MHz or 1280MHz(reset UV!) update.zip to /sdcard

- reboot to CWM

- BACKUP

- flash v1.4

- reboot to recovery from 'Advanced ULK' (DO NOT REBOOT THE SYSTEM)

- advanced restore /system

- reboot

- if you get stuck on the bootlogo or the phone boots but everything disappeared, flash back to v1.2.6/1.3.5, you're gonna have to go with solution #3

Solution #3

- backup with Titanium Backup

- flash your ROM of choice

- flash my kernel

- restore with Titanium Backup

***RESET ALL UV SETTINGS BEFORE UPGRADING FROM V1.2***

***RESET 1200MHz UV SETTINGS BEFORE UPGRADING TO 1280MHz VARIANTS***

I'm not going to implement TINY_RCU and RAMZSWAP as they seem kinda pointless: the first should only work in SMP (multi cpu) systems, the latter... virtual ram swap in an OS that doesn't swap to begin with? Really?
[Captivate Android Development] krazyphire:
Awesome! Thanks setiro!
[Captivate Android Development] shaolin95:
Just to confirm, no need to remove lag fix to flash this right?

Thanks!
[Captivate Android Development] SetiroN:
I made a little mess with browser windows and my internet connection suddenly went down, give me half an hour to reupload everything.
[Captivate Android Development] tjsooley:
1.4 links went down
[Captivate Android Development] shaolin95:
Ok F5 like crazy to try this before lunch break is over lol
[Captivate Android Development] krazyphire:
So were the earlier versions fine? Bc I've already updated the kernel on my device lol
[Captivate Android Development] SetiroN:
Uploaded again. Please re-download.
[Captivate Android Development] bts0uth:
You are the man. I am upgrading now, going to try the 1280 version
[Captivate Android Development] slider2828:
Same here doing nandroid bu as we speak....

Xan's app doesn't seem to like it? Anyone else have issues with it?

17.7 MFlops for Linpack

but my wifi doesn't seem to want to connect
[Captivate Android Development] shaolin95:
Voltage Controller is not working for me neither
[Captivate Android Development] cappyron:
around the same linpak here, 17.6

Wifi working fine here though so far looks good :)
[Captivate Android Development] chipsa964:
+1. Root Explorer doesn't work for me either. I followed the precautions exactly, but for the 1280, you say reset UV settings for 1200, does that mean change them all to 0? or set them to the UV we had working before? (75, 75, 75, 100, 125, 125)
[Captivate Android Development] johan8:
With this reoriented, the original Samsung boot animation and sound is gone,

how to restore it ?
[Captivate Android Development] joeshmoe08:
Hello I have a question:

1)Can I use the JK3 modem with the setron 1.2.6 kernel? thanks in advance
[Captivate Android Development] SetiroN:
Did you download it again when I reported the issue I had?

When upgrading from 1.3 (which means using Xan's app v1.97+), you just need to set 1200MHz undervoltage (last value in the app, first in the script) to 0.

Sorry, you're out of luck. :D

I personally prefer the default animation and in order to use it, Samsung's one must be disabled. If you only see a black screen, that means you're using cognition. Don't.

Yup.

v1.4.1 OUT

fixed BLN (flashing as update.zip or re-enabling it from CWM might be necessary)
[Captivate Android Development] joedon3:
I'm using this on Perception Build 4 with the JK3 modem and it's working great!
[Captivate Android Development] johan8:
I'm not using cognition, and everything works fine.

And I have Samsung logo on power up.

Just wanna know if it possible to use i9000 default animation and power up music.

Is it possible to modify the boot script to re-enable it ?

:rolleyes:
[Captivate Android Development] bts0uth:
Voltage controler won't create the script for me. Using 1.98b.

Also can we safely use jfs lagfix and not worry about it corrupting if our phone dies

Posted from my Captivate running Perception build 3 with SetiroN's SuperOptimized kernel
[Captivate Android Development] slider2828:
kernel# 1401280...

but I will download and try again
[Captivate Android Development] chipsa964:
1.4.1 still not working well for me. Voltage manager gives me an error and I cannot connect to wifi. Root explorer also cannot get root access. I am running axura beta 3
[Captivate Android Development] shaolin95:
I am using Perception 1 and after trying this the phone started restarting on its own even when not doing anything just at 100mhz...I am going to try again.
[Captivate Android Development] bts0uth:
I don't get an error but the script just doesn't create.

Edit: finally it created it. I had to reboot a few times and press set on boot like 10 times. Try version 1.98b of xans app

Posted from my Captivate running Perception build 3 with SetiroN's SuperOptimized kernel
[Captivate Android Development] joeshmoe08:
Hello can someone please tell me what is the difference between jk3 modem and jpp modem?
[Captivate Android Development] slider2828:
Yup same thing just updated via cwm setiron 1.4.1....

No wireless, can't connect to APN either.....

Which method did you guys try? I am going to try the odin method... Knock on wood it doesn't blow up the lagfix.

***EDIT Same thing using the Odin Tar file*****
[Captivate Android Development] slider2828:
Search in some rom threads next time....

JK3 is for att and roger.... Its the latest modem file for North America 850 and 1900....

JPP is for 900 and 1900 band...
[Captivate Android Development] joeshmoe08:
Yes I read that but what difference does it make to the user (meaning I dont really understand 850/900/1900 stuff) Also which is the recommended modem jk3 or jpp?
[Captivate Android Development] slider2828:
Did I not just say North America JK3 and all other places JPP?
[Captivate Android Development] joeshmoe08:
oh ok really sorry... I thought there was also some other difference
[Captivate Android Development] slider2828:
Man this 1.4.1 1280 BLN kernel is really jacked....

No Wifi

No Voltage App

No CWM reboot into recovery

3 Button Recovery not working

Hopefully it gets sorted out... Going to see if 1200 works better.....

*** EDIT Nope... going back to 1.3.5 ********
[Captivate Android Development] lpsi2000:
I don't know what is going on with your install but WiFi is working here

Edit: 3 Button and CMW is working for me too
[Captivate Android Development] bts0uth:
No idea why your having those issues. Everything works just as it did in 1.3.5 for me. Wifi works and connects automatically after a reboot. 1280 overclock seems stable to me, got a linpack mflops score of over 18 and I've ran quadrant a bunch and have had no issues.

Posted from my Captivate running Perception build 3 with SetiroN's SuperOptimized kernel
[Captivate Android Development] schtuka:
I used 1200 version after flashing fix kernel.

Wifi at home works Do not have wifi at work so no comment, but Root Explorer works, Volatage 1.98 works fine, CWM works fine, 3 button boots in CW recovery. Applied Advanced ext4 fix after full reboot.

The only thing is that I was on JPM modem after JG8 with WCDMA 850 only and after applying this 1.4.1 kernel my phone still has JPM modem and still on 850 WCDMA.
[Captivate Android Development] MarlowXim:
Hey setiron can you reimplemrnt these two configs back. They don't cause any instability I was using a kernel that had them enabled, since you removed config customizations in previous builds.

PREEMPT_VOLUNTARY UACCESS_WITH_MEMCPY

Also since noatime was removed from optional mount options try instead nodiratime instead. Noatime was related ext4. Nodiratime should work with the different filesystems eveyon else is using.

You can mark as an experimental build. To separate it from your stable builds.
[Captivate Android Development] shaolin95:
Neither 1200 or 1280 is working for me...constant restarts...I will try later.
[Captivate Android Development] krazyphire:
Hey SetiroN I was wondering since I'm not having any issues with BLN (lights up for calls/emails, and sms) on 1.4 other than the BLN app not showing it as installed should I just stay? Just seeing if 1.4.1 isn't necessary for me
[Captivate Android Development] SetiroN:
To who's reporting connectivity issues/malfunctions/inability to boot:

you most definitely still have a corrupted /system partition.

Either you didn't follow the suggested upgrade procedure or it didn't work.

Please note that if you flash a kernel version preceding 1.4 you'll have to repeat the conversion.

***MANDATORY READ***UPGRADING TO V1.4***

As you might be aware, supercurio discovered a potential corruption bug present in Ultimate Lag Fix based kernels: v1.4 fixes it, but precautions are necessary when upgrading.

The fixed kernel might not be able to read your previous /system partition so following either of these procedures is NECESSARY.

Unfortunately, either #1 and #2 aren't flawless and there's a chance you're not gonna be able to retain system functionality with them. If that's the case you unfortunately have to reinstall your ROM as per procedure #3

Solution #1

- BACKUP with Titanium Backup and CWM

- Flash the specific fix kernel made by supercurio (odin version / CWM version)

- if the phone boots fine, go ahead and flash v1.4

- if you get stuck on boot or the phone boots but everything disappeared, flash back to v1.2.6/1.3.5 and try solution #2

- if you get strange connectivity/system/application issues, flash back to v1.2.6/1.3.5, you're gonna have to go with solution #3

Solution #2

- backup with Titanium Backup

- copy the v1.4 1200MHz or 1280MHz(reset UV!) update.zip to /sdcard

- reboot to CWM

- BACKUP

- flash v1.4

- reboot to recovery from 'Advanced ULK' (DO NOT REBOOT THE SYSTEM)

- advanced restore /system

- reboot

- if you get stuck on boot, the phone boots but everything disappeared or you get strange connectivity/system/application issues, flash back to v1.2.6/1.3.5, you're gonna have to go with solution #3

Solution #3

- backup with Titanium Backup

- flash your ROM of choice

- flash my kernel

- restore with Titanium Backup without system apps

IF YOU GO BACK TO PRE-1.4 VERSIONS YOU NEED TO REPEAT EVERYTHING

***RESET ALL UV SETTINGS BEFORE UPGRADING FROM V1.2***

***RESET 1200MHz UV SETTINGS BEFORE UPGRADING TO 1280MHz VARIANTS***

When upgrading from 1.3 (which means using Xan's app v1.97+), you just need to set 1200MHz undervoltage (last value in the app, first in the script) to 0.
[Captivate Android Development] Yuna:
Hi! How can i make this kernel to use original boot animation with sound? e.g logo and sound
[Captivate Android Development] shaolin95:
Well I am about to flash the last Perception Rom but he is still using 1.35 so I am not too sure how to edit that install file to replace the kernel with 1.4.1 to avoid the issues I am having
[Captivate Android Development] Yuna:
Also i seems can't make use of OCLF in recovery - after conversion - at lot of errors...
[Captivate Android Development] SetiroN:
I was already thinking about forking an experimental build with more aggressive optimizations, unfortunately (as you'll have noticed by my reduced posting frequency) I'm working a lot recently so I delayed it.

I already have to go but I'll make sure to meet your request as soon as I can, possibly tomorrow.

Yeah you should be fine.

You currently can't. As you're not first to request it, I'll think about reimplementing it in a future release.

Do you mean the app or the kind of lagfix?

Many of the app's functions don't work with my kernels, and as weird as it may sound it's actually related to samsung's playlogos being disabled. :P

You don't have to edit anything, just follow the instruction in the first post. :)
[Captivate Android Development] slider2828:
You sir are CORRECT!!! It looks like even if the system boots up when upgrading from Previous version to 1.4.1, there is still corruption.

Ran the SuperCurio fix and all is 100000000%%%% better!

its not just a mandatory read, its mandatory to do the steps. Thanks again!
[Captivate Android Development] slider2828:
Do the steps..... Pretty much mandatory. fixed all my problems.
[Captivate Android Development] jhnstn00:
Wifi works. Voltage control wont remember settings on reboot even though script is created. Root explorer works. Running Axura b3 with 1.4 OC at 1280

Sent from my SAMSUNG-SGH-I897

Edit: Band Aid for voltage settings to stick: Here
[Captivate Android Development] lpsi2000:
You might be onto something, I followed option #3 because simpler and easier to ensure you minimal issues.
[Captivate Android Development] joedon3:
Why would you want to use OCLF over top of ULF? You'll run into MAJOR issues! you can't lagfix a lagfix.....
[Captivate Android Development] darkamikaze:
what is 1.4.2 odin? is that a different version to 1.4.1 or just .2 because it's an ODIN flashable?
[Captivate Android Development] bts0uth:
Can we JFS lagfix without worring about corruption? Anyone know

Posted from my Captivate running Perception build 4 with SetiroN's SuperOptimized kernel
[Captivate Android Development] chipsa964:
All right, since it is working for you, I will try solution #3 one more time to the T and hope it works. Otherwise, I'm just gonna stick with 1.3.5
[Captivate Android Development] airbillion:
I would like to know this as well. Is it a newer kernel?
[Captivate Android Development] SetiroN:
It was just a typo in the filename, corrected.

Whoops, sorry I missed your previous post.

The issue you're referring to can't be circumvented in any way as it lies in the very nature of this filesystem: JFS delays writes for an indefinite amount of time so power interruption has an high probability of data loss. There's nothing I can do. :(
[Captivate Android Development] kangi26:
Setiro,

I'm getting ready to do a clean install of DG's Perception Build 4. Just so I know I have this right, I'm flashing back to JF6, Master Clear, install Perception, then CWM your kernel. Sound about right?

Thanks for your time
[Captivate Android Development] SetiroN:
It should be ok but I suggest flashing supercurio's fix kernel (see first post) right after the ROM settles, let it boot and only then flash my kernel.
[Captivate Android Development] kangi26:
Will do, thanks for the advice!

Is supercurio's fix mainly to enable the 850 band?
[Captivate Android Development] smokestack76:
Thanks for the info setiroN. This helps alot man.
[Captivate Android Development] bts0uth:
Ah, ok. Well I just converted to JFS to try it for myself lol

Oh well, I'll stick to ext4 then. Is there any benfiet to using the ext2 data loops? I can't tell if they make anything faster or not.

Also, I look forward to trying your experimental build when you get it finished :D
[Captivate Android Development] jhnstn00:
Actually I ended up using option 4. Took the kernel from SetiroN and put it in the Axura b3 ROM zip then flashed. Axura b4 will have it all packaged up if you can wait till tomorrow (likely). Posted it here
[Captivate Android Development] Kizzmiazz:
SetiroN, the voltage settings are not staying through a reboot again . Is a fix on the way ;) . I'm loving the new kernel with the new oc makes axura rom fast as hell . Thank you .

Sent from my Samsung Captivate | Flavor Of The Day - The Flash Addicts ROM of Choice | SetiroN's SuperOptimized ReOriented Kernel v1.4.1 ULF OC/UV and Screaming Fast
[Captivate Android Development] peachpuff:
No its because dg's rom still uses the old kernel that has a bug in the lagfix, maybe the newer version will use setiron's latest kernel, the 850 band should be enabled by default in dg's rom.
[Captivate Android Development] bts0uth:
Try it a few times. I kept selecting set on boot and I would check init.d and the script wasn't being created. Then randomly it was there lol I probably did it 6 times and rebooted a couple times in between.

Posted from my Captivate running Perception build 4 with SetiroN's SuperOptimized kernel
[Captivate Android Development] Kizzmiazz:
Well tried that , most have done it 50 times lol , and no script made :(

I honestly don't mind setting it manually every reboot but I am a lazy ass lol

Sent from my Samsung Captivate | Flavor Of The Day - The Flash Addicts ROM of Choice | SetiroN's SuperOptimized ReOriented Kernel v1.4.1 ULF OC/UV and Screaming Fast
[Captivate Android Development] Kizzmiazz:
Ok found a fix someone posted.

Sent from my Samsung Captivate | Flavor Of The Day - The Flash Addicts ROM of Choice | SetiroN's SuperOptimized ReOriented Kernel v1.4.1 ULF OC/UV and Screaming Fast
[Captivate Android Development] bts0uth:
Ah, just as I was about to attach my script for you to drop in init.d lol. As long as its fixed all is well!

Posted from my Captivate running Perception build 4 with SetiroN's SuperOptimized kernel
[Captivate Android Development] Kizzmiazz:
Thank you but yeah working perfect now.

Sent from my Samsung Captivate | Flavor Of The Day - The Flash Addicts ROM of Choice | SetiroN's SuperOptimized ReOriented Kernel v1.4.1 ULF OC/UV and Screaming Fast
[Captivate Android Development] JamieD81:
Running perception build 3 flashed 1.4.1 over top, got a 17.4 linpack and running smoothly, used the 1280 kernel
[Captivate Android Development] techmik67:
This is really a great kernel, imho.....
[Captivate Android Development] shaolin95:
Just flash Perception 4 and installed the 1.4.1 kernel and things are a lot more stable now, voltage is working etc.... awesome stuff... a little $$ coming your way this Wednesday mate.
[Captivate Android Development] Rhiannon224:
I am running version 1.2 of your kernel and haven't had a need to upgrade to any of the newer versions. I have been following the thread and I am wondering if I should apply Supercurio's fix, if this corruption is present I want to stop it now before it's too late. I still want to continue to use the 1.2 kernel, the modem works great for me, gps works, and I have hsupa, all combi bands are working. Is it necassary for me to apply the fix and if I do can I just reflash with the 1.2 version if the fix is successful? I am not having any trouble with my current setup aside from the known 2.2 bugs, occassionally wifi dosen't connect and I have an error when I go to setting--wifi, usually reboot fixes the problem, bugs that are associated with 2.2 ROMS and kernels due to no source code. Thanks!
[Captivate Android Development] crazililazn:
So far so good with v1.4.1 :D

1280 mhz is stable with .05 UV :D

However, i think Xan should make another voltage setting for clock speeds above 1200 mhz, because i was able to keep 1200 mhz at .10 UV before, but now i have to keep it at .05 UV so it is stable :/

EDIT: nvm, it was because of that little bug and the file was not saved in the right spot. .075 UV works fine for 1280 mhz OC! Thanks setiron!! :]

Funny how the 1.4.1 1200 mhz kernel saves in the correct spot, but the 1280 mhz one does not :x
[Captivate Android Development] KaLiBLeeK:
Flashed the 1280MHz kernel with CWM, using Method #2...worked like a charm. Just moved the S_volt script to the correct folder, like somebody mentioned earlier, tested it by rebooting...realized my phone couldn't handle -200mV. Haha.

Re-restored the /system via advanced recovery, set the UV to a more conservative level (-100mV)...and everything is working beautifully. Just posted a 17.19 on Linpack. Phone is running smooth as heck. I haven't been this happy with my phone since before Froyo was first leaked.
[Captivate Android Development] crazililazn:
D: your phone can handle 100 mv UV at 1280 mhz?! lucky :[ if i set it at 100 mv, it starts to vibrate randomly, and then has random reboots and crashes. :[

Your chip must be a good clocker, it would be fun to see who on XDA has the best overclocking cpu :D
[Captivate Android Development] KaLiBLeeK:
Haha; I may have spoke too soon. Got a few random freezes, including one where the shutdown logo froze. Bumped it down to -75 for now :)
[Captivate Android Development] crazililazn:
lol, that is literally exactly what happened to me D:

i wonder who has the golden chip that can handle 200 mv UV :eek:
[Captivate Android Development] Kizzmiazz:
I tried screwing with it fire a bit I'm running stable at 125,125,100,75,75,50 I tried 75 on 1280 and that was all good and bam big fc lol I was able to get 75 from 1200.

Sent from my Samsung Captivate | Flavor Of The Day - The Flash Addicts ROM of Choice | SetiroN's SuperOptimized ReOriented Kernel v1.4.1 ULF OC/UV and Screaming Fast
[Captivate Android Development] crazililazn:
lol kinda similar to me. i was able to get 100 with 1200, but i had to lower the UV for 1280. Well, guess it makes sense since it is a higher clock speed, but still... one can hope :(
[Captivate Android Development] KaLiBLeeK:
Haha; yeah, -75 seems to be the butter zone right now.

*knocks on wood*
[Captivate Android Development] Yuna:
SetiroN, can you make capacitive buttons to be MORE sensitive? I have em not such sensitive as on Eclair.

And can you fix Vibration on Home Button? e.g it don't vibrate. and Menu vibration is weaker than Searcn and Back buttons...
[Captivate Android Development] Dani897:
I get random freezing on 1280. It crashed during the under volt. I know I can't over volt for stability. Too much heat.

back on eclair with unhelpful kernel my phone benchmarked better undervolted, and was more stable at 1224 mhz undervolted.

Obviously I don't have the best clocking chip.

But I'm gonna rig up a heat sink in my phone and I'll post my results. Well really it'll be a heat coupler just a sliver of copper between the cpu and the aluminum chassis with some silver paste. I may also use copper tape to try to couple it to the back plate.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] aleadam:
root problems with update?

I updated to 1.4.1 1.20 mhz from 1.3.5 running perception build 3. I followed the "mandatory read", including supercurio's fix through cwm and the update followed by a restore of the backup.I even reset the voltages first, jist in case. Everything seemed to work fine, until I tried anything needing root, namely volt settings, root explorer or tibu. Superuser app shows that root access was granted, but apps don't seem to acknowledge that. Tried install superuser from recovery, one click unroot followed by one click root, etc. Nothing worked.

I finally went back to stock, install perception (build 4, should not make a difference) and applied the fix and the update through recovery, without rebooting and wiping without backup. Now everything seems to work fine.

I've seen several reports of problems with root explorer. I would think the problem is in the root, rather than in a specific app. I don't know whether the backup and restore broke something.
[Captivate Android Development] johan8:
I read the script, this is suppose to call default animation, but those lines are remarked.

And if I changed it, it will be revert during bootup.

How to make that work ?
[Captivate Android Development] bclark:
Same thing happened to me except I was using dilligaf's darky rom

Which btw all happens right as i am cooking Thanksgiving dinner. Yeah for multitasking!!
[Captivate Android Development] crazililazn:
Lol thermal paste on a phone. Nice. But i doubt its because of your temps. Your chip probably just can't handle the UV.