yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] tazman171:
Well yeah, that makes sense, while it's slow, but 13% in 1 hr is a far cry below what the wall charger will do and shows that the car charger can barely keep up, if at all depending on use, which may be causing the shutdown that h3llstorm had and the charging issues jon.groves experienced. :cool:
[Captivate Android Development] LucasBrazil1984:
I've oc/uv my phone on this kernel and it's been perfectly stable. I don't if this is useful for anyone else but my settings are: 1200-25, 1120-50, 1000-50, 800-100, 400-100, 200-100, 100-100.

Sent from my Cappy using kickass FireFly 2.9, oc/uv Onix 2.0.5 and xda premium app.
[Captivate Android Development] TRusselo:
you guys are confusing kernel hertz (hz) of 128 and minimum speed of 100/1000 MEGA hertz (mhz)
[Captivate Android Development] shane87:
Actualy, there IS a 1000hz version. The difference, unless I am mistaken, is that on the 1000hz version, the user-space apps run at a base clock of 1000hz while the kernel, and anything that runs in the kernel space, runs at 128hz base clock. There is no 100hz version, as existz changed the 100hz version to 128hz, which means there is no conversion from user space to kernel space, which saves battery. It is explained in post 2, the faq post. And yes I do know the difference between the kernel base clock settings in hz and min/max cpu speeds in Mhz. :p It is easy to mix them up, since they use the same values, just different units. I have the 128hz kernel, and even though the 1000hz version is supposed to be smoother, I have seen no lag or glitches with this kernel, although I have not tested the 1000hz version.

[EDIT]As it turns out, I WAS mistaken above. The 100hz kernel sets the kernel hz to 100hz to match the userspace hz, while the 1000hz version sets the kernel at 1000hz to increase smoothness of operation. I have it listed the other way around above. In my defense, I was on my last break at work, and all I was thinking of was how much I would like to be at home, lol.[/EDIT]

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] aalh:
Spoke too soon

I started having sd's again last night, still doing it this morning

I am pretty sure the only changes I made were enabling the readahead tweak in CWM

and disabling the threshold tweak.

I have disabled the readahead, now I will try enabling the threshold tweak in CWM
[Captivate Android Development] Shammyh:
Lol, I'm pretty sure we're not.

He was suggesting running the non 1000 kernel hz version, since I was having problems with the 1000 hz kernel. I simply referred to the non-1000 hz version as 100/128 cause it used to have a kernel hz value of 100, before existz changed it to 128.

That's all kernel base clock. No reference to actual CPU speed here as far as I'm aware.

Either way, useful for others to make the distinction, since it can be a bit confusing to the un-initiated.
[Captivate Android Development] jon.groves:
So what happened to the nightly builds?
[Captivate Android Development] existz:
I stopped them for now, nothing new...been playing with 2.6.35 sources.. kinda waiting to see when i9000 2.3 sources drop (hopefully soon)
[Captivate Android Development] TRusselo:
oh shat you are right!... i was running off memory from my earlier days and what i understood then... and probably a few posts improperly saying mhz... OOPS.. totally my bad! you (I) dont think to re-read something you thought you understood.. but that was too long ago... once again my bad.

didnt the 100/128 hz playing started right after playing around with the min. speed? if my memory serves me correctly, that might be what screwed me up.... i think i remember some 500/250/100mhz versions or was that a different kernel?

i might try the 1000hz version now...

page 420... lol that reminds me i just got back from dave...
[Captivate Android Development] aalh:
Dave's not here, man.
[Captivate Android Development] GGXtreme:
On top of the other issues I mentioned, I'm now getting charge deaths and sleep deaths with no OC or UV. I'm going to flash 2.0.3 and hope things start working like they used to.
[Captivate Android Development] aalh:
I have had such oddness too.

after eliminating all changes other than using VC EX instead of VC

I reflashed 2.0.5 to see if that would change things before I removed EX to see if that was it.

I havent had an SD since I reflashed 2.0.5 but it hasnt been long
[Captivate Android Development] TRusselo:
2.0.3 was the only one i have ever had sleep death with. just that one time.
[Captivate Android Development] rlorange:
@exitz

Hello! Been a while away while using Jvk gingerbread but sources are out now for gingerbread! Don't know how that helps captivate users but onix i9000 gingerbread sounds bloody amazing to me :)

**Simply Honey 3.0, Voodoo GB hack, JVE modem**
[Captivate Android Development] geokilla:
Ah crap.... Another Kernel Panic while charging the phone when it was off. Definitely not caused by UVing or OCing as it's impossible to UV or OC when the phone is off. I don't think it's caused by the tweaks either... The problem is probably the kernel itself.
[Captivate Android Development] aalh:
I am now about to remove VC EX as that is the only remaining change I have made since these SD's started back.

I will update later today
[Captivate Android Development] sjavvaji:
so...jvk sources out...how long do u think it will take for xcaliburinhand to reorient and for u to get the overclocking goodies into it?...im hoping for a little more than a week :D
[Captivate Android Development] existz:
Shouldn't take long, hopefully...should be pretty similar to the nexus s sources, both are 2.6.35.7, I have a Dr appointment today and have to pick up my 1yr old son, so I will be pretty busy today, but I should get some time tonite to look at it
[Captivate Android Development] kodos96:
Well you can't get a kernel panic if there's no kernel running, and if there's a kernel running, then it must not be literally "off". I wasn't aware that there's a kernel running during "off" charging, but if you're getting a kernel panic then that must be the case.
[Captivate Android Development] existz:
Remember guys, if its only happening to one person ..it = something else causing it.... If it happens to mulitple people who CAN reproduce it ,it = something with the kernel ... I personally can't reproduce it..

And a kernel panic doesn't necessarily mean its a kernel problem , a kernel panic is just the kernel telling you it detected a fatal error with the system and its shutting down to protect the system...so one simple setting or tweak could be causing it, I'm not saying the kernel isn't at fault, just make sure to check everything first
[Captivate Android Development] Shammyh:
Had a kernel panic once a long while ago, and it seemed to just be a one off event.

Just like with science: if you can't reproduce it, it didn't happen.
[Captivate Android Development] kodos96:
onix-2.0.5-bigmem

So I've been experimenting with building bigmem versions of onix kernel, and thought I'd share my results in case anyone else is interested. The largest amount of available ram I've been able to get without breaking anything other than 720p video recording is 358mb. That's not as much as I'd hoped, but still, 18mb of extra ram in exchange for giving up 720p recording seems like a worthwhile tradeoff to me, especially since 720p video is too big to be very practical anyway.

I've managed to get up to 430mb by disabling the hardware video decoder, which would be fine by me, except that the youtube app doesn't seem to want to fall back to software decoding.... it seems kind of a shame to waste 64mb of system memory just for youtube, but that's how it goes.

So here's the 358mb version for anyone who wants to give it a try. If you find anything other than 720p recording that doesn't work with it, please let me know.
[Captivate Android Development] johan8:
You can try other kernel or back to stock kernel see if the panic still happen.

Most likely your system framework is corrupted so kernel panic is occured.
[Captivate Android Development] LNJ:
Trying it out. So what else can you free up?

Sent from my GT-I9000
[Captivate Android Development] kodos96:
Not a whole lot. The big ticket items are the hardware video codec (64mb) and the camera interface (25mb)... you can take 14mb away from the camera and everything but 720p recording will still work... you can push it a couple mb lower if you're willing to give up 720x480, but any lower than that and even the still camera doesn't work.

If you take ANY memory away from the hardware video codec, then youtube stops working, which really sucks, because for all other video I always use software decoding anyway, as it's less prone to audio sync issues.

Then there's 10mb reserved for texture streaming, which you can steal a few mb from, but any more than that and it seems to have a noticeable performance impact.

All the other reclaimable reserved memory I see is too little to be worth messing with.

This is all just based on a few hours of messing around with it, so I'm not an authority on the subject.... existz said something on IRC about having once worked out a config that got 350mb free with 720p recording still working.... I'm not sure how he did that, so obviously I still have more to learn about this.
[Captivate Android Development] geokilla:
Even I can't reproduce it... It's just a random event now. I was able to reproduce it before, but I fixed that by changing the steps used.

How can there be a fatal error when the phone is charging in its off state? There should be absolutely nothing running.... Or so I believe. You guys are the Captivate/SGS/Android masters.
[Captivate Android Development] AmandeepG:
They have dropped! So excited! :p
[Captivate Android Development] existz:
If I'm not mistaking I think I got the memory configs from DamianGTO in the i9000 forum... you can ask him or I think he posted the config in Hardcores Speedmod thread in the i9000 forum .. everything worked (including 720p) but I kept getting weird artifacts on boot, it was happening to everyone and they wanted it reverted,so I never messed with it anymore ..I had it in SuckerPunch #40 i believe, http://berryfx.com/RobBeane/Kernel/i897/SuckerPunch/ ,....but u can dig through old post in Hardcores i9000 thread, its been awhile ago, so might take u awhile, or ask DamianGTO for the configs.. I would mess with it some more but I've been playing with 2.6.35 sources (running Miui now) ,gonna start messing with new i9000 2.3 sources later tonight
[Captivate Android Development] kodos96:
By "crazy artifacts", are you just referring to the visual glitching on the white AT&T boot screen? Cause I get that too, I just don't really care as long as it works.

Yeah, it's probably pretty stupid timing for me to start playing with froyo kernel tweaking, when it's going to be obsolete in (hopefully) a matter of days... hopefully though what I learn will be applicable to the new kernel too.

Oh, and while I have your attention, I had another question for you: how do I build a 1000hz kernel? Just changing config_hz doesn't seem to have any effect.
[Captivate Android Development] existz:
Yea, right when the white att screen goes to kernel boot image, it was a small 1 liner at the top, wasnt nothing major and was the only side effect...but due to high demand to revert it, i did...

You can change CONFIG_HZ to 1000, but I always set it default in arch/arm/Kconfig also...just to make sure it sticks...you can change it here
[Captivate Android Development] existz:
Yea most of it is already applied to Onix, still need to "tweak" the recovery tweak some more, so it only effects sdcards instead of /system /data..etc..but most of the patchset is already applied to Onix
[Captivate Android Development] H3llstorm:
My phone didn't shut down because I lost power. My battery was nearly fully charged - and very hot. While I was able to use my GPS with my phone unplugged, I've found that I get better GPS reception/accuracy with it plugged in.
[Captivate Android Development] LNJ:
Existz, do you think the issues from 2.0.4 onwards we're more related to SpeedMod k13d?

Reason I mention it is cause I have been trying the Paragon kernel which is basically a k13a with oc/uv enabled and nothing else as far as I can tell and it is smooth as butter.

Maybe k13d does not like the tweaks you added :-p

Sent from my GT-I9000
[Captivate Android Development] sixstringsg:
He doesn't pull in all of hardcores stuff just things that are useful.

Sent from my CM7 powered captivate
[Captivate Android Development] aalh:
SD's came back,

while I thought it might have been EX I was commenting in Shane87's thread, but I dont have EX installed now

I uninstalled EX and just had VC all through yesterday

my phone was off again this morning, with 65% battery

I have disabled all CWM tweaks now, I will update results here after giving the phone a few hours to act up (or not)

2.0.5
[Captivate Android Development] grkmaster:
Are nightly's still being done?
[Captivate Android Development] sixstringsg:
What existz said a few pages back. The search function is nice.

Sent from my CM7 powered captivate
[Captivate Android Development] grkmaster:
Thanks, I know how to use the search function, but didn't think I'd need to. I like simple responses without a need of someone being a smart ass.(no offense)
[Captivate Android Development] abee_13:
So existz are going to see gingers pretty soon?

Sent from my cappy UC'd 900mhz and UV'd running serendipity 6.4/ Onix kernel
[Captivate Android Development] aalh:
14hrs uptime now, no SD's after disabling all CWM tweaks

I will let it sit overnight to see
[Captivate Android Development] Trae32566:
Can't wait to see your GB kernel, I'm tired of 2.2.1. Maybe I'll jump on the bandwagon this time and learn how to compile an i9000 kernel :/ As of now, my linux VM is f***ed up.
[Captivate Android Development] monkey5i:
Thanks for your hardwork, Speedmod K13E came out for a while, will you upgrade your onix to 2.06???
[Captivate Android Development] aalh:
25hrs uptime and no SD with all CWM tweaks disabled
[Captivate Android Development] TRusselo:
yeah i disabled everything in CWM last night. ran proper stability tests to under volt at each step. also removed a memorytimings script from init.d few others un accounted for, removed 4MB fix script, 1MB tweak selected in CWM.

already seeing BIG improvement.
[Captivate Android Development] grkmaster:
If im not mistaken one of the last nightlies included k13E but ill let someone confirm that (and since it hasnt been a 2.0.6 since the nightly it might not be stable lol)
[Captivate Android Development] aalh:
you always need to

(no offense)
[Captivate Android Development] sixstringsg:
He doesn't just merge in everything that speedmod does. He adds things that aren't there, and only add functions from speedmod that he doesn't have and that he finds useful. Onix releases aren't necessarily linked to speedmod releases.

Sent from my CM7 powered captivate
[Captivate Android Development] grkmaster:
Thanks for clearing that up! By any chance do you know which last nightly was the best one before he stopped it?
[Captivate Android Development] sixstringsg:
If it were me I would just download the latest final. If he changed anything significant, there would be a new final. If you want the most up to date, just download the newest nightly.

Sent from my CM7 powered captivate
[Captivate Android Development] aalh:
Is that your final ans:eek:wer?
[Captivate Android Development] sixstringsg:
It is now :p

Sent from my CM7 powered captivate
[Captivate Android Development] pwnerman:
Please tell existz

Tell him to attach this to the thread it will help alot of people IMO

http://xdaforums.com/showpost.php?p=12817245&postcount=4030

THUMB UP
[Captivate Android Development] existz:
As I posted in my sp-voodoo thread, I'm not sure if ill build anymore i9000 froyo based kernels, if I do it will be very little...most of my attention will goto i9000 2.3 sources, I've been messing with 2.6.35 sources for cm7 until xcal works his magic and gets it reoriented, then ill probably take what work ive done with cm7 sources and port it to gb 2.3 sources...(no I wont be releasing a cm7 kernel, just playing with them in the mean time) ..but ill see how it goes, might be another Onix release or two, who knows...
[Captivate Android Development] TRusselo:
i dont think anyone will be mad that you are moving on from our 2.2 kernel but thanks for telling us!
[Captivate Android Development] Sqb:
No apologies kind sir. We are also waiting patiently. To expect a release at this point is silly. Thank you for all your hard work and we can't wait to get you back once everything gets worked out.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] TRusselo:
ya but can we get some suckerpunch please? im a bit thirsty...
[Captivate Android Development] TRusselo:
update on this.. its been OVER 24 hours from unplugging, i have 72% left on my extended battery, but didnt do a lot on the phone today, bit of web browsing, bluetooth transfer, dropbox upload and email of a link, one call, updated 3 apps from market, few txt. screen at 60%ish

this is a huge impovement over before the changes quoted. woulda been down to 30% by now!

and i would say its running

smoother!

EDIT: now 30 hours down to 66% (phone call, updated more apps, read couple xda PMs, dl'd the big firefly update)

EDIT: 36 hours at 39% just a few more calls.

EDIT: 48 hours at 26% another call, some xda app, 1 speedtest.net on HSPA (300kb D 144kbU), wifi has been on whole time99%, data off 99% in power menu... was at 34% for a few hours.

EDIT: 57 hours at 15% I finally slept
[Captivate Android Development] abee_13:
Its funny how this thread went into silence once gingerbread made its way into or forums
[Captivate Android Development] topiratiko:
Yea its unfortunate. Its way to early to start playing with 2.3 roms so im stickin to my Paragon/Onix combo.

Sent from Paragon Optimized
[Captivate Android Development] aalh:
read ahead it is

I woke up with my phone off

the only change was enabling the read ahead tweak

I will continue testing each of the other cwm tweaks in turn after disabling RA and verifying the SD are gone
[Captivate Android Development] TRusselo:
thats the ONLY tweak i have enabled, but i removed the script (and others) in init.d

and read my edit above...
[Captivate Android Development] bballer182:
I was die hard Paragon/onix user but Paragon is old and out dated and hasn't even been tweaked since the first part of March... I even donated EspyeL. But then i tried Serendipity. I'm a changed man...
[Captivate Android Development] topiratiko:
Serendipity is good huh?

Sent from Paragon Optimized
[Captivate Android Development] H3llstorm:
Yep. Check out the Serendipity thread for all the comments from people who switched from other ROMs.
[Captivate Android Development] goodolsen:
Honestly a lot of the roms are similar. I switched from Paragon to Serendipity then to Firefly. Serendipity and Firefly are similar with minor differences. But if you are familiar with how to see what is in the rom and remove what you don't want then just pick one.

Then there is theming. Until 10tonhammr released his dark fire theme for serendipity you were limited to redrom or bluedipity.

It is all a matter of preference. Try as many as you want and see which one you like best.

Sent from Mister Red
[Captivate Android Development] H3llstorm:
I used a number of themes prior to Redrom & Bluedipity.
[Captivate Android Development] goodolsen:
That you made or from a post that the rest of us could find?

Sent from Mister Red
[Captivate Android Development] H3llstorm:
I used Generation X & Steel Blue before REDROM was even released.

I even included links so "the rest of us could find" them. :cool:
[Captivate Android Development] LNJ:
Continuum v4 and Matted Blues is where it's at!

Can't wait for Shoman to port it to the GB v5.

Sent from my GT-I9000
[Captivate Android Development] nappent:
So I've been running into a issue lately and I can't figure out if it is a rom or kernel issue. Randomly when disabling my Bluetooth my phone will reboot. What is odd is it isn't a full reboot because the Onix logo doesn't ever show. 90% of the time the reboot takes 10-15 second, other times it just gets stuck into a endless boot not to be confused with a booth loop but that the OS just never loads up until I do a battery pull.

I'm currently running Darky 9.5 with the JVK modem on a 1010 Build phone. OC to 1400 but I have seen this issue at 1300. I've tested with no UV and with. I am running Voltage Control EX 1.3 beta app. I've tried using all 3 different CPU Thresholds via that app. I've tried several different modems and I still get this problem randomly. And when I say randomly it’s like 1-2 times every 1-4 days. I do have the following enabled for the kernel: IOSCHED, KernelVM, CPUTHRESH, MEMTIMING, READAHEAD. I’m currently testing with the Memtiming disabled.

I have cleared my cache a couple of times now.

Any thoughts or suggestions? It's not a huge problem as it happens so rarely but at the same time it would be nice to know what is causing the issue or if anyone else has experienced this.
[Captivate Android Development] MarlowXim:
If it's a reboot it has to do with samsungs radio interface layer. The modem crashed due to a low reception and the kernel panics due to the modem crash. You can easily test this, stick around in a low signal area.

Endless reboot has to do with cpu/gpu stability. What ever you clicked it at most likely 1.4ghz is actually unstable, even running whatever # tests you did. I'd up the voltage. It only takes a couple math errors to cause kernel panics or weird behaviour.

10.10 build Rogers captivate? They tend to vary on cpu stability I've had several replacements. 1 was capable of 1.4ghz with 1300mV to 1325mV. That was may 25 2010 internal board.

On that note @exists can you change the voltage range of 1.4 ghz 1275mV minimum, I've had models that max was 1400mV to 1425mV. Most phones require 1275mV+ for that frequency. I've compiled my own kernel to address it but I think it would be beneficial for everyone else. It's in SO kernel sources of I remember correctly.
[Captivate Android Development] TRusselo:
screw it 60 hours, 8%

Im switching batteries......
[Captivate Android Development] aalh:
CWM conf file

is there a text file with the tweak and other settings in it?

or do I have to boot to recovery to see what is enabled during troubleshooting?
[Captivate Android Development] existz:
/etc/tweaks.conf (i think. can't remember right off, and on 2.6.35 so I can't check)
[Captivate Android Development] shane87:
Yeah, I just wanted to confim, /etc/tweaks.conf DOES contain the enabled tweks. I just checked it out.

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] aalh:
Not hard to find at all. Probably why I didn't see it. Thanks

Sent from your Id using XDAPremium
[Captivate Android Development] rlorange:
Yes please! Be the first to get OC/UV working on 2.3.3 :)

**Simply Honey 3.0, CF 3.1, JQ1 modem**
[Captivate Android Development] johan8:
Google has pull back Samsung update to 2.3.3

Sounds like Samsung 2.3.3 has big problem.
[Captivate Android Development] TRusselo:
old news and not that big of a problem!

not a problem at all for the developers here. go back to reading the instructions on continuum5 or i9000 stock....

nothing to worry about.