yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Made a little progress on new recovery, hoping to get it done in a day or so and get a release out.. should have some new options in recovery that are oc/uv related, im hoping to put the mem timing script and the new cpu threhold tweaks in there..plus some other stuff... as long as it goes smoothly except an update wednesday, ..*fingers crossed* ..
[Captivate Android Development] bclark:
I only use the kernel flasher when switching from voodoo to ulf, otherwise cwm only. And when I do, I boot right back out to recovery to make sure all went well.
[Captivate Android Development] ccdoggy:
Sweet! Great to have those options in recovery.

I noticed in the speedmod thread talk about fixing the wiring enable error, or at least work on testing some things out for it.

Have you put any thought into working on this or why its happening? It is really the only problem I have been experiencing l, though sounds like its a froyo problem.
[Captivate Android Development] meadhros:
My favorite technique. It is a salvation from the"scary bot screen"
[Captivate Android Development] meadhros:
Just checking...any one else having a reboot on 59 when charge drops from 60 to 59%. Or I might just be special....P.U .7se
[Captivate Android Development] Johnny Paranoid:
Has this happened consistently, or only once? If only once and doesn't happen again, I wouldn't worry about it. Some Captivates are prone to random re-boots. It's a known problem and not much can be done about it. If it's happening consistently, I would try re-flashing.
[Captivate Android Development] disellusional:
what happens if i continue to UV? is there any danger besides charge death? does it slow down the speed? etc
[Captivate Android Development] existz:
No, it just lowers the voltages, it can actually increase the life of your phone...less voltages = less heat = longer life...the only things that will happen with UV is if you UV to much it can cause instability, charge/sleep death, freezes, reboots..etc.. if that happens just raise the voltages a notch
[Captivate Android Development] disellusional:
thanks

i'm at 1200 max with

-100 -125 -125 -100 -125 -150 -150 mV

guess i'll do more testing to see how low i can go

is there any point to go past 1.2 except for speed improvements?
[Captivate Android Development] existz:
Not really, unless you use cpu intensive apps, such as emulators..etc.. that really need, otherwise 1200 does the job
[Captivate Android Development] rajendra82:
There is no chance of hardware damage due to undervolting, but there is a chance of the software crashes causing file system corruption. Thus you should target for zero crashes due to aggresive undervolting. Speed of code execution is technically only dependent on the clock frequency, and not voltage.
[Captivate Android Development] xreflection:
Hmm, my in call speaker does not work (not speaker on the back, but when you put the phone up to your ear). Will reflash the kernal and see if that fixes it..

NVM was some weird glitch..
[Captivate Android Development] existz:
alright..finally got the recovery down... got a few new tweaks added, anyone have any request they would like to see in CWM?
[Captivate Android Development] Soccer_Dad:
Interesting. I have had one charge death and one sleep death on #59. I hadn't really thought of it as caused by #59, but it hasn't happened before - for weeks anyway. It wasn't the usual death - I needed a battery pull to be able to restart.
[Captivate Android Development] Johnny Paranoid:
You added all those voltage and battery tweaks in CWM?
[Captivate Android Development] Soccer_Dad:
I'm not sure what you're looking for. But maybe the ability to apply (or revert from) the fugu tweaks?
[Captivate Android Development] bclark:
All the options Steam had?
[Captivate Android Development] existz:
like?

im talking about any tweaks that you guys would want selectable in cwm...for example I made the optimized memory timing script a tweak in recovery, so no need for the script anymore, just select it in cwm if you want to use it.. stuff like that, theres a few more im adding but was just wondering if anyone wanted anything specific
[Captivate Android Development] ridethelight:
set /system/ to RW? To allow for easy ADB pushing.

Ya know, for us linux retarded folk who have to google every command and study it for 2 hours before even attempting to use it
[Captivate Android Development] existz:
You can already set system to RW with the cwm thats in SP #59, under Tweaks, set Read-Write /system
[Captivate Android Development] existz:
For those of you waiting nicely and quite, heres a preview build of v2.0.1, the kernel is now named 'Onix' ...still working on a bootscreen, so that will be in the final v2.0.1..also still working on the recovery, still adding new tweaks, also not sure if ill keep the blue color, probably will change it to something different..but just wanted to post this and get some feedback before making it final..so let me know what you guys think..this is just the oc/uv version, there will be a non-oc version as well when its final..treat this like a BETA, there could be bugs...report them ONLY on my irc channel, not here... also theres no support until it goes final..There will be an option to delete voltage control settings via cwm now..should be in the final v2.0.1

Onix v2.0.1

- add oc and non-oc versions

- add oc up to 1.6ghz

--- new sysfs file for cpu threshold

- update voodoo sound v6

- Kernel modules updated from ZSJPJ kernel

- Ported fix from ZSJPJ kernel for downloading apps >30MB from Market

- Default lowmemorykiller minfree changed to 36MB

- New custom 'Onix' CWM

--- Optimize memory timings now selectable in cwm under Onix features/TWEAKS

---Can now delete VC settings in CWM under clockworkmod features..(will be added soon)

Make sure to delete your VC settings before flashing, the update-script is not set to delete it..

Download Here:

http://berryfx.com/RobBeane/Kernel/i897/Onix/Onix_v2.0.1-OC-CWM.zip
[Captivate Android Development] rlorange:
Yay! i9000 BETA#2 nearly here too? Still lovin beta1 totally stable

Doc JS8, SuckerPunch i9000 beta#1 kernel 1.3ghz, all ext4, JVE GB Modem,
[Captivate Android Development] existz:
Yea ill have a new beta for i9000 up soon, once i get v2.0.1 finished ill port it to i9000
[Captivate Android Development] elghouchd:
So will this have better performance than 59? Or is it about the same? Same with battery life
[Captivate Android Development] existz:
For me its been better all around.. speed/battery life..plus new editions to CWM, once I get the CPU Threshold Tweak added there will be an option for "Performance" which it effects the way the cpu scales, it will scale up quicker for faster results...but im still adding more though, just got done adding an option to remove voltage settings from there, once I get a few tweaks added that should be about it..will make it final then...but its not complete, so treat it like a beta..when its final it will be replacing what would be SuckerPunch #60...
[Captivate Android Development] Barbarian:
I like the blue text in Recovery. Nice change.
[Captivate Android Development] existz:
Thanks :) not sure if ill keep it that way, will probably make the top and bottom text a darker blue then make the menu text a lighter blue color..kinda break it up some
[Captivate Android Development] elghouchd:
So are there any serious bugs that we should be aware of before trying this or are you aiming for us to reveal those bugs to you with this beta? Im just wondering cause i dont want to install this then have something happen and have to restore my phone. And thank you for all of your hard work and dedication for making the captivate phone a better phone :)
[Captivate Android Development] existz:
There shouldnt be any major bugs, its been running great for me over the last week, its the same base as SP #59, just added oc/uv up to 1.6ghz and the 900 step, voodoo sound v6, then new recovery... also cleaned up some code, but all the major stuff is the exact same as SP 59..just make sure to delete VC settings before flashing
[Captivate Android Development] elghouchd:
Would adding the 900 step increase battery life? And I dont feel brave enough to go to that 1.6ghz step :( Im afraid the insides of my phone will burn.
[Captivate Android Development] existz:
It can..yea
[Captivate Android Development] meadhros:
That is the odd part. Not random. I can charge uo past 60% and then let it trickle down. First time I identified connection I tried to let it drop past 60 and it actually rebooted after dropping to 59%. Just for kicks I reproduced same result. I am not technically savvy

enough to dig into the files and look for things you to tweak but it seems like a specific setting effect. First time it did it twice and I did reflash. KB1 rom didn't seem to happen. Seems to happen on the JS7 rom.
[Captivate Android Development] ridethelight:
That has never once worked for me when trying to push things with ADB. Gives me the same error every time(non writeable filesystem).

And why the name change? Someone finally nail ya for copyright infringement? lol
[Captivate Android Development] bclark:
I went back and looked and really the only thing that you are missing from Steam is the file manager. So that would be cool but otherwise all good.
[Captivate Android Development] existz:
Nah, just changing the name on this one, SP-Voodoo will stay the same, cut down on the ones confusing the 2
[Captivate Android Development] elghouchd:
Umm So i booted up my phone after i turned it off, and when i booted it up clockwork comes up and says "New filesystem config detected. Convert?" then there are 6 options, they are:

-YES

-Yes, with factory reset after backup

-Yes Yes, with factory reset without backup

-No, enter recovery mode

-NO,remove the new config

-****Go Back*****

I have NO IDEA what to press and why this came up. Before I shutdown the phone I did a dalvik cache wipe and battery stats wipe. When I press "Go back" it takes me back to this same menu.:mad: Can someone PLEASE tell me what to press cause I have no idea what to do and i dont want to mess anything up. Thanks
[Captivate Android Development] osendott:
select YES, it converts your system to EXT4, perfectly normal
[Captivate Android Development] Johnny Paranoid:
Choose "Yes". Just plain "Yes".
[Captivate Android Development] itdiestoday:
Just flashed Onix. Not really sure why. Was on 59 and it was working great. I'm pretty much done with the over clocking.

Sent from my Captivate
[Captivate Android Development] existz:
Try typing "adb root" ...it will restart adb then use it as normal
[Captivate Android Development] elghouchd:
Oh no oh no oh no, alright so i pressed yes and now when i boot up my phone every app force closes and i cant press anything and then after a lot of force closes my phone reboots and i cant do anything and its a continuous process oh no oh no somebody please help me please please please help me.
[Captivate Android Development] froli13:
Gray/silver would be nice too.
[Captivate Android Development] existz:
Yea i thought about that, ill probably try it out and see... which im using a dark and light blue now, looks better than solid blue..but gray and light gray/whiteish might look good
[Captivate Android Development] osendott:
sounds like you're using an i9000 kernel with a captivate rom or something. what are you running?

nm just saw your sig..

not sure what the deal is then..
[Captivate Android Development] Johnny Paranoid:
Just flash back to stock using Odin and master clear. Then re-flash. If you can't get into download mode the normal way, try using these instructions.
[Captivate Android Development] Rodman101:
Well I has the same problem earlier and I reflashed 59 and cleared cache and dalvik cache and it worked

I'm feeling serendipitous...
[Captivate Android Development] existz:
Try wiping cache and dalvik cache in cwm, usually fixes it
[Captivate Android Development] Beny The Kid:
Don't want to ask a stupid question but is this still a reoriented I9000 kernel?
[Captivate Android Development] existz:
Yes, its still the same as SuckerPunch..just with a new name..and new updates, since their was quite a few updates and a new recovery, I decided to label it v2 (v2.0.1), and gave it a new name just for the hell of it..and because people keep getting this kernel and my SuckerPunch-Voodoo kernels mixed up, the new name should help with that. But this is what SuckerPunch #60 would have been..this is still built off of #59..just a makeover and some clean up
[Captivate Android Development] Beny The Kid:
Thanks! And thanks for all the awesome work!
[Captivate Android Development] GGXtreme:
Does the kernel rebase fix the wifi 'error' issue? I didn't even know that problem was related to kernel until I read Hardcore's post.
[Captivate Android Development] existz:
yea actually testing it out right now, the fix will be in the final v2.0.1... The way things are going I might be able to get it up tomorrow..as long as it goes as smoothly as its been..

On a side note, I still need a boot screen..anyone here good with graphics design? Need/want something simple and clean
[Captivate Android Development] goodolsen:
The new 2.0.1 should still work with all the same rom's correct? I'm running Paragon RC6.0 and#58 with no issues. Thought I should ask before I update once the final is ready.
[Captivate Android Development] existz:
Yea, its still the exact same as SuckerPunch, this is what SuckerPunch #60 would be, just a new name and some updates, i actually built off of #59, just added Onix Recovery, OC/UV up to 1.6ghz, Voodoo Sound v6, a few new fixes from hardcore, and cleaned up some code ..plus some other random **** here and there..and going to add a non-oc version
[Captivate Android Development] telefantastik:
I'm finding SP is a pretty cool kernel, especially in terms of battery life when UV'd. Thanks existz for awesome work!

One minor thing I find is scrolling through the home screen (I'm on Serendipity 6.2) is noticeably more sluggish compared to original speedmod, on both 100hz and 1000hz versions. I narrowed it down to the Conservative governor, for which it looks like SP defines different thresholds (OP mentions changes after #54). When switching to Performance governor it's super smooth on the home screen (well, all over as well, as expected); but when comparing to speedmod's Conservative mode, it looks pretty much as smooth.

Does anyone else notice the same? I wonder if there's a way to customize those thresholds back for Conservative, or maybe adjusting them just a little in favor of performance? A little battery life sacrifice is worth the full effects IMHO.

Many thanks!
[Captivate Android Development] existz:
Actually in the new v2.0.1 (Onix) which is what's replacing SuckerPunch, it will have an option for performance values for the cpu threshold in cwm, I've already got it added, just got a couple things left to do...then ill release it.. also added the memory timing script and an option to delete voltage control settings in cwm as well.. I will probably try to add a few more tweaks as I go along ..

But as of pre #59 the cpu threshold is set to basically 55/90, the performance settings are 30/70
[Captivate Android Development] telefantastik:
Wicked!

Forgive a noob question: 55/90 and 30/70 are scale up/scale down percentages?
[Captivate Android Development] existz:
Yea, as of right now its set to 55/90 (up/down) , with the performance tweak it will set it to 30/70..meaning it will scale higher faster, giving smoother results, but 55/90 gives the best battery life
[Captivate Android Development] fractaline:
stability adjustments

so i,ve used #59 for a few days now... with good results oc'd to 1200 uv from 75 to 125.

today the system froze while looking at speed test results, it tried to come back but not quite. reboot with button combo and all's well

question; do i need more voltage at low cpu speeds with this kind of issue?
[Captivate Android Development] Johnny Paranoid:
I would say so. When I first UV'd I had all the lower speeds at -100 and I locked up. Now I have them set to -75 and no more lock-ups.
[Captivate Android Development] telefantastik:
don't want to bother busy developers - last question i promise :)

Do you know what speedmod's threshold is? just wanna see as a comparison

thanks again!
[Captivate Android Development] fractaline:
thanks, johnny. we have the same setup (and frequent the same threads so it seems) so your advice is quite helpful to me.

could you offer a scenario in which you found you had not enough voltage on higher speeds?
[Captivate Android Development] existz:
Well there's 2 thresholds, the cpu threshold and governor threshold, I believe Speedmod is stock on both..which cpu threshold is..

55, 80 (100)

50, 90 (200)

50, 90 (400)

40, 90 (800)

20, 80 (1000)

...or something similar ,don't know the exact settings right off but its very close, if not it..then the governor threshold is 80-20

With SuckerPunch the cpu threshold is ...

55/80 (100)

55/90 (200)

55/90 (400)

55/90 (600)

55/90 (800)

55/90 (1000)

60/80 (1120)

60/80 (1200)

60/80 (1300)

60/80 (1400)

..then the governor threshold is 76-12 (stock is 80-20)...with the new cpu threshold tweak you will be able to set the cpu threshold to 30/70 for all, theres no way to set the governor threshold without building from source
[Captivate Android Development] Trae32566:
Anyone see this?

http://m.suckerpunchmovie.warnerbros.com/index_no_support.php

The logo looks identical.
[Captivate Android Development] existz:
It is the same...its where I got it from, we have talked about the movie a few times in here
[Captivate Android Development] H3llstorm:
I compared the new "Onix" kernel (basically Suckerpunch #60) and Suckerpunch-Voodoo #11 with various scheduler settings applied in the Voltage Control app (no O/C OR U/V).

More interesting (to me) than the composite scores are how the different scheduler options affect graphics and read/write performance.
[Captivate Android Development] :
I loled when I saw the movie logo at the end of the trailer when I was at the cinema on the weekend

Swyped from my captivating awesomeness with darky's rom
[Captivate Android Development] 13_:
OK. So in an effort to go more than 2 days without flashing something, I am waiting for the final and suppressing my desire to flash :o

That being said boredom took hold... so I fashioned up a boot screen. I'm not to skilled, just bored and figured I'd share the fruits of boredom :D
[Captivate Android Development] rlorange:
Tee hee found this... there's a whole series of em

http://www.google.com/m/search?site=images&source=mog&gl=au&client=ms-android-samsung&q=onix#i=151

Doc JS8, SuckerPunch i9000 beta#1 kernel 1.3ghz, all ext4, JVE GB Modem,
[Captivate Android Development] rlorange:
@exitz

Is it essential to put voltage control in system apps folder? I haven't but think I might... just curious

Doc JS8, SuckerPunch i9000 beta#1 kernel 1.3ghz, all ext4, JVE GB Modem,
[Captivate Android Development] H3llstorm:
Nice. I like this one.
[Captivate Android Development] H3llstorm:
You could download the Voltage Control app for free from the Android Market, and it'll take care of itself. :cool:
[Captivate Android Development] rlorange:
Oh hell yeah that's way better! That's ur boot screen exitz... or beginning of it :)

Ah I see that early post was from an era when voltage control wasn't in the market.

Hey I found a wicked electric blue version of the gingerbread keyboard on another forum. Highlights blue instead of orange I LOVE it! Can I share here? Credit due I assume to the author...

Doc JS8, SuckerPunch i9000 beta#1 kernel 1.3ghz, all ext4, JVE GB Modem,
[Captivate Android Development] 13_:
Lmao... I did the same thing....then got carried away... Ehh.. Fireworks is fun to play with every once in awhile.

Sent from a Captivate on Bluedipity 6.2, SP#59, JQ1 with Xda App
[Captivate Android Development] bclark:
Delete post....
[Captivate Android Development] H3llstorm:
Here's something I put together quickly in Photoshop.
[Captivate Android Development] Beny The Kid:
I know that originally we were using 3.0.0 voltage sched because the newer versions weren't compatible with the kernel. Has someone tested the the newer version with Onix? Is it stable.

The other question I have is, the file that exitz recommeds we put in the etc/init.d folder for mem scheduling in the OP, is it still required for Onix?

My phone doesn't seem to like being OC past 1200 mhz with Onix, it becomes seriousely unstable. With the Kernel OC to 1200 mhz and UV to 1225 the phone runs really smoothely and seems excellent on battery power though. I am liking the beta and can't wait for the official release. Would like to play with the CPU governor a bit.....

Also, anyone had any luck with preserving any more than 5-7 CPU states like the program says?
[Captivate Android Development] H3llstorm:
It's stable on my phone. :D

I'd recommend NOT using it anymore. My phone locked up testing both this kernel and the Suckerpunch-Voodoo kernels with Voodoo v5 and v6 sound.

If the CPU governor is the same as the scheduler in the Voltage Control app, I posted my test results here: http://xdaforums.com/showpost.php?p=12282414&postcount=2896
[Captivate Android Development] Beny The Kid:
I am not entirely sure, by governor I mean up and down thresholds (conservative/performance)..........I don't think the schduler does the same thing but I am unclear, but at least your results gave me a good indication of what shceduler to use.

On a separate note, I seem to have done something inadvertantly to prevent my computer from recognising my phone. I can't use ADB and I can't mount as external storage. The phone doesn't show any problems but it doesn't register on the computer at all. I had played with the RW/RO setting in CWM in an effort to get rid of the old voltage control file before flashing Onix. I eventually had to download root explorer which did the trick but now the computer doesn't talk to the phone anymore.......
[Captivate Android Development] Johnny Paranoid:
I've never had a crash or lock-up due to UVing at higher speeds. I've never gone more than -100 at higher CPU speeds and I never OC past 1.2Ghz. I think -100 is generally where most people are at. Everyone's phone is slightly different though. Every chip is not the same. Don't be afraid to experiment if you want. Just make sure you don't save anything as a boot setting before you know it's stable. If you haven't already been using it, Stability Test (avail. in the Market) is a really useful tool. If you can make it past 30-50 CPU core runs, you're at a pretty stable level.
[Captivate Android Development] H3llstorm:
I haven't tinkered with the RW/RO settings in CWM, but if you haven't already returned them to the default settings, that's where I'd start.

I always connect my phone in debugging mode. I haven't tried using mass storage mode with any non-stock ROMs.

Correction: I just tried it and it worked. :cool:
[Captivate Android Development] fractaline:
Yeah, I had been boycotting

Any benchmark tests, but used them to get a handle on the oc/uv settings. But I didn't bother to isolate and check each speed individually, figured real life testing was,.......well, more real.

Thanks, I'll keep poking at it.

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] Beny The Kid:
Thanks. i am unfortunately not near my DEV computer right now, so I will give it another go later when i get home.