yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] bamonkey:
the skeptic in me skoffs when you say no phone has had trouble at 1300.. probably because no matter what method ive used ive locked up even at 1280 even comming from a fully stock flash. THAT being said though ive always been curious each time to see if something would change at the lower end to allow these crazy speeds. so i shall try this game again of flashing to stock and see if 1.4.5 really can make a christmas miracle for my phone ;)

edit: well, it still locks up about 30 seconds after the launcher comes up so no dice here. btw it sounds like maybe your a bit antsy from the last post? *shrug* hey if it makes you feel any better im the type to love to be proven wrong. alot of people around here will say you cANT do this.. you CAN do that and just say IT IS. i love it when something comes along to shoot it all out the window. people are saying the GPS is borked and JUST IS but hey its gotten better and better at least every month.. TONS better than the stock. who knows why some phones are having no trouble keeping stable while others right now are just touchy *usb charging issues, unable to OC very high if at all, some people STILL have poor gps, and others just say theirs turn off in the middle of the night lol* Who knows what the hell is up with our phones right? its just fun to push the damn thing where even samsung never thought off. thats why im here everyday, because all the devs here do extreme things for all of us...usually without getting much in return. So for what its worth thanks for putting up with the crap and hopefully you continue your path of awesomeness lol

ok //rant over//

edit 2.1??? i cant call it yet but after quickly changing back to stock clock after booting i decided to change some voltages in an extreme way *-100 on 1300* it almost took so i back down to -75 and for now its stable and i was able to browse the picture gallery which usually always makes it immediatly hang. first time above 1200 here so ill let it float a bit and see what happens. its not burning up in my hand thou so im optimistic
[Captivate Android Development] shaolin95:
And yet it took different settings and a lot less work to get it stable...but then again, when has OCing being a "normal" thing? I have had bios settings that I knew were perfect suddenly stop working...then I had to start slowly getting there again and end up with the exact settings that once again work...gotta love it :D
[Captivate Android Development] XGX5309:
Wow. I guess chip yields are pretty differentiated then. I'm running Assonance 4.3 with a couple of personal mods and I can run 1.4GHz with no issue at all. My phone doesn't even get but slightly warm when pushed. I'm going to try 1.6GHz a little later today and see how that runs. I would guess just fine.

On a seperate note, BLN just wouldn't turn off, even if it were turned off in recovery. I had to install BLN Control from the market and disable it with that. For some reason that stuck.
[Captivate Android Development] johan8:
Just the score is pointless.

I would like to absorb the score for better data integrity.

With 1.4.5, my phone rebooted just now....

I don't need wired headset, try go back to 1.4.3
[Captivate Android Development] aleadam:
You used to have the link to the instructions in the OP. It made a big difference in quadrant scores when I did it, but not so much in usability. I got data corruption, though :eek:

Here's another example. I just installed assonance 4.3 (with the 1.4.5 kernerl @ 1.3) and even though I really tried to bust it, I'm still waiting for the first f/c or lock...

I'm now using the same UV settings as with the 1.4.3 @ 1.28 (-75, -100, -100, -125, -125, -150 noop. It worked fine also with no uv settings at all.

Yes, quadrant scores were much lower than before, (1800+ to 1500) but this one feels even snappier. Maybe not so much when I transferred all my tibu backups from my pc back to the sd card, but who cares about that?

Linpack scores were still very high and I think they represent much better the daily usability.

So, thank you for another fine release :)

I'm tempted to try the 1.5.4 now...
[Captivate Android Development] TheYar:
Sorry... I was just trying to end that post on a positive note, like so I'm not just complaining. My intended point: ignoring the particulars of certain versions or people's individual hardware units, setiron in general is the best kernel I've flashed. Didn't mean to imply that version x.y.z was totally better than the one after it, other than the specifics of my own experiences. IRMV on the different versions, definitely.

EDIT: In regards to the home button issue above, I had the same problem on one of my 1.5.X flashes. It was also with an Assonance ROM. But I haven't had it happen since then on other setiron flashes or other kernels/ROMs. So I don't think it's a failure of the button.
[Captivate Android Development] shaolin95:
You are cool man , I mean, you got a Yar's Revenge avatar! Memories..... :D

Setiron, in 1.4.4 what is the voltage for 1360 and 1400?
[Captivate Android Development] DAGr8:
thx button is up , time to spam the hell of setiron with them !!!
[Captivate Android Development] aleadam:
First! :p

I rather should show him my appreciation through paypal instead of pressing a button... :rolleyes:
[Captivate Android Development] existz:
Make sure you have busybox installed...

(ps) I live about 45min east of Lexington...rarley see anyone else from around here
[Captivate Android Development] DAGr8:
Lol more like second

sent from the future using xda app
[Captivate Android Development] Peaster111:
Big Kudos to setiron on 1.4.5. I've been using the 1300 kernal on my own Bell based build since it came out. It's running super sweet. It's seems smoother than 1.4.3... just a seat of the pants feel. No sleep death, random reboots, wifi issues, etc. Battery life seems the same as always... no noticible change.

The best kernal l've used... Thanks!

Hummm... I wonder if my phone can handle 1400?
[Captivate Android Development] slider2828:
All settings are from jf6 master clear. You aren't serious that the scripts survive through that. Of out does how doo you fix it?
[Captivate Android Development] ReedX50v:
Well, if your install order is JF6 -> Some JK3 rom -> Setiron's kernal, then:

The JK3 rom you are installing may be writing its own scripts before you upgrade to setiron's kernal. (?)
[Captivate Android Development] Dani897:
what exactly does xt stand for in some of the file names?
[Captivate Android Development] peachpuff:
XT variant: 1xxxMHz, config optimizations: HZ=500, PREEMPT_VOLUNTARY, UACCESS_WITH_MEMCPY, KSM (possibly unstable, slightly higher performance and battery drain, might be necessary to lower UV)
[Captivate Android Development] johan8:
Mine can't run stabely with 1.4.5,

only 1.4.3 or previous version run stable on my captivate.

don't know why....
[Captivate Android Development] Da_G:
xcal updated with a fix for the internal sd being mounted as a cdrom in JPU. Btw both my captivates won't run stable at 1300 no matter which UV, they work ok until being put under heavy GPU + CPU load, then freeze (probably a kernel panic, but i'm not sure how to receive a notification of a kernel panic, since there's no hw watchdog)

1280 is stable with a uv on both (but not at the set voltage, so only with a startup script to lower it asap)

1200 is rock solid on both.

So count me in as wanting a 1280 or 1200 on the next iteration :) 1300 is juuuuuuuuuuust a hair too fast to be stable on my devices.
[Captivate Android Development] Yuna:
Agree.. I too want a 1200 Mhz variant - speed is a not a big essence here, but feelings and stability :)

BTW: SetiroN, i am at 1.4.5 - CAN"T make working CIFS...
[Captivate Android Development] johan8:
1.4.3 1280 is running perfectly in my cap.. (I haven't try 1350 1400....)

But 1.4.5 1300 will freeze or reboot after using for a while.

I'm not sure that 20Mhz will panic, but maybe.

And I never got 1.5.4 running properly, even just 1200 is enabled.

Setiron's kernel is good but can't use new verions, just don't know what to do....
[Captivate Android Development] johan8:
According to log file, the module is missing.
[Captivate Android Development] aleadam:
Soo... last night I got my first sleep of death :(

Had to do a battery pull. The battery was about 20% full when I turned the phone on again.

I remember your big red warning "revise your uv settings" so I will blame it to my heavy undervolting for now. But, I have a couple of questions to try to understand the issue:

Is there a heavier load on the cpu while charging than normal?

Why an extremely stable phone during whole day usage will freeze at night? The phone was on and off the charger during the day, just not for that long.

What settings do you think we should adjust? Low or hig freqs?

I will try to write a small app to log cpu usage tonight while charging. That way I will hopefully answer those questions and see at what freq it dies (the log should stop there). Problem is, I'm not sure how to read a system file from a regular app. I guess I'll have some reading to do today ;)
[Captivate Android Development] Peaster111:
I completely agree with your thoughts. While I appear to be stable at 1300 this is not true for many folks. I consider myself fortunate. 1200 would be the best to ensure stability and have the great appeal for everyone.

1200 would be the best option for rom chefs as well.

Da_G... Hint Hint... Master chef. ;)
[Captivate Android Development] johan8:
Take a look of Preception known issues,

in OC/UV version phone will freeze after usb unplug, charging death.....

other rom also has such problems,

Sounds like the oc/uc modules has a serious bug !

Now try 1.4.5 again.

By manually change scaling_max_freq to 1250000 i/o 1300000 after bootup,

my captivate seems working fine now.

But during charging it will reboot.......
[Captivate Android Development] momulah:
1.4.5 cwm

Is there a CWM version 1.4.5? My phone cannot connect to my computer using usb. I tried everything. It has to be something wrong with my usb and motherboard.
[Captivate Android Development] geokhentix:
Making CWM flashable: (ONLY FOR THE KERNEL!)

1. Make a folder called ROM on your desktop

2. Inside thsi folder, create 2 folders "META-INF" and "updates"

3. Put the zImage from the .tar into the updates folder, as well as redband_ua(grab a copy from another rom / cwm flashable)

4. Inside the META-INF folder, make a folder named "com". Inside "com", make a folder named "google". inside "google", make a folder named "android", and leave the folder open.

5. Open notepad++ and paste in..

show_progress 0.1 0
copy_dir PACKAGE:updates TMP:/updates
set_perm 0 0 755 TMP:/updates/redbend_ua
run_program /tmp/updates/redbend_ua restore /tmp/updates/zImage /dev/block/bml7
show_progress 0.1 10

There is a blank line after show_progress 0.1 10 VERY IMPORTANT

6. Save it named "update-script" [all files, no extensions] in ROM/META-INF/com/google/android

7. Go back to the ROM folder and highlight both the updates and META-INF folder, right click, add to, compressed folder.

8. Rename the .zip to update.zip

9. Download SignApk and extract it into the rom folder.

10. Open a terminal and type

cd %USERPROFILE%/desktop/ROM
java -jar signapk.jar certificate.pem key.pk8 update.zip updatesigned.zip

11. Push it to your phone and flash with CWM!

This will work for any flashable CWM, but the update-script file must be different depending on what you're flashing, so if anyone is reading this thinking they can use this above to cook an entire update.zip with a system directory and such, don't bother trying, it won't install unless you modify the update-script

As for the things you need to download, google is your friend.

On a late edit;

Signing the update isn't always required, but I added it for good measure. In terms of strictly flashing zImage, you don't need to sign it, just arrange and compress it like above and it will flash.
[Captivate Android Development] momulah:
Sorry no go I tried everything. Running windows xp and for some reason my computer only acknowledges 1 of 4 usb ports. I can charge only on the rest. No biggie new lap coming soon...
[Captivate Android Development] shaolin95:
Setiron any chance of getting the 1.5.x for JPU...specially the one with steps 1360 and 1400 ?

Thanks!
[Captivate Android Development] SetiroN:
Sorry for disappearing guys, I wasn't in the mood for posting or working on the kernel: unfortunately it looks like I bricked my phone.

I couldn't believe it myself but as soon as I restarted it phone after CWM-flashing my usual JPO rom, going back from official JPU+803.pit, the screen went black and never came up again, no matter the key combination. No signs of life besides warming up slightly after pressing power or connecting the USB cable. No luck with a JIG cable aswell, tried all the way from 290K to 315K Ohm and nothing happens... I guess there's nothing I can do.

The problem is, I came back to Europe last month and official Samsung centers around here are refusing to offer repair services on US phones because of some kind of freak policy they have, even if I pay myself. I could try an unofficial repair center but they're probably going to charge me an unfair amount I'm not willing to pay.

Anyway I'll try to come up with the versions some of you've been asking for in the last few pages in a couple days, but that'll be all.

Special thanks to my donors (in chronological order, last to first):

ReedX50v, junktzu, shaolin95, Shane, krl66, Smokestack76, Henry, Xstop, lpsi200, Arffer, newter55, Lertets, txRangerXDA, id10terrordfw and Bedwa

your appreciation is what made me happy to come up with new versions. THANK YOU!

I feel sorry for letting you down, but getting another Captivate shipped to Europe would cost a ton in shipping+customs (20% taxes and $80 for a decent shipping method), not considering the lack of warranty, and I'm not really up to it.
[Captivate Android Development] Yuna:
Oh no... Where we must go now? I tried to use Reoriented kernel - laggy as hell...
[Captivate Android Development] smokestack76:
I hate to hear that man. I hope you can get yours working again. We will be lost without ya :)
[Captivate Android Development] johan8:
I'm so sorry to hear that.

If JIG not help, then the bootloader is really corrupted.

Other than offical repair, maybe you need to look for Jtag repair.

Btw, your kernel is the best I have ever used.

However the recent new OC kernel has dead loop problem, that's not your fault,

hope that you can back to development very soon.
[Captivate Android Development] aleadam:
Dude, that sucks so much. If you're planning to get a riff box let us know (that's what you would need, right?). I am sure many of us will help with the cost. I don't know where you are located, but I saw it for about 100 pounds in a uk based website, so if 15 of us chip 10 bucks each, we're covering the cost. That, or any other repair you decide.
[Captivate Android Development] ReedX50v:
Well that is a shame, but understandable. Smartphones have a shorter life span than the old pdas anyhow.

1.4.5 is definitely and awesome kernal to retire on.

I am curious if you would be willing to post the pre-compiled source files? Would be nice to make some tweaks here and there.
[Captivate Android Development] xpamiceftk:
Thanks for doing so much. I is using the SetiroN1.2.6 and 1.3.5 for long time. I think it is good enough expect that it can't use the wired headset .Can you fixed wired headset of 1.2.6 or 1.3.5?

If it comes ture, I think it is perfect.

Thank you again!:D
[Captivate Android Development] krl66:
Setiron, you've done so much for this community I think it would be perfectly fair for us to contribute to your costs here. I'll gladly chip in again. I'm sure others will, too. But hey, its gotta be a pain to do all this for so long and put up with all this silliness, so if its time to retire, its time. You're a great guy. Thanks for all you've done. And if you wanna stay in, let us know the costs... I'm in.
[Captivate Android Development] junktzu:
I feel the same way. If you want to continue doing this let us know and we can start some sort of fund raiser or something to get you a JTAG so you can unbrick your phone. If not then thanks for all your hard work!
[Captivate Android Development] shaolin95:
'Now is the time to

REALLY

show the appreciation for Setiron and his work guys so lets start to collect the money to get him a new Captivate ....where should we do this and how? We cant let this wait too long as new ROMS are coming out for the JPU stuff and I know we want Setiron Kernels for it...screw stock speeds! lol

So what do you say guys?! :)
[Captivate Android Development] bts0uth:
I have to agree.

SetiroN, unless you have other plans of switching phones or something let us know if you'd be willing to accept donations from us toward a new captivate. You may not realize how many people love your work. I remember when I woke up one day and saw this thread with your first kernel release and was amazed at how much better my captivate performed. All your work is greatly appreciated. Thank you for making our phones better then Samsung intended them to be :p

-Sent from my Captivate running Assonance v4.3
[Captivate Android Development] DAGr8:
need we say more setiron?

if your up for it i ll chip in to (who kows maybe now you just want another model ) , and ill even start a thread asking how much and whos willing to contribute
[Captivate Android Development] slider2828:
^^ Agreed.... What is the cost of a new captivate where you at?
[Captivate Android Development] junktzu:
Since he's in europe he'd probably have to buy it from somewhere in the US. Maybe someone could get one from craigs list or something.
[Captivate Android Development] Shammyh:
http://boston.craigslist.org/search/?areaID=4&subAreaID=&query=captivate&catAbb=sss

Up in Boston, almost mint Captivate's seem to go for about $300.
[Captivate Android Development] dambrosioj:
Why not just send it back to samsung for a refurb phone? You have a 1 year warranty right?

Thats what I did when my bootloader got borked they overnighted me a new one and I had to put my old one in the box, and the refurb looks brand freaking new :)
[Captivate Android Development] eSPyeL:
Setiron,

Will you be posting source?
[Captivate Android Development] FocuseD83:
atlanta.craigslist.org/sat/mob/2092129332. Html

Here is one from atlanta at 195

Love your kernels setiron
[Captivate Android Development] Da_G:
@SetiroN

If you do give up the ghost, please take the time to post your source tree, would greatly appreciate it. I have my own I put together after we talked in PM, but I wouldn't mind yours to diff it with :) Ideally on a versioning system starting from stock source and applying each patch as a revision. I'll throw in a meager donation for that (i'd do more if I had a job!)

If you are interested in attempting a JTAG repair I have a RIFF BOX sitting right here that I purchased for use with HTC HD2. I haven't had a need to use it with the Captivate yet so I haven't built a JIG for that. But I have some universal JIGs that might do the job. The pinout etc. is in the RIFF BOX software. I hope the pinout isn't as incredibly tiny as it is in the HD2 for your sake :P

[Edit: JTAG Pinout is all in one spot, quite convenient :) Not too small either, but not too big! Pinout
[Captivate Android Development] Mattwp103:
SetiroN, did you try holding volume up and power together and some red numbers will come on the screen. After they do hold both volume buttons and power then when the red numbers flash release power and that may get you into download mode. Not sure if you tried that one but goodluck and hope it helps.
[Captivate Android Development] FocuseD83:
@mattwp103

Had to do the same thing... was flashing with one click odin3 (at 3 in the morning in my bed, don't ask me why, lol) and hit my cable accidentally in mid flash. Screen turned red and had to do a battery pull shut it off. When I tried to cut on, no response at all! Quickly searched for a completely bricked solution in the captivate forum and found the remedy. I was able to see those red numbers you were talking about and was able to follow the instructions (involved taking the battery, then using a button combo while usb was plugged in with odin up and put the battery in while holding button combo) I was back in download mode and was stock by 3:30... Hopefully, setiron has a similar issue that can use the same remedy...
[Captivate Android Development] FocuseD83:
xdaforums.com/showthread.php?t=775911

Here's the thread... MAN, I hope this helps!
[Captivate Android Development] johan8:
I think this not help,

his is real brick, no phone-!-PC
[Captivate Android Development] johan8:
Hey man, you have a Jtag !:rolleyes:

That would be helpfull to help him repair the i897 !

Setiron, as a developer, don't give up that easy !

Brick a phone is just piece of Oreo, no big deal, not end of the day.

;)
[Captivate Android Development] FocuseD83:
@johan8

My phone was totally non-responsive except for when I held power and the volume up button for a while, then a 2 rows of red digits showed up... I followed the instructions on the link I provided and was able to get in download mode... I was just hoping that he had the same situation I had... If you see the red digits after the button press then you can get into download mode... I'm probably just insulting the dudes intelligence by offering this method though (he knows more about kernels and scripts then I ever will), but maybe there is a small chance it could help...
[Captivate Android Development] FocuseD83:
Also had no phone to ! Screen... blank screen, unless I held down power and volume. Then the red digit showed up
[Captivate Android Development] whitesox311:
****, i work for at&t....you're obviously well within warranty, doesnt matter that's the phone's modded

i can even get you one sent out if you trust/want me to.
[Captivate Android Development] johan8:
Sounds like most people here are willing to help each other,

so don't just give up.
[Captivate Android Development] Yuna:
SetiroN, just say something...

What are your plans? What have you tried?
[Captivate Android Development] SetiroN:
Hey guys,

thanks for your support, I had almost made peace with myself to go back to my old N82...

I knew about the RIFF box but didn't actaully consider it, the soldering is absolutely out of my capabilities... I've modded lots of PC hardware but 8 contacts less than 1/2mm apart are just too close by.

I've just noticed there is an adapter for the i9000 tho, which I'd say is compatible, it's not very common but a couple Polish stores seem to have it in stock.

The whole deal, cheapest RIFF box I've found from UK and shipping included, would be close to 200€...

The alternative would be shipping the phone to the only effectively international samsung repair center I could find (most only accept European phones) for a 20 working days ETA (which means 2 months, Christmas is right in the middle) and no certain price estimate ('probably over 50€' the operator said).

To be honest, I'm more inclined towards waiting for this summer to go back to the US and have it replaced then, for cost reasons.

Of course with a little help getting a RIFF box wouldn't seem as unaffordable as it does right now... but that's up to your generosity. :)
[Captivate Android Development] designgears:
Well, I like competition ;)

Get the shipping together for this guys, I have a cracked glass cappy I will send his way. (single crack across the screen) Should be easy to swap the boards, its like 6 screws :)
[Captivate Android Development] MikeyMike01:
Looks like you tried the jig...
[Captivate Android Development] designgears:
He did, the jig, no go.
[Captivate Android Development] MikeyMike01:
Well that sucks.
[Captivate Android Development] Cezar`:
Damn man... and we were so close to have the perfect kernel...