yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] GGXtreme:
Is that so? I don't remember that being the case. Hmm, well it's not that big of a deal. Although at first I thought I ended up with another bad USB port like on my previous Captivate, since I'm used to seeing the icon (which apparently wasn't there to begin with? :confused:).
[Captivate Android Development] Twicebak3d:
That made for some pretty interesting reading. Is it that too much can cause data inconsistency, or am I totally off? Overkill is overkill I guess lol. Really like that 512 to 1024 with cwm idea. I like the feeling of having some control haha.

Keep up the good work lol.
[Captivate Android Development] LNJ:
Back to 2.0.4 from the nightly.

I missed the smoothness.

I can live with the battery drain for now!

Sent from my GT-I9000
[Captivate Android Development] existz:
This will change the max readhead on everything, internal/external..(stl9, stl10, stl11..etc) as well as 179:0, which sets it for the external (i believe) so take that into consideration, i would judge it by your internal (16gb)..so 512/1024 seems to be the best..but for 32gb, 1024 seems good also..so..according to the patch, it sets 2048 for 64gb
[Captivate Android Development] nickm50:
So this patch has the potential to speed up everything.........

If it wasn't optimized to begin with.

When do we get to start testing it :)
[Captivate Android Development] existz:
Well, the way I have it for 2.0.4 sets it for everything also..but I think 2048 is way to much, and possibly causing higher memory usage, which could explain the higher battery drain.. The difference between the way I have it set in 2.0.4 and the sdcard fix script, is that the sdcard script just sets it for 179:0, which is external (i believe).. But the difference between 2.0.4 and 2.0.5 is I set the max_readahead to 512 (with option to change to 1024 in cwm)..which will set it that way for everything (stl9, stl10, stl11..etc..and external), and raised the min_readhead to 32kb (from 16)..plus updated some of the actual readhead code.. which helps with controlling memory usage

I should have 2.0.5 up later tonight
[Captivate Android Development] topiratiko:
Cant wait!

Sent from Paragon Optimized
[Captivate Android Development] pwnerman:
Question

Im on Serendipity 6.3 and can someone give me directions on how to flash this
[Captivate Android Development] nickm50:
Put it on the root of your sd, flash with clockwork, reboot.

Once rebooted, install voltage control from the market.
[Captivate Android Development] BigBen:
Auto-rotate glitch - button freezes

I just uptdate to the latest Onix kernel, 2.0.4 on Cezar's Continuum 4.0 and now my auto-rotate button has no effect - my screen rotates whether I choose auto rotate or not.

Rebooting seemed to correct the problem, but now after testing a couple of times, auto-rotate icon freezes - sometimes to "on" sometimes to "off." And the screen freezes to whichever state it was in before the icon freezes up. In other words, the screen could be in its non-auto-rotate stage, even though the button is set to auto-rotate "on."

I have been running Continuum for a couple of weeks. He uses the Onix kernel in his ROM and I have only upgraded the kernel as existz updates it. No other kernels have been on my device since I started running Continuum.

I have cleared cache and Dalvik, and reflashed the kernel .zip. I even checked the MD5 on the .zip before flashing. Rebooting temporarily fixes the auto-rotate glitch, but after a couple of times pressing the button, it freezes up again.

Any ideas, folks?

Thanks

Ben
[Captivate Android Development] nickm50:
Read back one page...(post 3830)...there could be memory issues with 2.0.4

2.0.5 will be up later tonight. Should fix the issue,as every release before this one has been perfect!

I had similar "strange" problems. I solved mine by wiping the phone clean and reinstalling 2.0.4, but I would wait for the revision tonight :)
[Captivate Android Development] sinichi21:
2.0.5 nightly is the best for me no charge of death for me been unplug for 12hrs and still on 88 % seems all good to me dont know about the others dont have a problem with the 2048 but the cwm option is cool to set it dont really care about much the cache for the sd card. hope when you release it tonight the performance to me will still be the same :D. thankz exist
[Captivate Android Development] pwnerman:
Best Kernel

Do you guys know what the best kernel is. Idk what to choose so give me ideas. i posted this here cuz i was checking this one out.
[Captivate Android Development] harpo1:
Try downloading 2.0.4 again. I had a modem earlier that wouldn't install for some reason and a fresh download and flash fixed it.
[Captivate Android Development] nickm50:
Posting in here will get you a very biased response............

Onix.

This is my favorite kernel. Frequent updates, And Existz is always around to answer questions, and works very hard to correct bugs.

The same can be said for all the Dev's here.

Did I mention Onix?
[Captivate Android Development] pwnerman:
You say onix but your signature says suckerpunch?
[Captivate Android Development] nickm50:
Onix is Suckerpunch............

It got renamed...... I just haven't modded my sig.
[Captivate Android Development] existz:
Well you got a few choices...if you want to get as much performance as possible, have alot of tweaking options..etc..etc.. then I recommend Onix :P ...you have the ability to OC/UV up to 1.6ghz, additional tweaks in recovery (performance cpu threshold, optimized memory timings..etc..etc..)...but if you want something thats rock solid out of the box, low maintence, something you can just flash and never touch again..I recommend using Hardcores Speedmod kernel (K13D)..

(woohoo post #1400)
[Captivate Android Development] pwnerman:
Sorry I know I sound retarded I havent changed Kernels or Modems yet
[Captivate Android Development] pwnerman:
Just a question but is overclocking to 1.6 bad for the hardware and battery?
[Captivate Android Development] harpo1:
And a thanks to get you to 400 for all the hard work you do.
[Captivate Android Development] Sqb:
Can't wait. I'm still floored by the amount of support you devs give here. Went to att to pay my bill yesterday and asked about sgs2. Rep told me not to bother since the iphone is going to release its next lemon soon. I had to laugh before I left. I wonder if their checks are cut straight from apple or if the have a ghost company to cover the paper trail. Thanks for all the hard work and support. Without you awesome devs and xda wed all be screwed. Well me at least
[Captivate Android Development] BigBen:
Thanks for your reply and the information on 2.0.5. Looking forward to flashing it.
[Captivate Android Development] existz:
Most phones (if not all) probably cant do 1.6ghz 100% stable (ive yet to come across one).. but the voltages up to 1.4ghz (1300mV) is only 25mV more than what stock max is for 1ghz (1275mV)..so its a very little raise in voltage.. Plus if you factor in UVing, then it will most likely end up being less the what the stock max for 1ghz would be..so theres really no harm.. as for 1.5/1.6, thats a little different, in earlier releases the voltage was 1500mV, which is quite a bit more than max stock.. But the reason for the high voltages was it gave room to adjust it lower to get stability (it was better having to much and being able to lower it, than not having enough to begin with)..but if running it at 1500mV and stressing it out for a long time could effect it.. the more voltages=more heat=less life span...But in 2.0.5 i lowered it down to 1375mV, it might have been to much voltage..so instead of having to UV 15/1600 by 150-175mV, you should only be able to have to use 25-75.. But for 1120-1400, theres not much risk.. for example if you OCd to 1.4ghz and you UV it by 50mV, you would actually be 25mV less than what stock is for 1ghz, so theres really no harm there..

As far as just UVing goes, lower the voltage = less heat = longer lifespan of battery/phone... but an unstable UV (to much UV and your phone cant handle it) then it can cause alot of issues,...ie. lockups, reboots, sleep/charge death, force closing..etc..etc.. but adjusting your UV to a lower UV will solve that. It takes some time to find your own stable settings
[Captivate Android Development] rajendra82:
April 8 nightly release performance update:

Been 8 hours running, with 1.5 hours time not in deep sleep. Battery loss 19%. Can't complain.
[Captivate Android Development] BigBen:
Hello, Harpo,

Many thanks for taking time to reply. I may give it a try while waiting for 2.0.5.

Off topic, sorry, but how's Groucho? Besides his old movies that he made with you and the other brothers, I used to watch him on TV in the 50s lol. Yep, that old. I'm a museum piece compared to most here on XDA :o
[Captivate Android Development] harpo1:
I'm 49 so not far behind you. It's funny because one of my friends father gave me the nickname harpo because of my hair. Big hair days of the 70s.
[Captivate Android Development] BigBen:
That's a cute story. Glad I was right on with guessing the origin. You're Harpo1. The original did have quite a head of hair lol. Well, wig, anyway.
[Captivate Android Development] existz:
*UPDATE*

Onix v2.0.5

-compiled with O2 + laststufo optimized CFLAGS

-randomize the location of the heap (brk) (security)

-add address randomization to mmap() (security)

-random ISN (28 bits hash instead of 24) (security)

-add fstack-protector support (security)

-more sched/mm tweaks and removed more debug

-revert PMEM_ADSP/MEMSIZE_BCM memory configs

-adjust read-ahead max to 512kb - min to 32kb

-limit read-ahead size for small memory systems

-add read-ahead tweak to recovery (1024)
[Captivate Android Development] antonyvijai:
I am on 2.0.4. Using continuum v4 themed version UGKC1 Modem. Can I flash this on top of 2.0.4 through CWM? Hope this will be an enhancement.
[Captivate Android Development] existz:
Yep, just select zip and flash
[Captivate Android Development] pwnerman:
SGS Kernel flasher

How do you install this with the flasher or is just easier to install by putting it on the sd and just going into recovery and flashing?
[Captivate Android Development] antonyvijai:
Thanks
[Captivate Android Development] harpo1:
I always flash them through CWM in recovery.
[Captivate Android Development] Sqb:
Thank you. Just like I said. Best support ever. You devs need to get tour own cell company. Thank you for all your hard work and endless hours.
[Captivate Android Development] existz:
Flash with CWM, ive seen kernel flasher app cause some crazy issues.. cwm is safer IMO, less chance of a bad flash
[Captivate Android Development] nickm50:
My only soft brick ever came from that program!

CWM is much more reliable.
[Captivate Android Development] pwnerman:
what if....

if im on the speedmod kernel is there anything special to do before flashing this? and if i decide to go back to speedmod what would i have to do?
[Captivate Android Development] antonyvijai:
^ totally agree!
[Captivate Android Development] nickm50:
nope, flash away. Going back to speed mod is the same, just flash back.
[Captivate Android Development] pwnerman:
Whats the difference

between

Onix-2.x.x-OC.zip

and

Onix-2.x.x-OC-1000hz.zip
[Captivate Android Development] nickm50:
"Whats the difference between 100hz and 1000hz?

HZ is an internal timer value used by the Android/Linux kernel. It affects the timer granularity of some kernel functions. With Kernel HZ=100, the Kernel HZUser HZ conversion is eliminated, giving better battery life while giving about the same performance (compared to stock)..With Kernel HZ=1000, it should give smoother results." -Existz

Quoted from the Q&A on page 1
[Captivate Android Development] pwnerman:
about how much worse is the battery with the 1000hz one
[Captivate Android Development] nickm50:
I didn't notice a huge difference. Your best to try them, and see which one you like better. I use the 100hz (which I think is actually 125 or 128 now).

Also when you flash, don't forget to enable the tweaks in the tweaks menu, they are not enabled by default.
[Captivate Android Development] Johnny Paranoid:
So do you suggest I enable the 1024 read-ahead tweak since I have a 32GB external SD? This is thought to consume more memory and therefore more battery, correct? All I have on that SD is music anyhow, so I've never really had a problem with the read speed when playing music. The media scanner is pretty slow, though.
[Captivate Android Development] abee_13:
I know its kind of early but I just flashed and wow!! its really smooth. Ill give some feedback about battery life and overall experience after a few charge cycles. Keep up the good work.

Sent from my cappy UC'd 900mhz and UV'd running di11is rom/ Onix kernel
[Captivate Android Development] IStern:
Seriously wow! Best suckerpunch/onix update yet!
[Captivate Android Development] nickm50:
Yes.

Its a global setting (changes internal and external) and a 32gb card is optimal for the 1024 read setting (you will be able to utilize the bandwidth). All the details are a few pages back.

It was the 2048 setting that was causing the issues.

I have 1024 enabled and it rocks!

http://xdaforums.com/showpost.php?p=12754322&postcount=3830
[Captivate Android Development] existz:
this isnt the same as the "sdcard fix".. this sets the read ahead value for both internal/external sd cards, plus there were alot of changes to the code for read ahead in the source.. read these..

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

http://lkml.org/lkml/2010/2/3/27
[Captivate Android Development] nickm50:
WOW.

This is the best revision yet. My phone has never been so responsive.

Great work ExistZ!
[Captivate Android Development] topiratiko:
Excellent kernel existz. Smooth responsive stable and fast. Feels worlds more composed than 2.0.4

Sent from Paragon Optimized
[Captivate Android Development] pwnerman:
question

i just installed this kernel and i was wondering how do oyu use voltage control exactly and i have a 16gb sd card anything i should do for that like that fix people are talking bout
[Captivate Android Development] Johnny Paranoid:
Got it. Thanks. I would have clicked your thanks button also, but we're limited to five per day. :(
[Captivate Android Development] nickm50:
Overclocking guide-> http://xdaforums.com/showpost.php?p=10936691&postcount=1102

You enable the read ahead in the tweaks menu in recovery.

There are also other options in the tweaks menu that you can enable.
[Captivate Android Development] geokilla:
With the read ahead fixes for both SD card and whatever else read ahead is used for, how does it play with FireFly 2.8? FireFly 2.8 also has the SD card fix. I'm sure more and more ROMs will in the future too.
[Captivate Android Development] topiratiko:
This question by RichMD was never answered and id love to know the answer!

Sent from Paragon Optimized
[Captivate Android Development] Delicate Donut:
Existz, which do you recommend... 100 or 1000Hz?
[Captivate Android Development] nickm50:
Firefly only changes the external SD card. As I understand it, The firefly setting will circumvent the kernal setting after loading, so you will see the firefly setting for the external SD card after loading.

The difference is that Onix changes the settings for the internal sd card as well.....

This translates into a faster UI (loading apps, making changes) Stuff that is not loaded into ram, faster load times etc.... This fix is different than the fix used in firefly. It affects the phone as a whole not just one part of it.
[Captivate Android Development] nickm50:
Tighter timings mean faster ram, which ,means a faster more responsive device.

If the timings are too tight, it could cause instability. It would only use more battery if he upped the voltage to the ram

The ram timings were adjusted from the generic settings to specific settings based on Samsung specs.

Try them.............. If they work for you great! If they don't turn the feature off...

I have always run them with no problems, and they do make a difference.
[Captivate Android Development] existz:
I recommend the 100 (actually now its 128hz...kernel hz=128 | user hz=150)..but it still gives the same battery life with a little extra speed/smoothness compared to 100/100hz.. But the battery life/performance ratio is better than 1000hz IMO.. 1000hz may be smoother during certain task (some games..etc..) but the 128hz version works just fine for me
[Captivate Android Development] topiratiko:
Thx nick im gonna try it

Sent from Paragon Optimized
[Captivate Android Development] pwnerman:
Question

I have the read ahead tweak and bln off from the recovery with this kernel and i wanna go back to speedmod do i have to do anything?
[Captivate Android Development] nickm50:
No.

If you used OC/UV go into advanced features in clockwork, and wipe voltage settings

Put the Speedmod kernel on the root of your SD and flash back.
[Captivate Android Development] Delicate Donut:
Figured I just wanted to know which one you used. I will gladly donate next week after these bills are paid off ;) I absolutely love this kernal I've had 0 issues since suckerpunch 57. Keep up the good work
[Captivate Android Development] pwnerman:
Question

when you flash a new rom or an update to one is your kernel and modem changed back to the original? are the setting reverted also
[Captivate Android Development] goodolsen:
Flashing yes, a full ROM install contains a modem and kernel. Updates usually don't contain either one.
[Captivate Android Development] 13_:
I am loving the feel of this update. It may be my favorite yet. Awesome work.... again. Many thanks.

Sent from a Captivate on Bluedipity 6.3, Onix 2.0.5, JQ1 with Xda App
[Captivate Android Development] thresherhorn:
First off, awesome kernel. Long time reader, follower, and advocate of tinkering with the captivate. This release is smooth as silk also.

Second, small question, any reason different versions of Onix would behave differently with the same modem? One thing I noticed was I recently flashed KC1 on top of 2.0.4 and was getting the first decent dl/ul rates of any modem I've tried (usually couldn't break 1/.5 and with KC1 hit 3/1 and have been getting these results constantly). But, right after I flashed 2.0.5 I decided to recheck for whatever reason and I'm back to not being able to break 0.4/0.1 :/

Thoughts?

Fixed: Coincidental Network congestion on flash :P
[Captivate Android Development] H3llstorm:
Could be network congestion or a busy server.
[Captivate Android Development] Twicebak3d:
I'm having pretty much the same prob, except I'm more like 1.1/1.3 atm on JK4.

With 2.0.4, I was getting just under 3 with U/Ls @ like 1.5. This was with good signal, and that pretty little H

EDIT: I guess it was congestion or something. 3.2 down :P
[Captivate Android Development] thresherhorn:
Ha ditto... hit a new high with 4/1.5... Just seemed a little odd that nearly all day i'd been hitting the highs and then right after I flashed 2.0.5 it bottomed out.

I retract my question, huzzah for crappy at&t servers!
[Captivate Android Development] antonyvijai:
Ok. What is it? Problem with at&t server or the onix 2.0.5? I am getting pathetic dl / ul speed. Should I flash 2.0.4 back? I am using UGKC1 modem. Pls let me know.
[Captivate Android Development] Twicebak3d:
I'm not sure if SD tools is the thing to benchmark SD with, but that's what I've been using. 2.0.3 no fix I was around 20/6, 2.0.4 was around 22/8.

Using 2.0.5 with the 1024 tweak, I'm 27/9 flat.

I only run it once, as I want to avoid cache interfering with my results or w/e.
[Captivate Android Development] existz:
Its not the kernel ...must be modem/network related
[Captivate Android Development] fractaline:
2.0.5 feels great.... Responsive, smooth.. Still working out my voltages.... Just had a freeze on unplugging.... That's what I get for testing in daily use....

On the modem note, I find onix is great for data speeds.

I'm using jvk and it's solid, almost never below 1.5/1.0 . Midday is the slowest usually, but I just got 2.5/2.0 ish and the lowest pings I've ever seen 60 and 46 !

Edit.... So is the kernel totally unrelated to modem performance?

It could be placebo...

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] antonyvijai:
Cannot be modem. UGKC1 modem with 2.0.4 gave me about 3.5 dl and 2 ul consistently. Let me see if this is network related. Or I shld go back to 2.0.4.
[Captivate Android Development] existz:
The only thing that might even come close to data speeds that was changed was CONFIG_WLAN_SAMSUNG_MEMSIZE_BCM=256 (was 512)...but I dont see it effecting actual network speeds...even if it does in some way, its still the same settings that I used with SP59 and below (also use with SP-Voodoo)..and was the settings used in Speedmod from K13C and below..ive only been using 512 the last 4 builds..and ive always got the same speeds with those kernels compared to Onix...so I dont see it being the issue...everything else wouldnt effect network speeds
[Captivate Android Development] antonyvijai:
So are you saying it is network issue?
[Captivate Android Development] Twicebak3d:
I'd say so. I was having network issues a little bit ago. Now I'm back up to normal on jk4.

I gotta say this is the smoothest I've seen my Cappy run. She's like butter, bro.
[Captivate Android Development] existz:
Yes, I havent changed anything that would effect network speeds...even with setting CONFIG_WLAN_SAMSUNG_MEMSIZE_BCM=256 (which i dont think it will effect actual carrier network speeds) it was the same settings thats been used during SuckerPunch/SuckerPunch-Voodoo and Speedmod K13C and below...nothing else was changed that would effect d/u speeds..
[Captivate Android Development] thresherhorn:
I'm sorry I even brought this up, lol.

Currently experiencing shaky d/u with any modem --jk4, kc1, kp1, jpp-- (getting anywhere from 0.4/0.1 to 4.2/2.1) ... thus it must be network. Momentary inquiry due to flaky service is simply what caused this.

Everyone put your pants back on :p this kernel is rock solid :D

Side note: Normally OC to 1.2 (previous builds started hitting lock ups past it) but so far with 2.0.5, OC to 1.3 and she's blazin fast and stable. :cool:
[Captivate Android Development] antonyvijai:
^ pants back on LOL...but I just noticed something after repeated network speed tests. With 2.0.4 and UGKC1 I got consistently around 3.5 dl and 1.8 ul. With 2.0.5 and same modem the dl is hovering around 2.5 with 1.2ish ul. Is there any idea why this is happening? Does it mean that KC1 does well with 2.0.4?
[Captivate Android Development] ewingr:
I installed Andromeda3, and then Onix 2.04, yesterday. I am trying to find a combination that prevents the modem 'error' status I get when using Tasker to enable/disable WiFi when I come and go from home.

With this combination, I still have that problem.

Tried your app above, made zero difference for this particular problem. (I assume it installed correctly...nothing in app drawer to run; and when looking at it in the market, it shows as installed, but the run button is greyed out. Assuming it just installs and runs in the background).

I just seem completely unable to get a ROM, Modem, and Kernel combination that doesn't have something wrong. I even have a thread about that and several said Anromeda3 gives that to them, but the kernel that ships with it does not OC/UV, and I need OC (because of my spastic need to have a lot of apps), and want UC to try to stretch my battery.

BTW...Exitzs' other kernel for Captivate gave me great performance, and marvelous battery life. I only left Cognition and that kernel because of this same problem: WiFi 'error' status.

[sigh] [/endsigh]
[Captivate Android Development] Twicebak3d:
You know... it could also be that you were testing on a different server when on 2.0.4.

Closest server to me is in Cocoa, but my best test results are always from Tallahassee, so I always use that as my test server.
[Captivate Android Development] antonyvijai:
My.comparison is from the same server!