yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] aalh:
I did that before flashing Ultimate

I had frequent SD's as soon as I got this phone, but surgery kept me from doing another in-store exchange within 30days

And after flashing Phoenix months ago the SD stopped, till a couple weeks ago

since they went away before with a flash I figured it was most likely software/settings (helped by Samsung's design)
[Captivate Android Development] aalh:
I got Deep Sleep back by simply rebooting last night

Odd thing, the MIUI weather clock widget would FC when I tapped on it to open the weather, but after the reboot that recovered Deep Sleep it works fine

I never had trouble with that app b4

I waited till this morning to say anything so I could let it sit on the USB charging all night (had no SD or COD)
[Captivate Android Development] shane87:
Hmm, I think the no deep sleep issue may have been related to tye phone's real time clock being reset for whatever reason. Rebooting will reset the real time and processor awake timers, and that will fix the deep sleep read out. I am not positive though. As far as the miui alarm clock fc'ing, then that being cleared up by a reboot, I have had similar problems with my phone. Minor hiccups where an otherwise working app will start to fc for no apparent reason. I have had that happen on several occasions, and sometimes it will start working again on its own, other times I have to reboot. It doesn't happen often enough to really be a problem, but it does happen. Also, I sometimes have the issue of better keyboard messing up. It will stop showing the text I am typing in the input box. It puts the text where it should be, but it just doesn't show it. A reboot clears that issue up as well. I just thought it had something to do with me deving on my phone, but I guess it may be a kernel or rom issue. Either way, I am extremely happy with my current setup, and I can't wait to get gingerbread!!

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Android Development] fractaline:
Strange, I have that issue of not seeing the text in the input box until I touch it. But it is with any keyboard and only with andchat irc client.

I've uninstalled reinstalled and so on but keeps happening. I will try another app soon but more and more I am convinced that rather unique things happen to our phones that can't easily be identified.

I am also happy with my setup.....issues and all.

After all, if everything was perfect, we wouldn't have such a satisfying hobby. ;)

Sent from me to you.

Firefly + onix = :)
[Captivate Android Development] shane87:
Hmm, see, on my phone, after you click on the text box, the text that you type in shows up in the suggestionbox, but does not show up in the main text box above the keyboard. After exiting the keyboard, it will show the text in the textbox you were editing. It is very weird. I will have to get a screen shot of it next time it happens, but who knows when it will happen, sometimes it happens two or three days in a row, then I may go a week without seeing it. As several of us have said, our phones truly are individuals with their own personalities. I love my cappy, faults and all. And you are right, if they worked perfect, it wouldn't be as much fun to work on them.

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Android Development] rlorange:
@exitz

Hows the gingerbread kernel going? Seems like hard core and others are finding some weird quirks to contend with

**Simply Honey 3.0, UltimateGB beta7 kernel, JQ1 modem**
[Captivate Android Development] johan8:
I think you missed this

http://xdaforums.com/showthread.php?t=1050206

After Suckerpunch, seems that Onix is a history again;)
[Captivate Android Development] rlorange:
Thanks for pointing me to the new gb talon thread :)

**Simply Honey 3.0, UltimateGB beta7 kernel, JQ1 modem**
[Captivate Android Development] johan8:
existz seems paid all attention to new Talon,

no more froyo:(
[Captivate Android Development] 13_:
.... And you find this surprising? You have 59 ver of SP and 5 Onix to choose from. All of them reasonably stable. Time for new stuff. Let the man work. ;)

Sent from a Captivate on Bluedipity 6.4, Onix 2.0.5, JQ1 with Xda App
[Captivate Android Development] intellium:
BLN

I just switched from speedmod to onix.. the BLN isn't working! I checked in the console and BLN is enabled, but nothing is lighting up on missed calls. How do I fix it?
[Captivate Android Development] KayvinM:
You need to download the BLN app from the market. Here's the link https://market.android.com/details?id=neldar.bln.control.free&feature=search_result
[Captivate Android Development] intellium:
I downloaded the BLN app and still not working.. :-(
[Captivate Android Development] topiratiko:
I use blinky :) try that

Sent from Paragon Optimized
[Captivate Android Development] intellium:
BLN email notification works but missed calls don't... ahhh this bugs the hell out of me.
[Captivate Android Development] aalh:
I hope he is living GB right now, get Talon ready to go so when Team Pheonix puts their GB rom out the full package will be ready to fly

Have you seen the numbers people are posting from the GB roms

zzzzzzzippppyyyy!
[Captivate Android Development] 13_:
lol... ya .. I'm so anxious. I am waiting to switchto GB till the kernels are just about done or at least out of "dev". Sounds like all is going well though. :D
[Captivate Android Development] shane87:
Yeah, things seem to be great with talon! I have been running talon for a few days now, and I can say that, for a DEV version, they are incredibly stable. There are a few things that still need to be fixed, such as bln is resisting all attempts to fix it for gb, but neldar is working on that. And existz is trying to get a version with some more memory available, in the 340mb range I do believe, and I am sure there are many small bugs, but I am using talon as a daily driver and have had no problems at all.

ROM: Perception II beta 2

Kernel: TALONDEV 0.1.4, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Android Development] aalh:
very good to hear

I am still waiting on Mosaic to drop before I move to GB
[Captivate Android Development] shawnl01:
The search isn't working right now so I'm hoping someone can provide a fast answer. I'm not seeing any clockspeed higher then 1.12ghz and think I did something wrong. A different ROM from the past allowed up to 1.4ghz dynamically which is what I'm after here.

I'm running Firefly 3.0 with Onix 2.0.5 on it and using No Frills CPU to see the clock speed. It shows options up to 1.6 but nothing is setting it higher the 1.12. I also tried other CPU tools (set CPU, and another free one) with the same outcome. It won't go higher then the 1.12. I set it in performance mode so it won't downlock and it shows 100% of the time at the 1.12.

I'm assuming I did something wrong or there is some safety feature in place that I haven't found. Does anyone have an idea how to get it higher?

Thanks
[Captivate Android Development] existz:
Only use Voltage Control...you have to enable states, then set the max clock..most of the other apps dont allow this.. You pretty much have to "activate" the other steps so they are active, then set whatever you want for max clock
[Captivate Android Development] shawnl01:
That worked perfectly. Thank you
[Captivate Android Development] Xanaki:
Are there any plans to make Onix work with 2.3.3? I just flashed Mosaic I and am already missing Onix...
[Captivate Android Development] existz:
That's what Talon is..but we have to start at the bottom and work our way back up..plus things are different in gb/2.6.35 , for example we use ondemand/interactive governor, so there wont be a cpu threshold tweak..etc..for it..but some of the features in onix are or will be on talon
[Captivate Android Development] sepherian:
Nice kernal. Love the oc/uv, is this version final?

Sent from my captivate flying firefly!
[Captivate Android Development] singlag:
is it possible to add GPU oc just like Glitch Kernel in CM7 ??

http://xdaforums.com/showthread.php?t=1041532
[Captivate Android Development] Seanbest:
Still rocking this kernel. Any chance we'll see an update with the latest voodoo sound?
[Captivate Android Development] IDoMy0wnRacing:
+1...

I have two daughters and a friend that have Captivates running FroYo with Continuum 4.1. An updated kernel would be great.
[Captivate Android Development] ewingr:
Backup and Restore...

Been pretty quite here for a long time. Not sure I'll get a response.

I have ONix 2.05 running on my Captivate with Andromeda 3 for several months. I am not to the point I need to refresh, as I am having lockups for some reason.

I have tried doing a backup through recovery, and later a restore, 2-3 times and was never successful.

Given that it has been quite a whild since I have done any ROM installs, I am now rusty, and would like to insure that I can get back to at least where I am at right now.

Hoping to get verification of process for a restore. I'm doing a backup now, having booted into recover, and seleccted "Backup All".

I presume that if I were to just do a hard reset, it would be as if a fresh install of Andromeda 3 and Onix kernel; From there I could boot to recovery, and just select Restore All.

Is there something else I would need to know or do?
[Captivate Android Development] ap1618:
does this support init.d scripts?

thanks
[Captivate Android Development] shane87:
Yeah. Just mount /system as rw, drop the script in /etc/init.d folder, give it read/write/execute permissions, then mount /system as ro. It should then be ran at every boot. If it doesn't run at boot, check the "shebang" line: the very first line in the script should be "#!/system/bin/sh" (without quotes).
[Captivate Android Development] lrs421:
Now that you mention it I haven't seen any posts from him in a while. I hope all is well with him.
[Captivate Android Development] GGXtreme:
I'd love to try this, but is there any chance you'd release cold and warm color versions of this kernel? My Captivate's screen is perfect with a warm kernel (my last Captivate needed a cool kernel), but the default blue tint is just too much for me to deal with.
[Captivate Android Development] nickm50:
I'm not getting charge death. Mine is working perfectly.
[Captivate Android Development] lrs421:
I just peaked over in the nexus s forum and saw a 4000 quadrant score, damn!
[Captivate Android Development] LimaI896:
Wow that's insane
[Captivate Android Development] Auridran:
Yeah, I'm not sure where he's at but I remember him making a post about releasing a new version of his kernel either "Saturday or Sunday", referring to last Saturday or Sunday. He hasn't posted since then. I hope he's okay.
[Captivate Android Development] ls377:
He posted in the CM forums earlier today. I think he complained about being busy, not certain though.
[Captivate Android Development] existz:
Should have an update tomorrow... decided to go ahead and use the v300 oc patch, with this patch I will only have 2 versions now, 100hz and 500hz, so you can select what ever speed you want from Voltage Control, .. also updated the initramfs from Hardcores K12R, nothing really changed, just keeping it up to date...should release this version in the morning if all goes well..
[Captivate Android Development] DOAlaboratories:
Sweeeeeet :D
[Captivate Android Development] sjavvaji:
that is a heavenly combo...thank you...lets hope rasdeep's helps with the charge death
[Captivate Android Development] agaruba:
Two things: sometimes after the phone sleeps I have to do a battery pull to wake it again... no charge of death (or is it?). In running Darky 9.0.2 the #26 kernel build with uv settings just as it says in 3rd post.modem is kp1. Phone is sgh i896. Any possible reasons? My UV settings have always been cfq by the way.

Second thing ... after applying the UV settings on boot, should the system be left as rw or can it be put as ro?

Should i reduce the uv settings? do u think this will solve sleep problem?
[Captivate Android Development] LimaI896:
How much did you uv? Sleep death could be caused from uv too much therefore freezing when asleep.
[Captivate Android Development] agaruba:
uv settings are: cfq scheduler (highly recommended so used this and was never on noop) and 50/50/75/75/100/125. Are these uv settings too low? perhaps i should have gone more conservative? what do you think?

Also, can you tell me what exactly does the additional cpu power grant over speedmods latest kernel because i installed this suckerpunch #26 build and honestly quadrant and linpack scores are similar (and i know these are just approximate tests) but i just want to know whether its only the clock speed that is the difference between this suckerpunch kernel and speedmods because battery life is definitely the same no matter which modem or kernel i flash.
[Captivate Android Development] RonH54:
I had been using SpeedMod so since this is based on it I thought I'd give it a try and I Loving it. I am wondering every time that SpeedMod is updated will you do an update to your Kernel implementing his changes to yours?

Thanks again
[Captivate Android Development] ryude:
I will answer your question, but next time please use the "search thread" function.

Existz said he will update as long as it is something he agrees with, it's existz kernel; not speedmod with oc/uv.
[Captivate Android Development] RonH54:
Thanks......
[Captivate Android Development] existz:
**UPDATE**

Build #30 (01/30/11)

Updated initramfs to Hardcores K12R

Updated to v300 OC Patch | Up to 1400mhz OC [Default 1000mhz]

-Available frequencies - 1400/1360/1280/1200/1120/1000/800/400/200/100

-To overclock enable desired "States" and Max Clock via Voltage Control App (use latest)

Dont go crazy trying to overclock, in reality MOST phones have a hard time getting above 1280, or even getting to 1280, so if your having problems, lower your clock, also since all phones act different and handle oc different, i will NOT be providing support on overclocking, but maybe someone will be nice enough to help you in this thread, 99% of the time if you have a problem, try lowering you speeds (of course if your not OC'ing then thats different, so post it) but I just dont want alot of threads about "My phone keeps rebooting at 1400mhz, it didnt do this with Speedmod.. this kernel sucks," .. so OC at YOUR OWN RISK!

Later on I might swap out the 1400/1360 frequencies for 900/600 , something we all could benefit from, since most phones cant handle that high of a clock anyways..
[Captivate Android Development] lrs421:
Installing as I write this...1200 here I come.
[Captivate Android Development] agaruba:
Is the wifi connectivity issue fixed?
[Captivate Android Development] existz:
Im still trying to narrow it down, if you still have the problem in this build use the same quick fix, enable/disable IPv6 Privacy via CWM.. Im trying to figure out exactly what is causing it, if people still have the problem in this build, ill disable IPv6 privacy all together and release another build. I know I said I was going to do it in this build, but ive been super busy and forgot..sorry guys.
[Captivate Android Development] Dlev7:
Hey Existz I love the kernel right now I was at the 1.12 GHz one, but I experienced a charge death where it charged to 100 then the phone turned off, so Im back on Speedmod for now because of the fact that I needed my alarm in the morning : D.

But my question is if I were to download the update what are the settings I should use if I only want my max OC to be at 1.2 Ghz? I am currently on 1.12 with -50, -50,-75,-75,-100,-125. With a Noop Scheduler.

And Does this fix the charge death yet?

Regardless though the best kernel ive ever used just need help with the charge death and understanding more of the OC UV settings.

Thanks in advance to anyone that helps
[Captivate Android Development] existz:
I cant give ya a set UV, since all phones are different you will have to trial and error it.. just set 1 frequency 25mV at a time, stress testing it each time you lower it, then try another 25mV, and so on, then moving on to the next frequency..

As of right now, im still getting reports of charge death, ive done about all that I can trying to fix, since it doesnt happen to me its making it 100x harder for me to test different things.. Its looking like we might have to wait till Glitterballs msg me back for a fix...unless i really really luck out on a test build...its getting there though
[Captivate Android Development] Dlev7:
Alright Ill be patient and until you find the fix Im going to have to use Speedmod because of my alarm on my phone (sorry I LOVE this kernel its just I cant have my phone die on the charger ever night)

But Is this what your saying: -25,-25,-50,-50,-75,-75,-100,-125? For OC to 1.28 GHZ? And then how can I test if that works just apply on boot and reboot the phone?
[Captivate Android Development] Milkshakes00:
I haven't had a problem with charge death on your kernel, ever, but then again, I've never had the issue.

One thing you might want to look at is why Serendipity 5.0 seems to consistently lock up with your kernel; the older Serendipity 4.3 didn't lock up, ever, with your #27 Version, 500Hz or 100Hz. 5.0 locks up every 3-5 minutes with your #27 version, and I just noticed you uploaded the #30 version, so, I'll give that a try.

I know that Serendipity really isn't your problem, but I figured it would be easier for MikeyMike to come up with a solution if you're both looking at the problem. :)
[Captivate Android Development] sf1120:
What wi-fi connectivity issues are you guys refering to?I don't seem to have any problem with wi-fi:confused:

Btw,update on the sleep death,I bumped up the voltage a notch and woke up this morning with the phone still on.YAY... :-) -50,-50,-50,-75,-100,-100 cfq (1120-100)
[Captivate Android Development] existz:
The only wifi issue I've noticed is that if you had wifi enabled and rebooted, wifi wouldnt automatically connect back, but if you either disabled IPv6 privacy or if it was already disabled, enable it then reboot then back to recovery and disable. So far that's the only wifi issue I could duplicate
[Captivate Android Development] sjavvaji:
yea...its kinda a non-issue...i believe it might have something to do with the modem you are using at the time...anyway...im at 1.4ghz with 70+ stability tests passed uv settings are highest to lowest including 1.4ghz, 1.2ghz, and stock frequencies: 50, 75, 125, 125, 125, 100, 100
[Captivate Android Development] mkr14:
No problem with 5.0 for me. Running great. Had consistent charge death with the #27 kernel though. #30 seems to be ok so far, even at 1400.
[Captivate Android Development] sjavvaji:
yea...i never had charge death on Setiron's which also used the same overclock code...im pretty sure this should reduce it drastically. I got it regularly on #27 too
[Captivate Android Development] c0ldburn3r:
As posted in the OP if you are having troubles with Charging Death set your wifi policy to "never" or "Never when plugged in" and leave your wifi on. I stumbled across this last night, you can use spareparts to set the policy. So far with raspdeeps v300 patch this kernel is very clean and very stable.
[Captivate Android Development] sjavvaji:
i would recommend not using spare parts for this function. go to ur wifi menu and click menu. and set if from advanced settings
[Captivate Android Development] nosenuggets45:
Does the 500mhz vs 100mhz kernel make a big difference in Quadrant scores? With build #29 1.28ghz 500mhz, I was getting around 1800 as a score. Now with #30 1.4ghz 100mhz, I'm only getting 1300.
[Captivate Android Development] c0ldburn3r:
Curious to why not?
[Captivate Android Development] existz:
are you sure that all the states are enabled via Voltage Control app? Cause it sounds like its not set, its still on default, If you just set max clock to 1400 its not going to work, you have to also set the "states", it allows what frequencies are available, by default its stock frequencies... DO NOT use SetCPU, it will cause more harm than good.., you have to use voltage control app, it will control everything you need, (voltages, which frequencies are enabled and set max clock) latest version is in the OP

With setting the "states" it sets which frequencies are available, then setting max clock sets whatever you want as the max, so if you just have up to 1000 set in states, setting 1400 as max will not do anything and revert back to 1000 since the 1400 frequency is not active
[Captivate Android Development] sjavvaji:
by clicking the android default option...it basically doesn't set anything leading to so sorta waste in battery...it not sure y...but i remember reading this somewhere...i guess it doesn't matter it you are just setting never
[Captivate Android Development] nosenuggets45:
I feel dumb now... Sorry about that. I just uninstalled SetCPU and set the states in Voltage control app. I didn't even realize that app did it all! Everything is working now. Also made a typo in the last posts. My quadrant scores used to be 1380, not 1800. Just ran quadrant at 1.4ghz and got 1392. Seems to be all working again, thanks!

EDIT: Scratch that. I just went to chose some different States and 1400mhz was my max. When I clicked apply I got the Kernel Panic Upload Mode screen. Guessing 1.4ghz isn't stable? And of course I ticked apply at boot.... I really haven't learned my lesson yet...
[Captivate Android Development] c0ldburn3r:
Yeah, it sets it correctly when you say never. It's just a workaround until Glitterballs gets back to eXistZ. Plus not everyone is having Chraging Death issues. Mainly me lol :D
[Captivate Android Development] existz:
Theres a very very good chance your phone cannot handle 1400mhz, most phones cant, a few can, from what ive read, alot of UV tweaking has to go into it to get it half way stable, even then its not 100% that it will even work...some phones cant handle anything above 1200

Its best to start from 1120 or 1200 and only setting your UV 25mV at a time, testing each time you change it, if it passes, add another 25, keep on till it crashes then go back to last working setting, then set UV for the next frequency,..so on and so on, then move up to 1280 and do the same thing all over again, the same UV might not work, stress test it for a good amount of time also use it daily to make sure nothing crashes, then move on to the next step, .and so on and so on,
[Captivate Android Development] abee_13:
So i tried flashing build #30 and am now stuck in a bootloop and cant access download mode or recovery :eek: bad flash?
[Captivate Android Development] c0ldburn3r:
Sounds like it. :(

Buy a JIG
[Captivate Android Development] AJerman:
Looking good so far. I came from GB's kernel to this because I wanted the updated Voodoo Sound driver. Ran 1400 without UV (on the 1400 step) pretty well for a while, but it seems to crash randomly, like a second ago when I opened my gallery, but not when running Linpack about 10 times in a row. Oh well, dropped it down to 1360 and seeing if it likes that a little more. Got a 19.392 on Linpack. :)
[Captivate Android Development] shaolin95:
May I humbly recommend using the mini guide in my sig to fully test your stability.

I am about to give this kernel a shot.
[Captivate Android Development] sjavvaji:
thnx...helped me perfect my 1.4ghz oc...now i cannot get it to freeze no matter how much i spaz out on the phone
[Captivate Android Development] cumanzor:
I was able to get 1400 with -50. It seems to be stable, played Jet Car Stunt for a while, didn't crash, didn't get too hot either.

Do you guys notice any noticeable difference between 1100 and 1400MHz?

Can a kernel flash mess up recovery or download mode?

I had the same problem with GB's Steam kernel. But I'm still not sure as to what left me without recovery/download mode. Right now your best bet is to use a USB jig. You can make one yourself with 3 100k Ohm resistors, look for the link in the General forum.

This is why I check if recovery or download mode are still accessible almost daily lol.
[Captivate Android Development] existz:
Added it to the OP if thats ok