yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] joedon3:
I don't know, but I moved mine to noop. as far as how it operates, phones are typically doing 1 task at a time, or maybe a couple. No reason for all that overhead handling threads.
[Captivate Android Development] joedon3:
I'm getting the same thing on my phone running Tayutama's ROM

I saw something in the Vibrant threads that mentioned something about the ROM we're running. The startup scripts in the ROM may be breaking that function.

Anyone running Doc's ROM seeing these issues?
[Captivate Android Development] bts0uth:
First time I set to boot on Doc's rom it didnt save after a reboot but since then I just applied it and hit set value waited for it to finish and then hit set on boot and closed the program and they are staying
[Captivate Android Development] arffer:
I've confirmed that the scheduler setting really is being 'lost' by checking the current scheduler setting using OCLF. I set the scheduler to 'noop' in VoltageControl, and set it to apply at reboot. OCLF confirmed it was noop. I rebooted, and oclf then reported it was back to cfq.

I then tried changing the scheduler to noop again, this time using oclf. I rebooted, and this time the scheduler changes stuck, it was still set to noop.

So using OCLF for just the scheduler change is an option that sticks through reboot. Now to see if manually changing the voltage settinsg sticks through reboot.
[Captivate Android Development] arffer:
Yes, the settings stick through closing and reopening the voltage contrl app, its a reboot that they don't stick through. But as I reported above, using OCLF to change the scheduler setting does stick through a reboot. Now to find a way to get the voltages to stick.
[Captivate Android Development] joedon3:
I asked about this in Rasdeep's thread, hoping someone there might have some insight into the problem.

http://xdaforums.com/showthread.php?t=822027&page=29
[Captivate Android Development] arffer:
Undervoltage being lost

Nope, setting the voltages manually using the 'echo' method does NOT stick through a reboot either.

So, setting up your undervoltage is only good till the next time the phone is rebooted, at least till we find a solution.

EDIT: I also tried manually setting the undervoltage, and then did a chmod 444 (read only) to both of the undervoltage files.

Rebooted, and both had been changed back to 644 permissions, and both reset to '0'.
[Captivate Android Development] wesc011:
Im pretty sure i used both.
[Captivate Android Development] junktzu:
Do I need to be in download or recovery mode?
[Captivate Android Development] PAulyhoffman:
DL mode (10 Char)
[Captivate Android Development] junktzu:
Great, thanks for the help guys!
[Captivate Android Development] lpsi2000:
Setiron

Thank you

PAulyhoffman,

Thank you and sorry for your lost.
[Captivate Android Development] Yuna:
Which IO scheduler is more good for stability & speed?
[Captivate Android Development] aleadam:
Paul, I just wanted to say that I 'm very sorry for your loss and really grateful for helping SetiroN give so much to this community.

Alex
[Captivate Android Development] SetiroN:
Charging death may only occur on XT so it's not that big a deal.

BFQ or Noop, depending on load. The former is more suited for heavy multitasking, the latter in the opposite situation and thus is preferred by many smartphone users.

This should cover every possible need:

SetiroN_v1.4.6xt_1460.tar.7z (lower GPU clock)

SetiroN_v1.4.6_1460.tar.7z (lower GPU clock)

SetiroN_v1.4.6xt_1450.tar.7z

SetiroN_v1.4.6_1450.tar.7z

SetiroN_v1.4.6xt_1400.tar.7z

SetiroN_v1.4.6_1400.tar.7z

SetiroN_v1.4.6xt_1350.tar.7z

SetiroN_v1.4.6_1300.tar.7z

SetiroN_v1.4.6xt_1300.tar.7z

SetiroN_v1.4.6_1350.tar.7z

SetiroN_v1.4.6xt_1280.tar.7z

SetiroN_v1.4.6_1280.tar.7z

SetiroN_v1.4.6xt_1200.tar.7z

SetiroN_v1.4.6_1200.tar.7z
[Captivate Android Development] aleadam:
Confirmation number: 5NT1699204573352R

To help with the taxes at least :)

tanti saluti
[Captivate Android Development] shaolin95:
WOW, Setiron came back in full force! :D
[Captivate Android Development] momulah:
Is there a reason CWM versions are stopped? I have no usb on my shi**y computer. Can someone make 1.4.6 1200 CWM? Please!!
[Captivate Android Development] smokestack76:
Yeah he did. Glad everything has worked out so far man. ;)
[Captivate Android Development] SetiroN:
No particular reason, I'm just too lazy to upload twice the files.

You can open a previous CWM version with 7zip or alike and overwrite zImage (drag&drop) in /kernel_update/.
[Captivate Android Development] DAGr8:
+1 000 000

btw here is a post by PAulyhoffman (THE guy ) , the least we can do is spam him with thank you's

http://xdaforums.com/showpost.php?p=9791148&postcount=1982

oh and yea flashing is on... like donky kong ...

EDIT : both 146 and 155 freeze on boot for me ... althoug running at 1504 mhz doesnt freeze on boot on past kernel Im back to 145 ..
[Captivate Android Development] shaolin95:
Ha that easy? I thought more magic was involved! lol
[Captivate Android Development] MarlowXim:
Bugs possibly Jpu related

1.4. 6 and 1.5. 5 do not execute scripts in init.d

1.5.5 cpu set on boot 1ghz doesn't come into effect. Most noticable in clockworkmod lock ups careful flashing.

Cosmetic

1.5.5 missing default bootup animation most likely the directory it searches for animations has been moved

Suggestion

Possibility of updating cwm there's a bug in which doing restores or format cannot restore system.img. Basically anything that is related to system partition. Found in 1.4. 5

Discovered workaround flash supercurios voodoo kernel I9000 version and do system restore. This only effects Jpu based roms.
[Captivate Android Development] PAulyhoffman:
1.4.6 did not read mine either. *note when flashing different ghz remember to remove boot settings in voltage control. when i went back to 1.4.5 it would freeze because the one I saved in 1.4.6 was there. (even though it wouldn't read in 1.4.6)

also, 1.5.5 did not make it past boot up. I am guessing it is not defaulting to 1ghz as anything 1400 or more will freeze my phone immediately.

I am happy with what is working until SetiroN can test on his own. hopefully we will be counting days and not weeks.
[Captivate Android Development] Rhiannon224:
I just flashed 1.5.5 with Odin and I am frozen on first boot screen, lol, I guess I need to pull the battery.
[Captivate Android Development] techmik67:
A small trick....... instead of pulling the battery, just hold all 3 buttons (both volumes and power). It takes about 10 seconds, but then it reboots..... from ANY mode or freeze...... haven't had to pull battery in a week, and you KNOW how much I flash =)

:D:D
[Captivate Android Development] shaolin95:
Actually its just volume up and power...at least on my phone :D
[Captivate Android Development] Rhiannon224:
Yes, that's exactly what I did, it even froze in Recovery Mode, lol. Flashed back to 1.5.2 lol and my battery dropped 50% holy ****.

update: That was weird, I just flashed the JK4 modem with Odin and now my battery is back to 66%, I hope this modem fixes my GPS that sucked on JK3 and the LJL3 modems. It has been flawless on every 2.2 build up until these modems.
[Captivate Android Development] MarlowXim:
Your battery indicators are wrong you'll need to fully charge and let it charge overnight. Then boot into recovery and in cwm advance features wipe battery indicator. That should correct it.
[Captivate Android Development] Rhiannon224:
Thanks I am aware of the steps. Actually it was correct after I flashed the modem. No way did I lose 40% flashing the kernel. I will recalibrate tonight anyway.
[Captivate Android Development] Doug8796:
hey guys im on assonance 3.1 .. what settings are going to give me the fastest cpu/gpu and highest ram?

I need these because I am alpha testing a dreamcast emu for the captivate.
[Captivate Android Development] shaolin95:
Try one of setiron's 1,6ghz capable kernel although I have yet to see anyone hit that so in the 14xxMhz is where you will end with luck :)

I cant wait for that emu to come out...Skies of Arcadia on the go?! OMG! :D
[Captivate Android Development] Doug8796:
This may be dumb, but do you think if I manage to take apart the captivate and apply arctic silver it will allow it to reach higher speeds? What are some of your thoughts on this? Also, shaolin. What is the highest confirmed nenamark score you have seen? I have heard an OC'd vibrant got 67fps.. i am getting 50.9 now.
[Captivate Android Development] shaolin95:
well artic silver first of all will be too risky in such a tiny space in my opinion and there are a few better thermal pastes.....on the other hand, I have never tried that on a phone so it would be pretty awesome but you can try a simple test...run an OC stock then put the phone near your fridge so it drops temp a few degress (rough aproximation of normal thermal paste improvement) and see if it helps. This is a silly test maybe but heck it might help lol

Good luck either way...I hope the emu used the power vr in the galaxy..if it does then it would be a LOT better since it is very powerful

I have only been hanging around the Setiron kernel thread and every 1.6 claim I have thing has not been backed up with any evidence so in my book, it is yet to happen.

The old 1.6 Ghz results that were posted some time ago I was told by a respected person was just a mistake + slowing down system clock which made the boosted benchmark scores....
[Captivate Android Development] johan8:
Just press Vol up + Power during ANYTIME !

no matter your phone is runnning or freezing,

just press UP+Power for a couple second, your phone will reboot itself.

:rolleyes:

You don't need 3 buttons.
[Captivate Android Development] davwman:
Tried to find info on the additional tweaks in recovery for 1.4.3 and could not. Can someone give me a clue what they are? Ir point me in the proper direction.

Sent from a ginger keyboard on the xda app.
[Captivate Android Development] Rhiannon224:
They are located in the Recovery Menu. Navigate to Advanced SpeedMod ULK features choose that and the next menu is where the tweeks are.
[Captivate Android Development] davwman:
Thanks. I know where they are, I was more curious as to what they do?
[Captivate Android Development] johan8:
Great appreciation to PAulyhoffman for his giving !

And huge appreciation to Setiron for your work.

I can't get 1.5.4~5 work on my phone, it just hang after media scan....

1.4.5 will reboot during system load, such as using Layer, it use wifi or hsdpa and gps disk buffering...., and phone will shutdown during charge.

Now I'm testing 1.4.6, played a couple minutes, it seems much better.

But it doesn't play the original startup animation, mounted system as RW.
[Captivate Android Development] Doug8796:
does 1.4.6 support ~1.4x ghz?
[Captivate Android Development] Nickel Dime Bay:
Theres a lot of love in this thread, thanks to all of you. Without you guys i'd probably be on an eyephone right now.
[Captivate Android Development] Peaster111:
Yes... 1400 & 1450. Take a peek a page back. Setiron has all the downloads posted. Have fun and good luck!
[Captivate Android Development] Doug8796:
i just bricked my phone.. i thought this wasnt supposed to happen? 1.5.5 assonance 3.1. update.zip success and hangs on android screen.

5. Allow the phone to boot. This will take an abnormally long time.

How long? Assonance did not take this long :\
[Captivate Android Development] Stephenv1971:
Relax, its hung from the improper oc settings everyone has been talking about all day. Grab the odin version of 1.4.6 (not xt) 1200 version. Get odin 3 and flash the extracted tar image (its in th 7z) to thr pda slot. You should boot fine now.

tips:

pull battery, put battery back in, start odin, hold vol +/- at the same time while plugging in usb.

make sure you have correct drivers, look for the captivate bible, I think its at the top of this forum
[Captivate Android Development] johan8:
Yours is not brick, far from it.

Seems that 1.5.5 is not working on yours.
[Captivate Android Development] johan8:
No need to pull battery anymore!

No matter your phone is running or freezing,

Just hold VolUp+Power for a few second, your phone will reboot!
[Captivate Android Development] johan8:
1.4.6 comes with 1200,1280,1300,1350,1400,1450,1460

check the first page you will see all the update.

Used for couple hours, 1.4.6 seems quite stable to use !

:)

However the original boot animation won't start,

CIFS module not working, I can't mount samba network share, sounds like the module doesn't compatible with the kernel.
[Captivate Android Development] Yuna:
SetiroN, how did you increase wifi perfomance?

I have 2.4Ghz 11n router near the phone, and it connects only at max 72mbps, usualy 65mbps...
[Captivate Android Development] johan8:
I think it is hardware problem,

iphone, android also have such reception weakness.
[Captivate Android Development] Yuna:
nonono, it's not a reception issue: i have -32dbm signal... it's just the speed of connection... look's like wifi is limited somehow... also i have on froyo x2 pload speed than on eclair via speedtest by ookla
[Captivate Android Development] FocuseD83:
Wow... Very impressed with the 1.4.6 kernel @ 1.45ghz so far... Stable as a rock and blazing fast... Has anyone had different results?
[Captivate Android Development] johan8:
I know what you mean, but somehow the reception is so weak so the bandwidth will also drop.

In my office the wifi just 10feets apart , N82 get 100% signal, but i897 just 50~70%, sometimes it will drop connection, just like my colleague who is using ip4.

So I think they all have problem.
[Captivate Android Development] Doug8796:
what settings do u use at 1.4ghz to keep stable?
[Captivate Android Development] xan:
Since most of you guys had problems with latest version of VC, I've posted an updated one, which should be working better :)
[Captivate Android Development] TheYar:
I forget where I posted this already - but so far on my phone I have pretty conclusively isolated the USB and chargining death - they only occur when I use noop and never occur for me on bfq.
[Captivate Android Development] glitterballs:
How vigorously have you tested this? I'm starting to think more and more it's a hardware issue because A.) No one using an i9000 phone has this issue, B.) Some people with Captivates aren't having this issue, C.) If you catch a log of it happening, there's no shutdown, no errors, nothing. The phone is completely losing power, however briefly.
[Captivate Android Development] shaolin95:
I used to be on noop all the time and now on bfq and neither one had that issue for the record.
[Captivate Android Development] bts0uth:
How come in Root Explorer when I try to view the files in init.d as text or open in text editor they are always blank? Every other file I can open and it has text but init.d does not.

That includes the zipalign.sh and everything.

Also, do we need the s99_FREQ script for 1.4.6? I have the 1350 version installed but Linpack scores are in the 14's which obviously isn't right.
[Captivate Android Development] tcaudill01:
I do love how fast it makes everything run, but I'm not loving the reduced battery life. Can someone give me step-by-step directions on how to reduce the speed back to stock as I can't seem to figure it out?

Any guidance would be appreciated.
[Captivate Android Development] slider2828:
I have had the same F...ing issue and no one really ever responded.... The data is actually still there you just can't see it no matter what permissions I give it. My work around was to copy the 3 startup scripts to the external sd card and open it there. Its should be visible there. Make your edits and overwrite back onto the internal sd....

Only work around I have found....

THe built versions of 1.4.6 don't need the Freq script, but it does need the S99 volt script and of course xan's volt script created by VC.
[Captivate Android Development] bts0uth:
I noticed they were all different sizes so I figured they were still there and not actually blank like it was showing. I will move and edit them and move them back and see if they actually execute at startup.

I guess I have another issue though, quadrant shows max freq at 1350 but yet linpack scores are 12-14. Normally for 1350 O/C they should be 17-18.

Seems like it's not actually overclocked and I am using version 1.4.6 so I thought it should be enabled by default.
[Captivate Android Development] JPxM0Dz:
Same issues for me, so I continue to stick with v1.43-XT

Sent from Axura RC 2.1 Captivate Edition
[Captivate Android Development] slider2828:
Yeah I am back to 1200 as my phone I think is not handling any OC's any more past 1200.... I think its just the frequency of me trying to OC or something I don't know.... So yeah even at 1200 my linpack is at 16.6 consistently.

Quadrant is back at 2000+ since I am now using ext4/ext2/ext2 binds.... Its a lot better than just ext4, but obviously more prone to corruption I think
[Captivate Android Development] bts0uth:
are you using version 1.4.6 or an older one?
[Captivate Android Development] Doug8796:
Setiron.. I am testing an alpha of a nullDC (Dreamcast emulator) for android. I am using your 1.4ghz oc. I was wondering if you could perhaps make a higher gpu clocked build (lower cpu) for testing :)
[Captivate Android Development] aleadam:
OC and reduced battery life: Really?

I was playing a little bit these days logging the cpu freq every 10 seconds. The app creates a csv file that I then plotted using openoffice.

The three runs were using the same kernel (1.4.5 @ 1.3 GHz) and Assonance 4.3. The first may have been with the JK4 modem, the last two for sure with the jl3 modem.

Caveats:

- The service I was using does not seem to log during deep sleep (although it does not get killed and quickly resumes logging)

- It reads /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq every 10 seconds. I don't know what happens in between.

- As a kind of Heisenberg uncertainty principle, there's no way to look at the cpu without using the cpu, thus changing the system. The app is designed to minimize cpu usage (minimal ui, short sdcard accesses, no whistles and bells) but it could be that the app is increasing the clock by itself, specially at low freqs.

- This is in no way a controlled experiment. I was just running the app in the background and using the phone normally.

Results:

- Standby time and moderate/heavy use can be easily distinguished by looking at the graphs.

- Typical standby frequencies range between 200 and 400 MHz.

- Most of the cpu time during phone use seems to be at 400-1000 Hz. 1.3 GHz frequency use is rare and seems only required for peak usage.

- The short 1 GHz peaks seen during the long standby time (overnight) are probably google, fb or yahoo mail syncs.

Conclusions:

- Battery life should not be really impaired by the use of the oc kernel.

- Battery could be much more improved by optimizing the frequency usage in stand by (try to force 100-200 MHz).

If I have time I may try to test it a little more carefully, in a recently flashed rom without so many apps installed and no sync set.
[Captivate Android Development] double RL:
Ext2 loops never last more than five or so days for me. I start getting fc's and just have to reinstall the rom. I've finally just settled for all ext4 and tweaks. I need stability in my old age I guess! :eek:
[Captivate Android Development] double RL:
Ok, I give up. Can anyone get voltages to stick on reboot? I'm using 1.4.6 1280 and they will not stick no matter what I do.
[Captivate Android Development] bts0uth:
No it's bugged in 1.4.6. I'm sure SetiroN will have a new version up with it fixed soon.
[Captivate Android Development] double RL:
Ok, thanks. I'm sure it has been discussed a million times but I just have not been able to read as much as I usually do.
[Captivate Android Development] johan8:
You need 1.5.x for the bootscript so you can stick those setting during bootup.
[Captivate Android Development] johan8:
Me too, ext2 loop is fast in scoring but it cause data corruption so lots of FC will come out.

Don't just look at the score, you need stable and smooth operation..
[Captivate Android Development] joeshmoe08:
Hello just a quick question. are the 1280 variants all gpu underclocked? Specifically I want to know if kernel 1.4.3 1280 has a gpu underclock or not.

And if it is underclocked then does it means gaming fps will be less?
[Captivate Android Development] junktzu:
From the OP it looks like 1288 has an underclocked GPU. I seem to remember SetiroN saying that even though the GPU was underclocked the overall performance would be better due to the CPU overclock.
[Captivate Android Development] joeshmoe08:
Ya but won't the gaming performance specifically be lower?
[Captivate Android Development] Doug8796:
If possible i would really like to see a Highly clocked gpu (at the exense of a lower cpu) :) to do tests
[Captivate Android Development] junktzu:
I wouldn't think so since games use both the CPU and GPU. It would be easy to test since there are multiple 3d based benchmarking tools out available.
[Captivate Android Development] Doug8796:
Setiron 1200 is actually faster than both 1344 and 1288.. only thing that beats it is 1400.

For High performance graphics tests
[Captivate Android Development] PAulyhoffman:
I used to be held up by the scores. Ext2 gave me FCs in places I didn't know I had. So I ran ext4 and then voodoo which have lowest scores. I found real life use kicks scores ass. They aren't meaningless just a bad tool to determine speed and stability.

Hopefully SetiroN gets his phone soon and can iroN out the bugs on the untested version versions.

in the mean time we can hope he is taking some quality personal time.
[Captivate Android Development] slider2828:
I am using the 1.4.6 1200MHZ version. Hmmm maybe I will take out the ext2 tweaks hearing all the data corruption that occurs....
[Captivate Android Development] double RL:
It yields some high ass scores, but doesn't seem to have any real benefit for the ui. If you have everything you need to reflash your rom and kernel on your sd card then it's not too big of a deal once the fc's start. :D
[Captivate Android Development] Peaster111:
Yeah... stick with "ext4 all". It safer and beats RFS (of course). I've experimented with other settings in the past. Conventional wisdom of experienced folks will usually advise ext4 all. I don't even waste my time trying anything else nowadays.
[Captivate Android Development] shaolin95:
yeah something is not right with 1.4.6 4500Mhz...I get 17s linpack yes the 4.6 version gets me almost 20!?
[Captivate Android Development] djfrost40:
I have been trying to install this new kernel in cwm, but once i choose it as line item from the update from sd card, it starts to install it and then aborts it, it says there was a error at line 2, any suggestions?
[Captivate Android Development] PAulyhoffman:
which kernel?

if you are trying to flash 1.4.3xxxx than maybe you have a bad download. CWM is set up to flash zip files. Those are the only kernels SetiroN has in zip file.(for installing via CWM)

anything else is set up as a tar file which you would need to install via Odin

http://cognition.theidiotshideout.net/mw/index.php?title=ODIN

use the stand alone and drop the file into PDA

hope this helps

if you let me know which one you are trying to CWM i can make it a zip for you if you don't feel comfortable using ODIN.
[Captivate Android Development] johan8:
Both 1.4.6 and 1.5.5 are currently in Odin flash file format,

it is Not for CWM update.
[Captivate Android Development] speshow:
does anyone know how to make the oc sticks after reboot. M running 1.5.5 at 1.4 pretty stable so far, but cant get it to stick after reboot.
[Captivate Android Development] dambrosioj:
ditto to this
[Captivate Android Development] existz:
You have to make a startup script...its on the front page
[Captivate Android Development] double RL:
Startup scripts are currently broken I believe. Unless something has changed, nobody is able to stick settings on reboot with 1.4.6 or 1.5.5. Just have to reset them after reboot.
[Captivate Android Development] aleadam:
It's a known issue of the last SetiroN's kernels. We'll probably have to wait until he gets his new phone and can test the builds again...