yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
If it doesn't happen with OC/UV then your settings are not 100% stable... I can't do anything about it since its not an actual kernel issue, anything above 1ghz and below stock voltages is out of my control

EDIT

Just tried it myself with no problems, OCd to 1200 with (1200 down) 75,100,125,100,125,125,150...so its not an actual issue, just an unstable frequency somewhere

EDIT 2

just looked at your oc/uv again, if your OCd to 1200, it will probably be better to remove the 1120 step and add the 600, you really don't need a step between 1000-1200...also the 600 step should help with battery life ...
[Captivate Android Development] froli13:
Just did it again without changing my oc/uv settings and it didn't freeze. I was able to go back to camera mod. So I guess I don't have to care much about this little "issue" lol
[Captivate Android Development] xdahgary:
Thanks for the tips existz. It lasted longer this time. ~about 10 switches. Gonna keep working on it.

-50 -75 -75 -75 -100 -100 -100
[Captivate Android Development] opcow:
I can switch back and forth between still and video without freezing. I have had the phone completely freeze a couple of times when using the camera (on #50 and #48, I believe), however.
[Captivate Android Development] oFUNGUSo:
does anyone here actually run at 1.4ghz completely stable with NO problems at all and with UV settings?

i seem to be CLOSE to stable enough.....but i did just notice i have that camera freezing problem (switched about 5 times before it freezes for a couple of minutes, the reboots)

running

100 -75

200 -75

400 -75

600 -75

800 -75

1000 -50

1200 -50

1400 -25

no idea if im even on the right track. but the phone runs good for the most part
[Captivate Android Development] cumanzor:
Hey I'm also using Serendipity and SuckerPunch. How is your UI performance?

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] oFUNGUSo:
everything seems perfect if i DONT use any animations. if i use all the animations, menus get kind of sticky/glitchy sometimes. fiddling with my UV states has made it better....

im thinking i might have to give up on the attempt at sticking with 1.4ghz unless someone more experienced can supply some ideas on how to possibly set it up.
[Captivate Android Development] johan8:
I have the similar issue,

most of the time my phone run stable,

take photos, use barcode scanner....

However after couple hours, take photos may freeze....

or barcode scanner can't start then photo freeze, then photo reboot after a minute...:(
[Captivate Android Development] RockRatt:
I have been using 1.4 for a few hours now with no issues. I am ONLY undervolting to -75 on ALL at this time though. I will slowly increase the numbers over time until I know where I can run stable at.

The weird thing is anything above the 1200 for me seems to have worse numbers for Quad, Linpack, and other test. I don't rely on them anyways but thought I would mention it. It does ACTUALLY feel faster and smoother at the higher MHz though.

Sent from MY 1007 Build using SuperNova 2.3 JS5, SuckerPunch #51 1.4Ghz, UGJL2 or UGJK4 depending how I feel on XDA App
[Captivate Android Development] existz:
Something is not right then, linpack will always score higher with higher mhz, at 1.4ghz I get around 19.2-19.7...1.3ghz gets roughly 18.5ish ,give or take a few ...so if its not scoring around that, then the max clock is not sticking ..
[Captivate Android Development] oFUNGUSo:
do you keep your phone at 1.4? if you do, i would be very interested in knowing your setup.....sorry if you have already posted it, its probably a good possibility you have
[Captivate Android Development] bay_wolf:
^ Same happens to me with the animations. I had to switch back to GBs kernel to make the animations run smooth.
[Captivate Android Development] sjavvaji:
mine is stable...i found that it wasnt the kernels fault...the camerafirmware.apk from JS5 wasn't working well from the modded camera.apk so i had to replace it with the one from JS3 and i don't have any problems...

100 -100

200 -100

400 -125

600 -100

800 -125

1000 -100

1200 -50

1400 - 0
[Captivate Android Development] rurouni572:
Based on what I've been reading in this thread, this kernel seems to have a lot in common with speedmod. I realize that it's based off of speedmod, but other than OC/UV, what other differences are there? Even all the tweaks and lagfix options seem to be identical.

I apologize if I sound critical. All the kernels and rom's seem to be converging recently and it's getting hard to differentiate between each one's core features.
[Captivate Android Development] existz:
The animations being choppy is probably due to the threshold values I use, it improves battery life but a few things take a hit from it... ill test some different settings and see if it decreases battery by alot, if there's little change ill use faster settings in the next version
[Captivate Android Development] existz:
Read the changelog, even though its based on speedmod I've added alot of different tweaks...
[Captivate Android Development] oFUNGUSo:
edit.....i just realized jk4 is the modem and not what your talkign about. im not sure what serendipity based on. im not sure how to go about swapping the camer apks, so i think i will try a different rom that i know is based on js3. im shooting in the dark (or at least low light). ill figure soimething out
[Captivate Android Development] oFUNGUSo:
i just went back to #50.....tested camera same thing happened. even quicker this time.

removed overclock settings. still camera froze up.

tired without overlcock and no UV settings. still froze up.

hmmmmm. :confused:
[Captivate Android Development] opcow:
Are you running the 1000Hz or 100Hz kernel?
[Captivate Android Development] oFUNGUSo:
i got laggy animations on both
[Captivate Android Development] ulupinar:
I have the same problem. The phone runs fine all the way up to 1400, except for the camere or any application that uses the camera, such as google goggles. One of the sure-failure is to click the camera/movie mode button on the right top corner of the camere as quickly as possible. This always freezes the phone if I overclock it even at 1200. Otherwise the phone runs fine all the way up to 1400.

I was thinkig, if there is a way to lower the CPU clock to 1000, whenever comera app starts. But your method is better if it really solves the camera freezing issue. Can you provide a link to the camerafirmware.apk that you mentioned.

thanks
[Captivate Android Development] sjavvaji:
are u using js5?...my problem was that i would get a force close clicking the view photos button (because it was an incompatible version)...i don't have an issue with toggling camera/videocamera...i did also mod a few things from my doc's JS5 so it may not be relevant...i have always been rock solid on 1.4ghz...you may not be stable
[Captivate Android Development] Peaster111:
Gotcha... figured it was related to your memory settings... no biggie. For now I've just turned off animations entirely. The kernel screams... and has the best battery life I've experienced to date. GB's kernel is the only other that has come close.

Thanks for the feedback... later
[Captivate Android Development] elghouchd:
yay for faster settings!
[Captivate Android Development] bclark:
So I woke up this morning with my phone off. Wasn't plugged in, it wasn't a UV death it was just off. Using 51
[Captivate Android Development] nissy86:
hello, i'm new here.

i have a few questions.

for the voltage control, is there any difference between the schedulers? Should i use noop or cfq?
[Captivate Android Development] AReynante:
Suckerpunch should use BFQ by default, but if thats missing or something, I'd use noop as my second choice
[Captivate Android Development] hauj0bb:
Can I flash SuckerPunch over speedmod without disabling tweaks/lagfix?
[Captivate Android Development] existz:
Yes

10char
[Captivate Android Development] AReynante:
I believe you should be fine, cause suckerpunch is based on speedmod, but I'd let someone else confirm first

Edit:

Lol, beat as I was typing :)
[Captivate Android Development] cishos:
I am VERY noob to this overclocking/undervolting thing.

I just flashed #51 and Install VoltageControl_3.0.a3.apk

and I went in the voltage control and have no idea what to do...

if someone could point me in the right direction, it would be much appreciated! ^^
[Captivate Android Development] RonH54:
Is anyone running SuckerPunch on Darky's 9.3 Beta 3? I am thinking about giving Beta 3 a test going from Darky 9.2.
[Captivate Android Development] existz:
Check out shaolin95s oc guide in the OP, but basically you have to set which frequencies (states) you want active, leave 100-1000 checked for best battery life, so if you want to OC to 1200, select states and then check 1200, if you want to OC to 1300, just select 1300 instead of 1200... then set the max clock to whatever your highest clock is, so if you set the 1200 state, select 1200 as your max clock. I cant promise anything over 1ghz, so you will have to test and see what your limit is. As for undervolting, same thing, I cant promise anything under stock voltages, but its best lowering 25mv at a time, then stressing it and testing it till it crashes to find your max UV. But watch out, cause most stress test only test at max clock, so you wont know if a lower frequency is 100% stable, I usually just use my phone and if it works doing what I do, then that's all I need..you can set your max clock to 800 for example, run stress test if it passes then lower to 600 ...etc.. but even though it passes stress test, it doesnt mean its stable, so if you get charge/sleep death, freezing, reboots, fc's...etc lower your UV, it might only be one frequency that needs lowered, or it might be 2-3 ..etc, its a long road to finding your 100% stable settings, just mess with it some
[Captivate Android Development] cishos:
what do you mean leave checked? I don't see any boxes to check.. all I see are the various states
[Captivate Android Development] existz:
when you select the states tab at the bottom, it will pop up a menu with all the states with checkboxes beside them (make sure to use the VC app attatched in the OP)
[Captivate Android Development] cishos:
oh okay! thank you!

currently I have everything up to 1200hz @ -100

would you provide some stable configs for your setup? I would like to see how much others have and base my configs base off those :D
[Captivate Android Development] A.VOID:
tried suckerpunch from speedmod.

Battery was getting killed on this suckerpunch. Not sure what the issue was since it was great under speedmod and everyone claiming great for suckerpunch ..
[Captivate Android Development] runawayprisoner:
Performance has gone down quite a lot for me after #48. #48 still gives me the smoothest animations and best battery life. And the 500Hz version is more responsive than 1000Hz.

But then again, I guess I'm in the minority as I run at 1.4GHz all the time.
[Captivate Android Development] WickedNite:
So why change the default from cfq to bfq?

Sent from my Muscles using Brain Cells
[Captivate Android Development] existz:
Just trying different things, will probably revert back to CFQ in next build or so..as CFQ seems smoother
[Captivate Android Development] psloan:
Thanks existz. I followed this advice. Did a full flash/wipe of andromeda 1.2, formatted the sd cards. Flashed Suckerpunch #51. Then installed the essential apps. Did the battery calibrate stats flush. One day to fully drain the battery. Started last night with a fresh charge at 99% woke up to 95% with wifi on all night, 6 hours and 4% drain. Today at 11 hours of use with some pandora, podcast listening with Bluetooth on, some texting etc.. I am at 80% battery left. I still don't have all the apps I wan't back on. I am worried about putting touchdown back on. I suspect that touchdown might be my battery killer. I will put that back on tonight and see how tomorrow turns out.

But I am very happy with these battery stats. I

Thanks.

--pat
[Captivate Android Development] Mevos:
Music player battery usage

I've been wondering what % of battery per hour of music I should expect to get from a phone with good battery life?

I'm listening to music constantly at work and after 10hrs i'm usually sitting at a bit below 50%, which means around 5%/hr.

I'm pretty sure I could at best get it down to a bit more than 3%/hr once (Which I don't remember the ROM I was on back then)

What's everyone else's %/hr with no wifi, no gps, no streamed music and screen always off?
[Captivate Android Development] IStern:
The best idle phone battery saver I've found is to force the 850 band using sgs tools. On automatic I generally lose about 4%-5% an hr due to the modem switching between 850 and 1900. Once forced to 850 it's down to less than 1% an hour. I'm currently on JK4 and I'm honestly not sure why it wants to keep switching bands.
[Captivate Android Development] existz:
1+ ...same here, awhile back I was digging through logs and noticed mine switching every 30seconds from umts to hspa, turned hspa off and now I get 1% idel as well, if that,..by far the best thing I done to save battery.
[Captivate Android Development] M1nur:
im wanting to apply the script from the new update but i dont have the etc directory.

Just create it?
[Captivate Android Development] existz:
Yep...

10char
[Captivate Android Development] cishos:
may I ask how you did that? I have SGS tools and I know it's under bands but I'm not sure what i have to check and uncheck. much help would be appreciated :o
[Captivate Android Development] existz:
Goto secret codes then at the bottom, Switch 3G--HSPA then option 2 (change hspa revision) then 1 (release r99 hspa off) that will disable hspa ...it will stick through reboot...also give it a few min after you switch for it to switch from HSPA to 3G
[Captivate Android Development] oFUNGUSo:
frustraiting. i really want to use this kernel buit i cant seem to make it work, even without underclock.

wasnt working for me on serendipity, kept having camera freeze and screen refusing to time out unless i reboot. no matter what settings i tried.

changed roms to paragon and tried the kernel again, still having camera freezing issues on any combo of settings.

went to paragon 1.4 oc kernel and there is no camera freezing issues.

grrrr! i want suckerpunch!
[Captivate Android Development] ReznikAkime:
Since this kernel update (51-100hz) and the memory timing tweaks I've been getting constant neocore scores of 63-65 without overclocking. Seems its a cap, when I push it to 1.4ghz it maintains the same fps. Not complaining though. Better performance clock for clock is better in my eyes.
[Captivate Android Development] xdahgary:
Thinking of trying paragon's kernel too. Heard he's about to release version 6.
[Captivate Android Development] Phoenix-Lead:
How is your phone functioning? There are very important files in that directory.
[Captivate Android Development] existz:
For some reason I had the init.d directory on my mind...as adam mentioned, the etc directory has some important files, I too am curious as to how your phone is functioning without etc dir
[Captivate Android Development] bhairya:
Maybe I'll have more luck asking here. I'm relatively new to flashing ROMs on my Captivate and totally new to OC/UV. This is a general question about OC/UV and not specific to a kernel per se. I've flashed my first OC/UV capable kernel today and was playing with the settings in the voltage control app. I read the OC guide and some of the related posts in this thread. Currently my settings are 125 100 100 100 100 75 from 100Mhz to 1280Mhz. Is there an app or widget which shows the CPU frequences/voltages in real time? I'd like to get an idea of how the CPU runs at different frequencies at various levels of use. It would also allow one to see if the OC/UV settings are working. For example, how do you know your CPU is running at 1280Mhz if that's what you've allowed it to run at? How do you know what voltage it's using? The guides I've read basically tell you it's a long process of trial and error either by using some stress software such as Neocore or just using the phone and seeing if it crashes, etc. There should be an easier way to arrive at settings which give you a stable phone for whatever you use it for besides calling. I'm wondering if there's a popular app/widgets folks here use. Thanks.
[Captivate Android Development] jojorios:
This is really weird. I'm using serendipity 5.11 and if i run this with it, Words with friends becomes unplayable. Numerous FC's and freezing. Once I put #48 back on, all runs perfect again.
[Captivate Android Development] existz:
There's none that I know of, other members might know of some though...but to tell if its hitting 1280 for example, you can use SystemPanel and see it scaling frequencies, you can't watch it out side of the app but if you move the screen up and down you can see it scale to higher/lower frequencies, that way you can tell if its actually working. Also, as to seeing what frequencies are being used, there's a command you can type in a terminal emulator to see how much time is being used for each frequency, its in the OP. As for voltages, there's no app except VC, as far as I know, the best thing I know of is using a file explorer like root explorer and going to .../sys/devices/system/cpu/cpu0/cpufreq/frequency_voltage_table ...the first column is the frequency, the second is stock voltage and the third is the current voltage..or use a terminal emulator and type..

cat /sys/devices/system/cpu/cpu0/cpufreq/frequency_voltage_table

..that's the best I can do..
[Captivate Android Development] RonH54:
I have been talking to some of the Developers of Darky's ROM which I use and it seems that with their Final 9.3 version which will be out soon you can't used the Tweaks that come with SuckerPunch and SpeedMod due to some type of changes they are making between 9.2 and 9.3, hate to hear this.
[Captivate Android Development] bhairya:
Thanks, existz. You'd think it wouldn't take much for someone to make an app reading this data and showing it on a small widget/app updating in real time. I don't know if the kernels used here have a /proc filesystem which could be read to do just this.
[Captivate Android Development] pizz0wn3d:
The problem with that is that you can't see the widget when you're using an app. As well as the problem with battery drainage from real time updates.

Herp Derp Captivate XDA
[Captivate Android Development] MikeyMike01:
Words with Friends stopped working properly (freezing and force closing). Switched back to speedmod and it works again.

Sent from my Captivate.
[Captivate Android Development] existz:
Ill look into it, not sure what would cause it... im thinking of building from scratch, seems when I do something it fixes a few things but ends up causing 2 more...ill probably start fresh so you guys might not hear from me for a day or so ..
[Captivate Android Development] johan8:
Which tweaks you mention about ?

I think those tweaks are kernel level,

once you flashed SuckerPunch or Speedmod or other kernel,

you can use its tweaks.

Not able to use those tweaks, means that you are not using SuckerPunch/Speedmod kernel.
[Captivate Android Development] johan8:
My phone freeze many times yesterday.:(

Basicaly everything works fine and stable, take photos, barcode scan......

But after some period of time, maybe couple minutes or couple hours,

phone freeze after taking photos, or during barcode scanner startup......
[Captivate Android Development] AReynante:
Are you UVing at all? That's usually the main cause for freezing, also/or it could be OCing too high. I know my phone can't go over 1280, so I have mine capped at 1200.

And if it is only after a period of time after using the camera app / barcode, you could have a faulty camera.apk? I really don't know for sure, but just trying to help :)
[Captivate Android Development] johan8:
Yes.

But tried my OC/UV, my OC just 1200....

tried lower Oc/UV, UV just -50mV

also tried cancel all OC/UV.....

My camera.apk is from stock rom, I haven't change it.
[Captivate Android Development] MikeyMike01:
I was using settings I had used problem free for months, yet it froze frequently. I backed them off a bit, and I still had the occasional lockup.

Then I gave Words with Friends a go, and ended up having to pull the battery.

Sent from my Captivate.
[Captivate Android Development] r3ferrei:
I haven't been able to uv below 50 on this build. It might only be a certain frequency that is causing issues but I went with no uv for now.

And now its really stable, even at 1400 surprisingly. To hell with battery life!

Sent from a Serendipitous Suckerpunch
[Captivate Android Development] AReynante:
I'm running OC to 1200, with UV of:

100/200/400/600/800/1000/1120/1200

-150-125-75-75-50-50-0-0

And I haven't had any freezing issues. Been using these settings since I first installed GB's kernel way back in mid-january. Also, words with friends wasn't working very well with me either, it ran extremely slow no matter what I did to try and help it along.

MikeyMike01: I was using settings I had used problem free for months, yet it froze frequently. I backed them off a bit, and I still had the occasional lockup.

As for MikeyMike, and the other guy having random lock-ups, I have absolutely no idea. All I know is what I've read from here, and its usually oc/uv.
[Captivate Android Development] sicmadek:
Words with friends freezes on my constantly. It started happening the same day the app updated and i flashed #51 so i dont know which caused it.
[Captivate Android Development] psloan:
i am running #51 with Andromeda. Last charge up for 22 hours with 35% battery left.

1200 1000 800 600 400 200 100

-100 -100 -125 -75-125 125-125
[Captivate Android Development] RonH54:
The 4 recommended Tweaks are the ones that I have been told can't/shouldn't be used on the Final 9.3 of Darky's because of some change they are doing with the ROM. The Final Darky's will only have Voodoo as an option so yes if you plan on using 9.3 Darky you won't be using SpeedMod/SuckerPunch Kernel. Now something may change or there might be some re working on SpeedMod to Match 9.3 Darky I got no clue this is just what I was told.
[Captivate Android Development] nybmx:
That's pretty weird considering that speedmod has been the go to kernel for most darky users. I'm on 9.2 and super happy with it so if what you said is true it looks like I'll be staying with it so I can enjoy suckerpunch. It's just too awesome and existz works super hard to keep the users happy.
[Captivate Android Development] AtoZ0to9:
I can report that I'm running Darky's 9.3B3 with lastest Speedmod with all recommended tweaks enabled, and EXT4 lagfix all around... no problems and blazing fast... don't even see the need to overclock but I do miss the undervolt...
[Captivate Android Development] Tweak4fun:
Several random lockups & FC's on #51 for me as well. I tried with no OC or UV, same results. This also happened with #50. I went to #48 last night...it seemed to work well a week or so ago. So far so good. I'll run it for awhile and see if I get the same good results with #48.