yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] 13_:
Just to throw something out there....

I had various problems with 2.0.3 so after not getting the phone to cooperate, I let it chill the f out for a bit on a different kernel (paragon 1280) . While on it I did some nice full charge cycles -5% to full.

So, phone properly chilled, I come back to Onix. Did the normal cache/dalvik/batt/volt wipes. Phone is a 1007.

I can report no sleep/charge deaths. I can report OC and UV

to 1.2 stable as a rock. I can report my batt life is excellent, yesterday for example, uptime 75 hours, unplugged 31 hours, display time 3 hours 20 min., calls 1 hour 35 min, wifi always on. When plugged in I was still at 11%.

The difference for me between 13-20+ hour day is games. Games drastically reduce batt life. I also rarely open a full browser, mostly use the browser in rss reader or something like xda app. Heavy browser use for me has same affect as games.

Onix is smooth stable and fast for me, it wasn't, but it seems sometimes its your phone getting pissy, lol, mine did, we made up all is well. Just wanted to put it out there that its not always a problem with kernel or rom, sometimes its us and our phones with attitudes.

Thanks for all the work/dedication existz.

Sent from a Captivate on Bluedipity 6.3, Onix 2.0.4, JQ1 with Xda App
[Captivate Android Development] H3llstorm:
For the record, my Captivate is also a 1007 build.
[Captivate Android Development] rajendra82:
I was seeing some lag on 2.0.4, but instead of reverting back to 2.0.3, I decided to flash the nightly build. Seems to be working a lot better than 2.0.4, and on par with 2.0.3.
[Captivate Android Development] existz:
With that build I used O2 + laststufo CFLAGS, instead of using O3, so let me know what you think performance/battery wise..

Also remember guys..nightlys are unsupported, may cause bricks, and they are UNTESTED! it auto-compiles, zips and uploads at a certain time of night, so however my source tree is at the time, is what you get...so consider them early Alphas just to be safe..
[Captivate Android Development] rajendra82:
So far, the performance seems better with the nightly build than 2.0.4. I don't know about battery usage. I usually don't watch it all that close. Haven't seen any drastically dropping numbers.
[Captivate Android Development] existz:
Appreciate the feedback, im gonna test again tonite with some changes and see if I still have charge death..last night was the first night I didn't have one when draining it completely dead...so im moving in the right direction...hopefully
[Captivate Android Development] b0wz:
That would work :D Thanks for the job well done.....and staying on the boat!!
[Captivate Android Development] pimpnmaxima:
I hope CM7 will finish. Especially with the gingerbread update supposedly coming out.

http://www.engadget.com/2011/04/07/gingerbread-update-for-samsung-galaxy-s-to-start-rolling-out-in/
[Captivate Android Development] Johnny Paranoid:
There's still no planned official release of GB for the US or Canada though. We need those builds to mod.
[Captivate Android Development] LimaI896:
I been flashing back between them all, My psx4droid on FF7 crapped out on me for some reason so playing around with different kernels, no success. Really weird, I get 60fps on average but it lags, also crashes when I try to load my latest save. I played with the UV to see if it was too much n still not the case. Tried all 4 kernels.

For the people who say their phones done like the 1280 O/C

you most likely from my experiance with my phone is the need to UV. Its kinda tricky but this is how I managed to do it:

1: On a 1120 kernel set your UV for -50 on all of them.

2: Apply a voltage control app icon on your main desk top

3. (optional) Delete widgets and live backgrouds if you have so it gives you some extra time with less load time taken up.

4. Make sure you have a root explore or super manager(I have as its free ;))

5. Go in CWM and flash you 1280 rom.

6. You should be stable when you boot up but your problem here is you may notice you cant open the voltage control as it FC's. Sucks right well onto step 7.

7. Go in to your super manager and go to system/etc/init.d and delete your S_volt_scheduler (make sure your on r/w)

8. Reboot the phone

9. Once booted you have to try before you media card scan is complete to get into your voltage control and apply an uv for 1280, I'd recommend -50 for all as a start then you can play with your settings how you like it, this is just to make it stable so you can use your phone.

I just had to do this now since I been switching around kernels.

Once you do this if you always update to 1280 kernels you should be good. Unless existz obviously notes otherwise.

Hope this helps people out that want 1280. :cool:
[Captivate Android Development] LimaI896:
Wish I saw this before posting ahaha, that would make things much easier.
[Captivate Android Development] iXNyNe:
How about slimming that down even more and making 1120 1200 and 1280 all steps on the same single kernel? Defaulting to 1000 so that those who want to oc can and those who's phones can't oc won't have to worry about it. I donno why people are getting bajiggity about the brightfix (don't like it? Turn off auto bright!) But aside from that you should only be maintaining two kernels (500 and 100 Hz)

Anyway nice work. So far I like it. No issues with the kernel itself yet.
[Captivate Android Development] cumanzor:
I was using VC 3a, didn't know Xan released a new version. Gonna try it and play around with the UV settings (I switched back to "SAFER" mount options just in case).
[Captivate Android Development] sjavvaji:
yup...this is kinda what i had to do to go from 1.4ghz to 1.45ghz on Setiron's...it wouldn't boot until it was slightly underclocked...the devs increase the amount of available voltage as frequencies go up...for some of you people, 1280 may just have to high of a voltage rather than too low...my two cents and if your wondering...i gave that up for the amazing battery life of speedmod and now im here having the best of both worlds
[Captivate Android Development] mkr14:
This right here! Seconded

Also, I have been experiencing the charge death problem with #27 1280. I know this is already confirmed but I wanted to let you know.
[Captivate Android Development] LimaI896:
Exactly why I am on n following this build:D
[Captivate Android Development] iXNyNe:
I've tried A LOT of things to get 1280 running stable. Trust me I'm jealous (I'm a cell phone sales Rep and any time I see someone buy a captivate I wonder if theirs would handle it). Some phones hardware is legitimately different (only slightly) making it impossible for those of us to run 1280 or higher without freezing. Maybe OVERvolting might help but I'd rather keep my battery life and use a 1200 kernel that I can safely undervolt without instability. :) thanks for the tip though. Might work for some.
[Captivate Android Development] existz:
For those of you on IRC, join #suckerpunch
[Captivate Android Development] ccdoggy:
for what its worth those with battery problems should look into different modems. I know that the JK4 modem does great for where I am but when i go to my parent's place the battery lasts 1/2 - 3/4 as long.

I am all about battery life and am seeing pretty good life with this kernel, so thank you for focusing on battery life. glad to see someone is.
[Captivate Android Development] gibson3659:
I don't think GB overclocks his kernels by default, or at least not on the first boot. Can you do the same? I flashed the 1280 and had a little difficulty getting to Voltage Control before the phone froze.
[Captivate Android Development] iXNyNe:
freenode? or what server?
[Captivate Android Development] iNFRiNGE:
I know you said "later on' but this is just my opinion, first of all you can't please everyone although at times we would like to try. From what I have seen when developers on up to major corporations start to expand beyond what they should truly handle something inevitably suffers from this. It becomes a game of Quantity and no longer Quality, this usually is done for financial gain of course that's not the case here which is even more of a reason to limit the builds you put out, so you don't burn yourself out. And before another version comes out makes sure whats out is without a doubt 100% correct and at that point there should be no reason to update that kernel unless the update is going to improve it in some way.

It's your baby though I would just hate to see something with so much potential loose it because time limitations due to too many versions.

Let's this baby running right for everyone and in a year from now worry about those others and the versions they want lmao :p
[Captivate Android Development] WickedNite:
It's killing me inside, I'm sorry but I have to ask this. What does SmR means?
[Captivate Android Development] iNFRiNGE:
where does it say SmR at?
[Captivate Android Development] existz:
SmR stands for "Speedmod Remix" :p
[Captivate Android Development] LimaI896:
gb does oc his kernels on default to which ever version you download.
[Captivate Android Development] WickedNite:
Okay. I do have peace of mind now. :p
[Captivate Android Development] iNFRiNGE:
lol I just saw it in the title and my guess was going to be SpeedMod R3load3d.

I was close :p
[Captivate Android Development] iNFRiNGE:
Now anyway possible you can set us up with a click link to your irc?

Also for the record I'm using 1120/100 with the default 1300mV and no charge of death but I did not UV and my phone has been plugged into a pc while I'm running wifi and all kinds of stuff and my battery actually charged up to 100%
[Captivate Android Development] olo567:
Really? What in the software makes that a necessity? We already have GB modems for that aspect of localization, right?
[Captivate Android Development] IRONMAN-NC:
Any one else having a problem with the download links?

/tmp/AeG+t5O8.zip.part could not be saved, because the source file could not be read.

Try again later, or contact the server administrator.
[Captivate Android Development] existz:
Nope, just tested all the ones for 2.0.4..they work fine
[Captivate Android Development] existz:
Also, for those asking about the wifi error fix...notice it says "-

Attempt

to fix WiFi error message when turning WiFi on sometimes" ... so it may or not help.. I know Hardcore started working on fixing it, but we wont know anything until he releases K13E or whatever, to see if he continues to work on it..
[Captivate Android Development] bballer182:
I was getting that problem with JVK modem,which is a gingerbread modem. And ever since I've been on KC1 never once have I had a problem with wifi not wanting to start.

Sent from my OC'd Samsung Captivate
[Captivate Android Development] sixstringsg:
Not if you have the source. Especially since this very kernel is based on the i9000, not offered in the us or Canada.

Sent from my CM7 powered captivate
[Captivate Android Development] existz:
Correct... as long as we get the sources for GB for i9000, then we will be in business .. we will be doing the same thing we are doing now, using a reoriented i9000 kernel so auto rotation, sound..etc..work correctly ...then we will be able to just use an i9000 GB rom.. its hard to say if/when we get official captivate 2.3, we just now got 2.2 (officially)

On another note, this looks promising for upcoming Voodoo Sound :)...maybe ported audience chip? :P http://xdaforums.com/showpost.php?p=12727085&postcount=1875
[Captivate Android Development] Johnny Paranoid:
From what I know, the firmware that's built for European (or non-North American) networks won't work with ours since the 850 and 1900 band are pretty much exclusive to Canada and the US. If we have the source code for the kernel and ROM then it can be "re-oriented" to be compatible with ours. I get crap reception if I'm not on 850 myself since that's what most of the towers around me use.
[Captivate Android Development] Johnny Paranoid:
I've often wondered if we could get Audience Chip support since we have it. I know my phone does because it clearly says so on the box.
[Captivate Android Development] existz:
JVK is an i9000 Gingerbread modem...its has 850 enabled..and so does JVE. you could use a gingerbread i9000 rom/kernel/modem combo right now and it will work fine, but auto rotation/sound..etc.. will be off, the only thing we need is the kernel source to correct that, as mentioned above, then thats all we need

Its the same thing as me using an i9000 kernel, reoriented, and using the JQ1 modem, (its an i9000 modem and I have 850), and me using an i9000 rom , such as JS8..etc..it will be the same thing with Gingerbread, we just need kernel source
[Captivate Android Development] sinichi21:
seems the 2.0.5 build is more better than the 2.0.4 i download the nightly thing cant comment yet on battery yet, and notice the build on settings is still 2.0.4 but when i flash it says on the recover 2.0.5 but anyways so far no charge of death left the phone charging still until now, the bootanimation time frame is quicker now again to me, it looks a little more smoother on loading the widgets now unlike before that everything get laggy until everyhting loads up now seem to do it more smooth.
[Captivate Android Development] existz:
Yea I havent got around to changing the kernel build number for the nightlys, I usually change it right before I compile and release, thanks for noticing it, ill change it so tonites shows correctly

Also my github doesn't show I switched back to O2, ill fix it so it shows also, for those that keep up with the changes
[Captivate Android Development] donegan6339:
Minor problem

Here is one for someone with more expertise than I........I flashed onix coming from a gb oc/uv kernel. Everything is working great except my network indicator no longer shows up. No edge/3G/HSDPA indication whatsoever. I still have bars, and can place and receive call and can use data. Any ideas?

Update: flashed back to previous kernel and same thing occurred.
[Captivate Android Development] Srikar_NBK:
Not sure if its only me, but I still experience random deaths (not charging deaths) on this kernel, specially when the phone is locked. :(
[Captivate Android Development] existz:
I hope im not jinxing anything, but with the last 2 nightlys, last nights and the one that will be up tonite, I've done 2 full drains and no charge death yet ..before I would get them anytime I done a full drain and charged... the only thing I can think of that I done that would effect this is changing the memory config back to how it was pre-Onix (SP59 below) ...changing PMEM_ADSP=1500 and MEMSIZE_BCM=256 ...Hardcore had changed it in K13D (Onix 2.0.1-2.0.4) to 1536/512, .. I've yet to update my github to reflect the change, ill update it if I can verify 100% that it helps/fixes it ...

So if your having charge death, give the nightlys a try... (remember, there's no support for nightly builds, its setup to auto compile, package zip and upload from my source tree the way it is at a certain time, so proceed with caution, make sure you know how to recover from a bad flash and you have a backup incase something goes wrong, these are NOT tested before uploading...however I usually compile and run my latest changes...but something could still go wrong during nightly compiling/uploading! So treat them as if they were early alpha builds!!)

http://berryfx.com/RobBeane/Kernel/Nightly/
[Captivate Android Development] geokilla:
If that change did cause the charge death, the SpeedMod thread would be flooded with complaints on charge death wouldn't it? Maybe it's the PMEM_ADSP=1500 and MEMSIZE_BCM=256 and undervolting combined that's causing the charge death?

I dunno, I'm not an expert with developing.
[Captivate Android Development] existz:
No, the same rules don't apply to every kernel...even oc/uv kernels.. with a non-oc kernel (speedmod) the way the voltages/frequencies..etc work is different than oc/uv kernels, since the oc/uv code alters this (main reason Hardcore doesn't do an oc/uv kernel)... Also, it can be different with oc/uv kernels...there's different variations of the oc/uv code out there now..(raspdeeps, laststufos modified, trasigs modified code..etc) ...so something could effect one kernel, but not another ... With early versions of SuckerPunch, it was found that setting swappiness to anything less than 50-60, would cause sleep/charge death .. which was one of the tweaks in Speedmod (swappiness=0), so ever since then I've removed that tweak.. so if something causes problems with one kernel, it doesn't mean it will cause problems for another...and especially with oc/uv kernels, the littlest thing can cause problems ... comparing non-oc kernels to oc kernels is like comparing apples and oranges..
[Captivate Android Development] donegan6339:
I was wrong about my data. I had wi-fi on(duh). So no data and no network indicators. I dont know why flashing this kernel would effect this......
[Captivate Android Development] existz:
If it does it on another kernel, then its not the kernels fault... reflash your modem ...and make sure its not just from a network issue with your carrier ..what rom/modem are you using?

You said you went to Onix from a GB kernel, so if your using gingerbread, this is a froyo kernel...
[Captivate Android Development] sinichi21:
just want to ask so every night the name of your file will also change by the date right or it will just be the same name?
[Captivate Android Development] existz:
Its setup to check the date, then name the file accordingly...so it will change every night , so tonights will be Onix-2011-04-08...and so on..
[Captivate Android Development] Johnny Paranoid:
Do you think we will see an official 2.0.5 some time tomorrow then?
[Captivate Android Development] existz:
Hopefully, that's what im planning on... im draining my battery again and going to do a full charge, so far I haven't had a charge death the last 2 times...so if it doesn't happen again tonite, ill put up what I got tomorrow...plus ill see what people report on the nightlys..so far no charge death...(fingers crossed)
[Captivate Android Development] disellusional:
i think that was his target..not sure though.

he said somewhere today or tomrrow
[Captivate Android Development] meadhros:
Dissassembled this battery. It appears to be a couple of 1350 cells glued together. Watch these carefully. There is no true shell or cover. The label is the protective barrier on these. No serial in our outside.
[Captivate Android Development] existz:
Nightly went up alittle earlier tonite, had to reboot my comp, so it ended my script, so tomorrows should be up around 1:11-1:15am ...but tonights is already up...so far im 3/3 with full discharge/full charge and no charge death.. look for 2.0.5 sometime tomorrow mid-day
[Captivate Android Development] LNJ:
Been running it for the past 15 mins. So far so good!
[Captivate Android Development] bamonkey:
nightly seems to be running well. 1.3ghz is running more stable overall, camera app *could freeze* but that is nothing new on my phone at this OC so i tend to disable when i really need the camera. disabled a few cpu steps and it seems smooth. will stress the Undervolt and do some charging tests but so far rock solid.
[Captivate Android Development] donegan6339:
Sorry man I wasn't very clear. I came from glitterball's oc/uv kernel. Thank you for your suggestion, it was pretty close to dead on. I did all of the above and it turns out that data packets randomly turned of in network settings. I should have started with the simple stuff. Thanks again, I really appreciate your time.
[Captivate Android Development] aalh:
I agree

but I would not mind getting a day out of it

24-30hrs

my phone has done 40hrs+ before so I know it can

over the passed couple days the life was around 12hrs to start with, this morning, it was at 30% after almost 14hrs

I had to plug it in to xfer a few gigs of music so I wasnt able to continue.
[Captivate Android Development] b0uncyfr0:
Hi guys i just sarted using onix and its awesome. Very fast and stable. Only problem im having is with gradients. Apparently this is on the speedmod kernel as well. Has anyone found any ways to fix it?
[Captivate Android Development] topiratiko:
Cant wait for 2.0.5!!! It will retain sd fix correct?

Sent from Paragon Optimized
[Captivate Android Development] ctleng76:
So far this kernel is the best for utilization of the car dock audio output. Thanks for the hard work on this!

Is there a way to change the EQ settings for the car dock audio output? The car dock audio is better than it has ever been, but it is still missing something in the low end frequencies. To make it sound decent I am having to boost the bass and reduce the treble on my car stereo. Even then it is still a little off. I can help this further with the music player's EQ, but with other applications I don't have additional control over this.

Just to compare, if I connect the phone's audio output jack directly to the stereo (without the car dock) the sound is as it should be.

Thanks
[Captivate Android Development] existz:
Ive removed it for now, in the mean time use the script for /etc/init.d/
[Captivate Android Development] Twicebak3d:
I was getting CDs as well on 2.0.4 with Phoenix Unleashed. I flashed Serendipity + 2.0.4 the night before last, mainly for GPS reasons, and the past two nights have been fine. No CD or 1300 freezing. Instead of removing the SD fix, could you make it a tweak in CWM?

Lol I need to learn to do things for myself >.>
[Captivate Android Development] topiratiko:
That would be cool.

Sent from Paragon Optimized
[Captivate Android Development] rajendra82:
Running the April 8 nightly for a few hours, and no issues so far. Battery usage with my typical usage seems to be running at 10% over about 2.5 hours with 45 minutes screen time.
[Captivate Android Development] existz:
Added :P ...but i might not set it as aggressive as I did before (2048), as to high of a value will waste memory and bandwidth... im thinking something like 512 or 1024.. maybe later on i will add an option to select different values, but for right now there will only be one option..
[Captivate Android Development] Twicebak3d:
Sick. I'm so glad you're open to suggestions lol. My dev hero :P
[Captivate Android Development] topiratiko:
Lol ya thats awesome

Sent from Paragon Optimized
[Captivate Android Development] LNJ:
Unplugged phone at 10:30am @ 100%, 3 calls totalling 1 hour, a little web surfing and emails and @ 77% now at 1:24pm

Sent from my GT-I9000
[Captivate Android Development] H3llstorm:
If you're going to implement this at all, make sure you're testing with the new (fixed) version of SD Tools - http://xdaforums.com/showpost.php?p=12708647&postcount=485
[Captivate Android Development] existz:
Yea I am, plus im testing by copying a file.. all the hype before was just that, a hype, ill probably only set it to 512, should help some without hurting anything .. its not going to double r/w scores or anything like what was happening before, but it will/should help adjusting it some

EDIT

Looking around, i did find this patchset.. ill mess with it some and see if it helps (theres more than this to the series)

http://lkml.indiana.edu/hypermail/linux/kernel/1003.0/00010.html

http://lkml.org/lkml/2010/2/3/27

EDIT EDIT

After looking at this some more, ill most likely set the VM_MAX_READAHEAD=512 and add readahead as a kernel parameter and then put a tweak in recovery to adjust to 1024... also ill mess with adjusting read-ahead/read-around size at once, while saving the low end from unnecessary memory pressure from the patchset...so this will be kinda different than the "sdcard-fix"...should actually help
[Captivate Android Development] nickm50:
COOL find! Looks like 2048 is way overkill.......

But what about if you have a 32g sd.......would you have to change the read a head to optimize it?

edit: answered my question while I was asking it........... Maybe make the option state for storage capacity? below x use this setting, above x use this setting? Where x=capacity