yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] johan8:
After unplugged power for 1day of normal use, battery level is 40% now, so far so good.

I have to disable 900Mhz and 600Mhz, otherwise I will get random FC on some apps and system service.

If FC is occured on system service, phone will reboot.

And UV can't lower than -100mV otherwise COD will occur.
[Captivate Android Development] diablo009:
Well, 600 and 900 are not standard frequency steps in Captivate (based on the steps provided by setCPU when I was on stock). So maybe that's why urs is FCing on those.

But I think this is again hardware dependent. Mine is showing considerable activity on 600 (00:28:58) and 900 (00:15:00) too, and has been pretty stable so far.
[Captivate Android Development] johan8:
Yes, it might be hardware dependent.

And theoretically the cpu can run at any clock speed, such as 610 620 630 ... But mine has problem if 900 is enabled.
[Captivate Android Development] diablo009:
Oddly, I noticed today that mine's freezing with 600 n 900 enabled. Froze twice in 3-4 days. Will disable those states n see how it goes.
[Captivate Android Development] disellusional:
how do you disable states?
[Captivate Android Development] harpo1:
Voltage Control from the market.
[Captivate Android Development] PearsonDKA:
About my earlier posts about the battery life being pretty bad, i got it fixed by doing a battery bump and everything seems good at a 1.2Ghz setting.

Anyone know a decent/stable voltage control setting for a 1.3 or even an 1.4Ghz overclock? Also, outta curiousity in regards to long term use with an overclocked cappy, do I have anything to worry about?

Sent from the I896 Cappy.
[Captivate Android Development] cnigro1279:
Just out of cvriosity, what ap are you using to see how long your cpu is staying at certain frequencies?

Sent from my couch on my phone.
[Captivate Android Development] sixstringsg:
CPU spy. Its in the market.

Sent from my CM7 powered captivate
[Captivate Android Development] Johnny Paranoid:
Different phones can handle different UV settings on different OC states. What is stable for one phone isn't necessarily stable for another. The chips react differently depending on a lot of things such as where on the board it was cut from (edge vs. middle), age and usage. I recommend you read shaolin95's Mini Overclocking Guide and test it out for yourself. Just remember not to save any settings in Voltage Control as a boot setting unless you're reasonably sure that it's stable. That way if you lock up you can reboot and everything will back the way it was. Also note that your phone may just not like being overclocked past 1.2Ghz. Mine tends to freak out a bit at 1.4Ghz no matter what I set the UV at (even stock). Supposedly, our chips are designed to be able to handle OC up to 1.6Ghz but that doesn't mean it's necessarily a good idea to do it. As with any modification of your phone, you take your fate into your own hands.
[Captivate Android Development] PearsonDKA:
Noted. If that's the case, prob just stick with 1.2 for awhile and see how that goes. Thanks again for the info.

Sent from the I896 Cappy.
[Captivate Android Development] fractaline:
I had a go at under clocking, set 900 as max clock (and in selected states) after 12 hours of moderate use I had no problems (aside from lag) but cpu spy showed only 1% on 900.

I have read that each cpu is unique.......

Now oc'd to 1200 no 900 uv'd 75, 75, and 100 on down...

Once you've tasted onix, it's hard to think of switching.

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] johan8:
Did you read existz #1 post ?

Voltage Control app has already there in the first day he post Onix.

:)
[Captivate Android Development] sinichi21:
The onix 2.0.4 build #1 is smooth dont know about what changes it has I just saw it and download it the bootanination time take long now even the tweak are on and seems that the widgets on the homescreen load a little slow than before I dont know if the tweaks are bug or its just like that but when everything is finish loading everything is so smooth big difference from the 2.0.3
[Captivate Android Development] existz:
Alright...I've noticed this so far, if I do a full discharge (down to 1% or till it shuts off) then plug in to charge overnight...i end up with a charge death...it doesn't seem to happen at any certain point, I caught it a couple times and when I powered back on it was at 20% one time and 68% the 2nd time... Then I noticed if I plug in to charge at around 15-20%, I don't get a charge death...let me know if you guys have similar results or if it happens at any % ...
[Captivate Android Development] shoman94:
Actually funny you mention that. The day I had mine I did kill it dead.
[Captivate Android Development] existz:
Hehe..so you noticed :P ... I should have official 2.0.4 up today, im still checking a few things before I post it here....that was basically a build I done for DAGr8, the official will be pretty much the same, just triple checking a few things before making it official ..I think its the smoothest yet
[Captivate Android Development] harpo1:
Oh so you can't get it from the market?
[Captivate Android Development] tehsam:
were you able to get this fixed in the build that will be going out today?
[Captivate Android Development] existz:
I cant say for 100%, i done a few things i "thought" would fix it, but it would take me another few days to verify it... even when I try to drain my phone it takes a full day, so to verify that i would need to drain then charge it full a few times and see what the results were.. but this way I can go ahead and get what i done with 2.0.4 out and see what you guys say, and I can be working on 2.0.5 in the mean time...it will give me time to really track it down and try to fix it..it took me 4-5 days just to figure that out
[Captivate Android Development] aalh:
I had a CD when I was bump charging yesterday, so it happened at the other end of the scale than yours, but it happened

the only non stock clocks I have enabled are 1200 & 1300

no UV

I was using JQ1 at the time, if that matters
[Captivate Android Development] DarkisFever:
Got my first charge death. Firefly 2.7 no oc/uv just happened randomly. Was on onix 2.0.1. Samsung captivate

Sent from my Samsung SGH-I896
[Captivate Android Development] existz:
*UPDATE*

Onix v2.0.4

-O3 compiler optimizations except sound soc codecs

-optimized CFLAGS inspired by laststufo

-set read_ahead to 2048kb (sdcard fix)

-few sched and mm fixes/tweaks

-optimize cache flush

-changed 100hz version-set CONFIG_HZ to 128; USER_HZ to 150

-removed useless patch to lowmemkill

-remove DEVMEM/DEVKMEM and set MMAP_MIN_ADDR=32768 (security)

-removed some kernel debug info

-disabled 900mhz by default

NOTE

I cant say for certain if the charge death issue is gone, but im still working on it..its been narrowed down some
[Captivate Android Development] reflex01:
awesome! 2.0.3 was incredible, excited for this release!!!
[Captivate Android Development] betadan:
Flashing now, Thank you!
[Captivate Android Development] Delicate Donut:
Quick question do I have to erase my voltage settings before flashing to the new one?
[Captivate Android Development] existz:
Ill add more security changes in 2.0.5, most of my time was consumed with hunting down the charge death issue...atleast I "think" I have it narrowed down some..but ill add more security features in next release...

This build should be the smoothest, its very very quick for me... You may notice I changed the 100hz version, its now kernel hz=128 and user hz=150..it helped with responsiveness but also does not hurt battery life, I tested this over 4-5 days and it was exactly the same for me..so if you have a batt drain, give it a few charge cycles before judging
[Captivate Android Development] TigerEnigma:
Give another go

Existz,

I love the kernel...had some wife error issues with the 2.0.3 version (just a note, I am aware of the other posts on it) no charging death issues. Brilliant work sir!

~Enigma
[Captivate Android Development] existz:
If your on 2.0.1-2.0.3 then no, if your coming from any version of Suckerpunch, or anyother OC/UV kernel then yes..but not from Onix version to version..unless I post otherwise, but ill usually make it do it automatically if I need it to
[Captivate Android Development] Delicate Donut:
Awesome you are the best man
[Captivate Android Development] goodolsen:
Does the wife know about these error issues? :)
[Captivate Android Development] Keland44:
flashed it !!!!!
[Captivate Android Development] jon.groves:
I just flashed 2.0.4. I do notice a difference in responsiveness. Los great. Thanks fire the update and the hard work.

Sent from Captivate with Serendipity 6.3 and Onix 2.0.4 and kc1
[Captivate Android Development] DAGr8:
I sure hope not :eek:
[Captivate Android Development] Johnny Paranoid:
Just flashed v2.0.4 and so far it does seem smoother and snappier. Battery is draining just a bit faster than usual, but I know to give it a couple cycles before judging that. Overall, I have to say that what was already great is now even better! Thanks!
[Captivate Android Development] existz:
Yea might have to give it a few charges, mine drained really fast at first, but got better... if it does end up having to much battery drain, it might be from the optimized cflags and using O3, which I can revert back to the normal ones I used...but its up to you all if the smoothness is worth it or not ..but after recalibrating there might be a tad more battery use but not much at all
[Captivate Android Development] AReynante:
Just flashed, feels great so far
[Captivate Android Development] RonH54:
How are the different Scheduler settings of "SIO","Noop", etc different and which is the most commonly used?

Thanks
[Captivate Android Development] Johnny Paranoid:
http://en.wikipedia.org/wiki/Noop_scheduler

http://en.wikipedia.org/wiki/Deadline_scheduler

SIO (or Simple I/O) is based on Deadline but is more a mix of Noop and Deadline. This kernel is set to use SIO by default and it is recommended that you use that.
[Captivate Android Development] disellusional:
any insight into those wifi errors?
[Captivate Android Development] 13_:
I let my phone chill for a few days. w0ot, new Onix. So far so good. After chilling on something else for a bit, the smoothness and quickness of this kernel is very obvious. Great work.

Sent from a Captivate on Bluedipity 6.3, Onix 2.0.4, JQ1 with Xda App
[Captivate Android Development] Sqb:
Great work! As usual. thank you for the countless hours of work. It shows

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] H3llstorm:
And just in time (to ruin everyone's good time)...

http://xdaforums.com/showpost.php?p=12675856&postcount=389

:rolleyes:
[Captivate Android Development] LNJ:
lol at least the new version feels smoother. I'm not using an external SD card so I'm good.
[Captivate Android Development] existz:
I think using O3 compiler optimization and laststufo's optimized CFLAGS is what made the biggest difference, I can tell a difference when using them compared to using O2 and CFLAGS from Speedmod.. everything is alot more responsive IMO
[Captivate Android Development] reflex01:
Will removing the /etc/init.d/s77sdcardspeedfix file be enough to disable this, or is it built into the kernel?
[Captivate Android Development] existz:
Its built into the kernel, either way its fine to leave it, isnt going to hurt anything
[Captivate Android Development] BaDaB!ng505:
Great work...only have one issue when using tv output..i notice the volume is very low..
[Captivate Android Development] sinichi21:
Hehehe was just cllicking a few and the file the official seems much better now really glad to see you stick with your simple boot logo =). But the bootanimation time frame is still longer than before is that normal? When I was using the 2.0.3 it wont finish my bootanimation now it finish it but the widget loading is faster now than before build #1
[Captivate Android Development] existz:
Im not sure to be honest, you could try clearing cache and dalvik cache, of course the first boot will be longer, but then after that it might speed it up some...not sure if it will or not, but worth a try
[Captivate Android Development] joeshmoe08:
What wxactly does changing CONFIG_HZ to 128; USER_HZ to 150 do better than 100 both?

I thought the old setting gave better battery lfe so why was it changed? Thanks
[Captivate Android Development] H3llstorm:
From a few pages back...

:cool:
[Captivate Android Development] existz:
I've ran 128/150 for awhile now and battery life was basically the same, however, if there is a higher battery drain then its most likley due to using O3 and laststufos optimizes cflags...even with that my battery life has still been roughly the same over the last few days...but IMO it really does help with speed/quickness...I can tell a pretty good difference when using them and when not..but im still trying different settings for different things, so nothing is set in stone, things may change in the next release
[Captivate Android Development] H3llstorm:
More info from the SD Card fix thread (bold text added for emphasis)...
[Captivate Android Development] existz:
Oh well...was nice while it lasted..hopefully someone does end up finding a real fix for sdcard read/write

Ill put a build up tonite/tomarrow with this reverted as a "just incase" type deal... if you still want to use it you can use the script.. also might lower the voltages for 15/1600 steps, to try to increase stability, might be to much voltage..
[Captivate Android Development] 13_:
The above about the SD fix may be true. However, I do not care at all, my gallery opens easily 3 times as fast. So if this is placebo affect..... I want more lol.

Sent from a Captivate on Bluedipity 6.3, Onix 2.0.4, JQ1 with Xda App
[Captivate Android Development] Seanbest:
Gonna flash 2.0.4 now. Woot

Sent from my Captivate (Phoenix Unleashed JS8) using the XDA App
[Captivate Android Development] H3llstorm:
Like the man said...

I for one will be glad to have my 2MB of RAM back. :cool:
[Captivate Android Development] existz:
Its actually not from that, (if your talking about ram dropping from 340 to 338) I believe its actually from using the optimized compiler options...O3 to be exact (i think) .if you also notice, the kernel image went from around 5.7-5.8mb to 6.5mb~ish ...not really much i can do, except revert back to O2, but using O3 seems to be alot quicker/smoother
[Captivate Android Development] Seanbest:
2.0.4 running smooth so far. Hard to tell if its faster cause 2.0.3 was already so fast.

Sent from my Captivate (Phoenix Unleashed JS8) using the XDA App
[Captivate Android Development] existz:
Ill more than likely have 2.0.5 up tomorrow, gonna try a few more fixes for sleep death..also will try to add some more security fixes, mm tweaks, ..etc..etc.. so there might be alot of releases while I try to figure out the charge death issue... I might just set up nightly builds, I wrote a script awhile back to automatically compile at a certain time, then set it up to auto package it in a cwm zip, and I also have a script to auto upload to my server...just need to fine tune it some, so I might just do that, have it auto compile/package/upload at 12am or something, but iono yet...thoughts?
[Captivate Android Development] shoman94:
I don't have an actual external sd card.... but my internal/external sdcard has 7.8mb/s write and 15.4mb/s read Which is higher then 2.0.3, 2.0.2, speedmod, skullcap kernels) and gave me my highest score in Antutu System Benchmark by over 200points. Bone stock is is faster then Speedmod k13d-500hz

I say congrats on that. Love it.... now for the battery.
[Captivate Android Development] H3llstorm:
Actually, I was talking about the 2048k being dedicated to SD card cache. :cool:
[Captivate Android Development] VFO:
So far so good! No issues with shutdowns since 2.0.4 and now my phone is truly zippy. On another note I did see my 50% time without signal issue go away since flashing this new kernel. Thank you existz!

Sent from my Continuum powered Turbo Cappy
[Captivate Android Development] existz:
gotcha :P..my bad.. it was just a coincidence that 2mb of actual memory is gone lol.. O3 makes it at 338, O2 makes it 340mb... just wanted to point out that it was unreleated to the 2048kb from readahead
[Captivate Android Development] H3llstorm:
No problemo amigo. Dropping what appears to be an unnecessary 2MB SD card cache washes out the extra 2MB O3 seems to use. :D
[Captivate Android Development] TRusselo:
battery seems to be dieing faster now. flashed this morning with fully charged battery. already at 49% 8 hours later, and i was sleeping all day! not using the phone. on 2.0.3 i could sleep for 8 hours and it would only drop 9-10 % . today i slept for 6 hours and it dropped 40%!!! no OC/UV
[Captivate Android Development] existz:
Give it a few charge cycles, then see how it does...I only lose 1-3% over 8hrs idel

Ill try using O2 with laststufo based optimized CFLAGS and see how it goes, see if it helps with battery but still boost performance...then ill see about using O3 with speedmod CFLAGS...etc..etc..see if I can find a middle ground on battery/performance... right now im just playing with different options, hopefully find something that gives us best of both worlds

Which IMO I think using O3 is what's causing higher than normal battery drain...but it seems to be smoother, and its noticeable imo.. but using O2 with laststufo's cflags should balance it out some ...ill probably use O2+laststufo cflags in 2.0.5 pending test tonight..hopefully release it tomorrow
[Captivate Android Development] abee_13:
So can someone educate me about O2/O3 whats the difference ?

Sent from my cappy UC'd 900mhz and UV'd running di11is rom/ Onix kernel
[Captivate Android Development] existz:
http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html

You can look at the commit on my github where I switched to laststufos CFLAGS to see which ones I use (it describes all the flags in the link above)
[Captivate Android Development] bballer182:
Well I have never had sleep death on any of the suckerpunch or onix kernels. I must be one of the lucky peoples. Lol. Anyways I was pretty skeptical about the SD card "fix" from the get go. But I will say that it does speed the gallery up some. As for the battery, I pulled my phone off the charge this morning at 6am and have had the gps and wifi on all day and and used nav, xda, internet both on wifi and 3g. And it is 6pm here now and im only down to 78%... I love this kernel!

I think another contributing factor to my battery savings is the modem im using which is a fairly new discovery to the captivate. KC1 check it out guys its the ****!!! Its way better that JK4 and JVK. The link to the CWN flashable modem is in the first post of the MODEM sticky and the top of the page.

Sent from my OC'd Samsung Captivate
[Captivate Android Development] brd912:
Here's my results. flashed and rebooted=awesomeness

Quick and stable. No lag,no nothing whatsoever that is negative
[Captivate Android Development] TRusselo:
1-3 % over night WOW. you must have data and wifi off while you sleep, right? and undervolting?

for my 10% (i am used to) data off wifi ON, i just run stock settings (unless emulating). 100/1000 default voltages. no task killers. everything syncing/updating 30 mins (fbook xda email). though i am happy with it like this...

i remembered i cleared batt stats and delvik cache before i flashed this morning. thats probably why my batt seems off today... hopefully.

Love your work man!
[Captivate Android Development] noside12123:
I have idea if its the kernel causing this problem, or a recent app install etc. But my power menu is GONE. When I hold the power button I feel my phone vibrate but nothing else happens. No power menu . Help?!?!

sent from my phone using my fingers
[Captivate Android Development] existz:
No that's with data 3G=on.. sync=on...wifi=off, ...I keep HSPA disabled, only use UMTS, ever since just using 3G my idel discharge went way down (I noticed in logs that it was switching 3G--H every other minute, not just the icon, but actually switching 3g to H and vice versa, not sure why..I live literally 100yards from a tower and I have full service).. Also noticed it varies with different modems, jl2/3 gives me the highest drain, which then is usually 10%...and I get the same idel discharge with or without UV... I don't use any battery saver apps or anything that kills connection when screen is off..or anything like that .. I wiped completely clean awhile back, formatting both internal/external sdcards and redownloaded only what I needed, no backups..that help probably more than anything. I usually unplug around 9am and usually charge at around 11pm, and I still have around 40-50% left..that's with moderate use, not going to say heavy cause I don't play much games. Also I removed what system apps I don't use/need (don't do this unless you know what those apps actually do) that helped with running processes in the background and what apps ran on startup ..etc..etc..I've done alot to get it where its at..

But yea if you wiped battery stats that's probably why..just give it a few charges ... im hoping to get 2.0.5 up tomorrow and it should help with battery life (pending some test tomorrow)
[Captivate Android Development] shoman94:
Try not to change too much.... This is the best version since you moved into Onix.
[Captivate Android Development] bballer182:
I don't know if it means anything to you or not but i would prefer to have performance over battery... I mean we're talking like what? 1-3 percent per hour difference? Maybe if you still want to do the 02 compiler you could still do an 03 version with better performance for those that would like performance first then battery.
[Captivate Android Development] existz:
Ill do what I can to keep it as smooth as 2.0.4, but just trying to get battery life down some .. if moving back to O2 kills the extra performance but doesn't help battery much, ill leave it O3, just trying to find the middle ground of 2.0.3 and 2.0.4 .. and hopefully that's what 2.0.5 will be
[Captivate Android Development] harpo1:
Can you just go into settings and select GSM only and acheive the same thing as disabling HSPA?
[Captivate Android Development] aalh:
so any idea on the sleep deaths?

I am on 2.0.4 now and still get SD.

I have all setting stock and if I disable soft locker the phone will turn itself off in 10-20min
[Captivate Android Development] shoman94:
No cause that puts you into GSM and edge data. What he does disables HSDPA and HSUPA. So it's still 3g but UMTS. DL will be 384k and upload is 128k
[Captivate Android Development] existz:
No, easiest way is to use SGS Tools and under secret codes select switch 3G--HSPA and then disable it .. but just switching to GSM sets it to 2G/EDGE ... disabling HSPA disables HSUPA and HSDPA, leaving 3G/UMTS

Nope, still working on it
[Captivate Android Development] brd912:
My one and only question has been Linnaeus answered but,yes or no. Can the frequencies on the captivate be changed to the vibrants? Is is a software or hardware thing? Trying to see if there's a way around captivate not being able to use T-Mobile 3G
[Captivate Android Development] Twicebak3d:
Is there any way you could possibly work a 1344mhz state into the kernel? I usually UC and all, but there are times when I like to max out my cappy and put my bud in his place benchmark wise. I can't get 1400 stable at all.

Let it be known that I am a nub and I'm not entirely sure how much work this'd take. Just thought it would be a nice feature for my selfish acts.

Keep up the good work ;D
[Captivate Android Development] shoman94:
Well... I loaded the armani modem... I believe its JK9... anyways... I could see WCDMA 1700mhz as one of the choices in the *#2263# menu settings but thats about it... I didn't play with it at all. I don't know if anything else is required for it to work.... kernel or ROM.