yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] aalh:
not using LP

I have actually never used a different launcher than the one that came with the rom

I ran Axura in December, I think Axura had LP, but I dont even have the Cappy that had axura, much less any LP install residue
[Captivate Android Development] RichMD:
Did not delete Voltage control before flashing

I had run Paragon 6 with UV set for noop for a while with no problems. I then tried Continuum 3.1.1 which did not have UV/OC support. I then flashed SuckerPunch #54 - no OC - just UV but I did not see the note about deleting voltage control. I then deleted the app and reflashed #54 and reinstalled Voltage Control. It came up defaulting to CFQ. I changed to noop and tried -100 for all which I know was stable on Paragon 6. It has frozen twice already. Is there anything elese I should do to "clean up" any problems since I initially flashed without deleting the app?

Edit: I also see "600 Mhz: ?" so it appears that it doesn't know which voltage is default for that setting. I saw previously, that 600Mhz was not an option so is this to be expected?
[Captivate Android Development] froli13:
" Delete S_volt_scheduler file" doesn't mean "delete Voltage-Control app"

You have to delete the file /etc/init.d/S_volt_scheduler

OR

In Voltage-Control app: Press menu --> delete boot settings

EDIT: Once you've done this, reflash the kernel and it will be perfect! ;) (Maybe you don't need to re-flash the kernel, but this way, you are sure you're making this right...)
[Captivate Android Development] RichMD:
Thanks, I just checked and that file doesn't exist. I think I deleted the boot settings in Voltage Control before flashing Continuum. I guess I should be fine then. I noticed your signature says CFQ which the "help" says to use if the kernel does not support UV - otherwise noop is best. Which is best? Should I be able to run the same UV settings on noop that I did with Paragon? I don't know if your phone and battery is the main items that determine usable UV settings or a different kernel (that has support) has a significant difference.

Edit: I read more and saw CFQ is now the default for this kernel. Apparently, the "help" in voltage control suggesting noop doesn't apply to this kernel. Yes, I should have searched before posting...
[Captivate Android Development] existz:
Which kernel are you using? SuckerPunch #54 or SuckerPunch-Voodoo #4? Cause it sounds like SuckerPunch-Voodoo...if so there's another thread for that kernel..
[Captivate Android Development] aalh:
then there is this from the Wiki page.....

NOOP scheduler is best used with solid state devices such as flash memory or in general with devices that do not depend on mechanical movement to access data wiki

I think it is not a "one size fits all" question

depending on how you use your phone, and where you use it, different combos of settings work best.

otherwise there would be a single modem file for the world;)
[Captivate Android Development] ridethelight:
For the life of me couldnt get #53 or #54 to be stable. Reverted back to #51 for now.

Ill be back to test #55 i guess lol
[Captivate Android Development] RichMD:
Thanks existz. You are correct, I was running the SuckerPunch-Voodoo. I had never run SuckerPunch before and didn't know there were seperate threads. I was about to give up on it since I was stuck in a boot-loop but am now trying #54-CWM. I want stability and the best battery life possible. I assume this version with UV set as low as possible while still ensuring stability is the best option to try.
[Captivate Android Development] existz:
With SuckerPunch, it uses very similar oc/uv code to Paragon kernel, as with Suckerpunch-Voodoo, it uses the older v21x code, so you will most likely have to redo your UV settings. During the last 54 versions of SP I've messed with alot of different code for the OC/UV.. Remember, just because certain settings worked on one kernel, it doesnt mean it will work on another, so you still might have to adjust your UV settings with this one as well.. There's alot of different factors that come in to play with different kernels, so if its not stable with the same settings used on another kernel, lower your UV, it might just be one frequency that needs lowered, or they might all have to be... this is why I don't support oc/uv, its not going to be the same on every kernel and on every phone, I just give the option to do it...if it works fine at stock voltages/frequencies, then its not a kernel issue, its an unstable oc/uv
[Captivate Android Development] existz:
Notice it says NOOP is best used with SSD, doesnt mean SSD is best used with NOOP, the IO scheduler controls how the kernel commits read/write to the file system.. I've actually optimized CFQ and its default for a reason...I've tested it numerous times with file system test and it gives better results, so just use CFQ for best file system performance
[Captivate Android Development] aalh:
you got it:)
[Captivate Android Development] GGXtreme:
What if you set states/oc/uv with Voltage Control, but use SetCPU for profiles? I'm loving the performance on #53 (will flash #54 in a few minutes), but I miss the ability to limit clock speeds based on battery/screen off/plugged in/etc.
[Captivate Android Development] aalh:
DONT USE SETCPU with this kernel

it could not be stated more plainly than that

It has been said over and over

if you are using setcpu, do NOT mention problems in this thread
[Captivate Android Development] existz:
GGXtreme

Lock your screen then unlock it, should give you 60+fps. Sometimes it does that after a flash, sometimes it doesn't..
[Captivate Android Development] Ptrout:
Couldn't get it to work stable for me.

On serendipity 5.12 tried both versions of the 54.

Runs neocore loop and stability tests fine to 50, @1300 cfq

But crashes on app drawer scrolling and anytime I try to install APk from ext SD

Other odd thing of note, when I set all the UV setting to 0, which I assume is stock voltage, it locks up within 5 seconds. if I flash stock serendipity kernel it doesn't lock up, so I don't think my CPU defective....

Maybe I'm testing this the wrong way, do I need to set max limit at every interval and stats, then run stability tests. Ie if I have 7 states, 1300, 1200, 1000,800, 600,400,200. Do I run the tests 7 times with each set at their respective max?

Thanks.
[Captivate Android Development] AReynante:
Yes, the tests push the phone to the max, so you would have set the max one step lower each time. But as for everything else going wrong, I'm not sure. I was using 54 for a little while and nothing went wrong for me
[Captivate Android Development] MaximumPotential:
The way i was told was to raise them one by one going up by 25 each time and testing until it is unstable. It is a long process but it works. I am at -50,-50,-75,-100,-100,-125 and am perfectly stable
[Captivate Android Development] johan8:
memory problem ?

Used #54 for a few days, no problem at all on my 2.2.

Then updated to 2.2.1 yesterday.

(tested just with stock i9000 kernel, everything fine)

Re-apply #54 and lagfix(all ext4)....

Browse web page with flash inside, play web base youtube....

memory ate up to 307/340MB.....!:eek:

Kill all tasks, just lower to 250~280.

After a while, memory usage raised to 280~290MB......

Then the phone become laggy.....!

where is the memory !?

Never have such problem in 2.2

Is it a problem of 2.2.1 or the kernel ?
[Captivate Android Development] existz:
I think you answered your own question, if it doesnt happen with a different rom, then its not a kernel issue... For it to be a kernel issue, it has to happen with every rom, and/or it has to happen with everyone...otherwise its an isolated issue caused by something else...this goes for anything...anytime there's an issue and it only happens on a certain rom, only happens to you..etc.. something else is causing it..not the kernel

But it could be from the new rom having more apps that run in the background, more services..etc..just disable the lowmemorykiller tweak in recovery, with it set default it allows more usable memory, allowing more apps to run before lmk kicks in, can't remember which version but since awhile back the settings was switched, before the stock settings was default, now the tweak is default, just disable it and lmk will kick in sooner, giving more free ram instead of more free usable ram
[Captivate Android Development] johan8:
I'm not sure.

Previously using 2.2, using new lmk, No such problem.

But now with 2.2.1, also with new lmk, 300MB used, flash inside web page are lag, phone become laggy.:confused:
[Captivate Android Development] existz:
My point is, its not from the lowmemorykiller, its from the rom having more apps..etc that's running in the background.. So disabling the tweak will help with that.. the kernel is not causing more memory to be used, the rom is, disabling lmk tweak will kick in sooner, killing more apps, sooner..giving more free ram.. I know it didn't happen on 2.2 rom, probably because there were not as many apps running, so with less apps running, theres more free ram..with or without lmk tweak

But that's just my guess.. some roms are stripped down and have less system apps than others...more system apps=more ram used...just recommending to disable the lmk tweak so it kills apps sooner, giving more free ram..
[Captivate Android Development] johan8:
And I wanna know is it happen to other people, or just mine.....

Sounds like GalaxyS doesn't have enough memory.....for newer system....

Tried keep playing flash, the browser keep eating memory, then the system just kick it out....
[Captivate Android Development] existz:
No, im currently on JS5 2.2.1, usually im always setting at around 210/340, when I do a level 2 clear it goes to 130/340
[Captivate Android Development] GGXtreme:
Charge death is usually caused by undervolting and should not be affected by SetCPU (actually, setting screen off profiles in SetCPU can reduce the chance of sleep death). Also, I now have SetCPU working just fine as outlined further down my post.

I will give it a try. However, I'm starting to get major issues with battery charging. For some reason, my battery started draining from 100% to 0% in under 2 hours with no use (no data/wifi/gps/BT/etc., no task killers, no SetCPU, no oc). I plug in the charger after the phone is dead and I immediately have around 40% battery.

I attempted to recalibrate the battery, but things started going downhill from there. Besides rapid battery drain, my phone would get sleep death (unrelated to charge death) and upon powering up I would instantly be down 10% in battery. I cleared battery stats, turned off the phone and plugged it in to let it charge. When the large battery indicator hit 100%, I got an instant kernel panic and my phone was very hot. I unplugged it and let it sit for a while with the battery pulled, then booted it up again. Battery life seemed relatively normal after this (although not great), but twice today my phone has gotten sleep death and gotten a "POWER RESET or UNKNOWN UPLOAD MODE", then the rapid battery drain resumes.

Kind of at a loss, as I can't tell if this is a hardware issue, but after going through 3 Captivates, replacing anything isn't an option for me right now.
[Captivate Android Development] existz:
If you flashed with kernel flasher app, reflash with cwm ..I've seen it cause some weird ****, kernel panics, only boot to safe mode..etc..then a flash with cwm resolves it.. As for the battery calibration, give it a few charge cycles and it will recalibrate itself, and usually battery life gets better... sometimes after a flash it screws up the calibration and battery will drain, you can't judge battery life right after a flash, also if you delete battery stats, then you have to start over..giving it a few full charge cycles... As for the rest of the ****, im not sure, after probably 100+ flashes of SuckerPunch (including test builds) I've never experienced any of those issues...nor has anyone reported it...so based on that, I have to assume its a bad flash and/or like you said a hardware defect...but im leaning towards a bad flash...but anythings possible

Also for the sleep death, Morfic from the Vibrant forum has mentioned to make sure the 800mhz step is used when making sleep profiles with setcpu as the 800 is needed during sleep, I have not verified this, but I do take his word on it, he's a very respected dev...but I don't know since I don't use setcpu...
[Captivate Android Development] GGXtreme:
I did flash with CWM, but I'll probably reflash anyway since I tend to get inconsistent results with a lot of things (modems, kernels, ROM's, etc.).

That's interesting. I actually use SetCPU to cap my CPU at 400MHz when in sleep mode (I used to use 200MHz, but occasionally lagged with music playback while changing songs). I'll bump my sleep profile up to 800MHz and see if that makes a difference.
[Captivate Android Development] existz:
Also its usually good to wipe cache and dalvik cache after a flash, note that it will take longer than usual on first boot for it to rebuild, sometimes when weird **** happens, it will fix them..I always clear both after a flash... but give the battery a couple full charge/discharges for it to recalibrate, usually takes mine around 3-4 or so full charge/discharges for battery life to get back to normal...
[Captivate Android Development] xreflection:
Could someone explain the difference between the 500hz and the 1000hz version again? Is battery life any different? 1000hz is smoother right?
[Captivate Android Development] existz:
Its 100hz and 1000hz...with the 100hz version it eliminates the kernel hz<-->user hz conversion, giving better battery life with little to no impact on performance (compared to stock HZ, I personally see no difference compared to 500hz)...but the 1000hz "should" be smoother on some things..you may or may not see a difference..if you dont, then I recommend using the 100hz
[Captivate Android Development] froli13:
Yes, but the other version is 100hz, not 500hz. The difference is very subtle IMO... I prefer the 100hz version (better battery life). The performance difference is not big enough for me to go with the 1000hz version.
[Captivate Android Development] xreflection:
Thanks for the quick replies. I'll give the 100hz ver a shot. I've been sporting the 500hz of speedmod k13c for a while, but I want to try out OCing and see if I can get a little more "umph" out of the cpu. Is stock clock 1GHz?
[Captivate Android Development] existz:
#55 should be up later today... added sched_autogroup patch.. should make things more smooth and responsive, should help while cpu is under load
[Captivate Android Development] existz:
Yes, stock clock/boot clock is 1ghz.. just use Voltage Control to set which "states" and max clock you want (i recommend having everything from 100-1000 selected for best battery life, then select your max OC...ie. 1200mhz)
[Captivate Android Development] GGXtreme:
Wow, you were right on the money about the unlock-relock thing. Getting higher scores and framerates than ever before in graphics tests.

I usually wipe the dalvik cache if things are acting up, but I haven't tried wiping the cache. I'll wait for #55 to be up, then wipe both before flashing.

Well, this sucks. I just can't get my SetCPU settings to stick. My profiles and settings remain, but the 'Set on Boot' and 'Enable' checkboxes on the profiles page always end up unchecked, requiring me to manually setup SetCPU every boot. I guess a solution would be to enable the 600MHz state (which is what gave me problems with 'autodetect'), but I'm not sure if having 7 states enabled is a good idea.

Also, maybe it's just me, but I notice a massive difference between 100Hz and 1000Hz (as well as 100Hz and 500Hz) in UI responsiveness, so I've been sticking to 1000Hz. Is this normal?
[Captivate Android Development] mipakr:
ok, what's the difference between #54 and Voodoo? i'm missing something here
[Captivate Android Development] existz:
Just a few differences...

SP #54

Based on Hardcores K13C

Ext2/3/4, JFS, RFS File Systems

Hardcores Color Tweaks

Hardcores Brightness Tweaks

OC/UV support up to 1.4ghz

Kernel TWEAKS and Color Profiles in CWM

SP-Voodoo

Voodoo Lagfix (Ext4)

Voodoo Color/Sharpness

UV Support (no OC) at stock 1ghz
[Captivate Android Development] xreflection:
Maybe I'll wait before flashing, haha. Was about to flash #54 when I read this.
[Captivate Android Development] LNJ:
I notice a higher RAM consumption on this kernal as well. Coming from an Acer Liquid E which had 512mb of RAM and it would have over 250mb available but the Captivate with the same amount of memory only has 130 or so available? How accurate e are the specs? Why is only a total of 340mb available?
[Captivate Android Development] existz:
Its the same on any kernel, it only allows us to use 340ish or so because the rest is used for the system/hardware...gpu, cache, 720p..etc..etc..
[Captivate Android Development] existz:
*UPDATE*

SuckerPunch #55

-add sched_autogroup patch

Should make things smoother/more responsive...should help while cpu is under load..
[Captivate Android Development] xreflection:
Ty for your hard work. Flash after my phone charges :)
[Captivate Android Development] Ptrout:
Wow after a full day of running tests....

My individual tests don't seem to work when multi state is used.

I tested using max oc, and only single state selected. Ran 35 iteration of stability and 15 minutes of neocore loop, and installing on off SD card.

1300 -75

1200 -125

1120 -150

1000 -175

800 -150

600 -150

400 -150

200 -150

100 -150

Final stable running 6 states, odd how individuals no crash but can't run those values when it has to change states.

1300 -75

1200 -125

1000 -125

800 -150

400.-150

200 -200

Is there an app that shows current clock ?

Thanks all for the help

1300
[Captivate Android Development] LNJ:
Yeah but out of the 340mb, only less than half is free on a fresh boot. How do we know for sure the rest off the 512mb is actually a system reserve?

Is there any dev tool that shows full hardware specs?
[Captivate Android Development] xreflection:
Was wondering the same thing. I want to make sure that I am actually testing at 1200, lol.
[Captivate Android Development] LNJ:
Download stability test from market and it will list current cpu speed on the top left when it is running.
[Captivate Android Development] xreflection:
Hmm, interesting because I just ran stability test and it said 999.### When I had my max set at 1200.

EDIT: After rebooting, I decided to leave the max at 1GHz because I don't have time to go through the testing again. (It froze on neocore before) I must say that my phone feels much snappier than before with this kernal though. Must be the new sched thing that existz added. Could be just me though. I like regardless :D
[Captivate Android Development] LNJ:
Did you select the frequencies you want in the pull up States menu? Apply them after you check them and only then will it be implemented.

I'm stable at 1.4Ghz with all frequencies selected in VC and scaler set to Conservative in SetCPU.
[Captivate Android Development] xreflection:
Yes. I had them checked in the states menu, then I clicked apply for now. Still shows as 995 or 999 next to the bogomips entry in stability.

EDIT: Hmm, I checked 1120 as well and now its at 1194, so I guess I needed the one in between to be checked.
[Captivate Android Development] it2swbrown:
Don't quote me but I think I remember reading somewhere that you need the next step down from your max cpu to be checked.
[Captivate Android Development] existz:
Sometimes you have to save vc settings twice for it to stick, which is what might have happened, you don't have to have 1120 selected, try unselecting 1120 and apply for now twice and see if it works then for 1200
[Captivate Android Development] GGXtreme:
#55 is smooth as butter, but...eh, I guess I have to give up on any sort of oc/uv. My phone is getting kernel panics and 'POWER RESET or UNKNOWN UPLOAD MODE' fairly often, as well as sleep death. I've already gotten rid of SetCPU, wiped cache and dalvik cache, disabled all uv/oc-ing and factory reset but it doesn't seem to help at all. My wifi will also not enable anymore, it just says "Error" in the Wifi Settings menu. I think my phone is fairly borked :(
[Captivate Android Development] xreflection:
I will try that after the stability test finishes. Thanks.

Ever consider flashing back to stock and reflashing your roms and stuff?
[Captivate Android Development] it2swbrown:
And...existz is right again. Took out 1120 and saved. Ran StabilityTest and it said 995. Saved VC settings again and StabilityTest said 1194.39. Good to know.
[Captivate Android Development] johan8:
Tks man.

I've fixed mine, everything fine now.
[Captivate Android Development] GGXtreme:
Yea, but the ROM I'm running is one I made for myself (JS3-based). My whole source folder is messed up--while the ROM has been functioning correctly on my phone for about a month (aside from the battery issues that started a couple of days ago), attempting to flash my last build gives me a softbrick (although it should be identical to what's already running on my phone, since it worked when I flashed it the first time) and I haven't had any success in narrowing down the problematic code/files. I'm too lazy to start from scratch, and I find that CWM backups don't restore consistently enough to risk, so I'm sticking with my ROM until a Samsung Gingerbread source is available (or someone adds mkv support to CM7).
[Captivate Android Development] xreflection:
I need some help with getting a stable clock..

I'm aiming for 1200 atm.

I have each level below 1200 set at -100, like in shaolin's guide. It passes stability test with no issues whatsoever. But when I go to run neocore, it freezes. I've tried multiple times and it was able to get through 10 minutes before it froze. Other times it freezes within a few loops. What do I change? I just tried setting 1200 at -125, but stability test froze. Should I set the one below 1200 to -125? It would seem that my phone may not be capable of reaching 1200 =(?

Also, could it be that I'm attached to AC power thats causing problems?
[Captivate Android Development] existz:
Lower your UV...if you have everything set to -100, change them all to 75, then test...if its stable, then start to raise each frequency 25mV at a time, but test each time you raise a frequency, keep doing that till its not stable again, then lower that frequency a notch, then move on to the next..you might not be able to UV to 100..ive seen some people only be able to get 50 on all frequencies..if that...nothing is gaurenteed, theres some phones that cant UV at all...just keep lowering your UV till its stable
[Captivate Android Development] xreflection:
Ohh...okay. I guess that part slipped my comprehension reading shaolin's guide. Thanks!
[Captivate Android Development] it2swbrown:
My settings are:

1200 -100

1000 -125

800 -125

600 -100

400 -150

200 -150

100 -150

I ran through 50 passes of StabilityTest and 1 hour of Neocore and it ran perfect.
[Captivate Android Development] xreflection:
I'll try out those settings sometime tomorrow. Time for bed :P.

How long did it take you to get those settings, btw? a while I'd guess right? Right now I have things all set at 75 and it seems okay. How much would this hurt battery life versus your settings?
[Captivate Android Development] it2swbrown:
I saw somebody else's post and decided to try them out and they worked. I haven't to push it any further yet but I will tomorrow.
[Captivate Android Development] xreflection:
Haha, just tried those settings and they definitely are not stable for me. Froze on apply now xD. Back to -75 for now...
[Captivate Android Development] s2h2golf:
Mine were, running 1.3ghz:

1300 - 0

1000 - 75

800 - 75

600 - 75

400 - 100

200 - 100

100 - 100

Regardless of what I did, and regardless of what kernel I was using, I always had to have the 600 set at -75.
[Captivate Android Development] Dungeon47:
Switched to SuckerPunch from Paragon. Screenshot says it all.

P.S. That's on 1ghz.

Sent from my Android using the power of Greyskull.