yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] dmshaefe:
Just an update. I had a charge death and I seem to have fixed it by changing the scheduler from bfg to sio and removing all but the recommended kernel options in recovery. Nice job great kernel
[Captivate Android Development] sinichi21:
I think this should be included in the OP maybe just for reference. :D
[Captivate Android Development] shoman94:
My sig below plus I'm OC'd to 1.2 and UV @ -50mv except 100,200,400 is @ -75mv.

Anyways I have never had the wifi issue you speak of. What RoM?
[Captivate Android Development] AReynante:
I'm currently OC'd to 1400, using a little lower UV settings than I usually run, but I was having some issues, and haven't had time to fully test. (So just playing it safe)

1400: -0

1200: -25

1000: -50

800: -100 (Phone likes to camp here, so I still get great battery life)

400: -75

200: -125

100: -150
[Captivate Android Development] jon.groves:
Can anyone tell me why my scheduler defaults to deadline? I change it to cfq in voltage control, and when I reboot, it us back to deadline. Is there a problem with it being at deadline? Let me know what you think.

Sent from Captivate with Serendipity 6.3 and Onix 2.0.3
[Captivate Android Development] shoman94:
Are you Allpying for now?

Are you saving as Boot before exiting?
[Captivate Android Development] jon.groves:
Yes and yes

Sent from Captivate with Serendipity 6.3 and Onix 2.0.3
[Captivate Android Development] topiratiko:
Im on paragon rc6 wich has a diff version of voltage control. Im trying to instal apk in op and it says app not installed. Huh? Help?

Sent from Paragon Blue
[Captivate Android Development] shoman94:
Write down your settings then go into CWM and delete your voltage settings.... reboot and try again.

EDIT:Another question..... Did you also set the system as ext4 along with the normal ext4 lagfix?
[Captivate Android Development] goodolsen:
Uninstall current version first, then install new version.
[Captivate Android Development] goodolsen:
You could also try removing the app and reinstalling. If you had an older version it might have saved a config file in the app folder as well as etc\init.d.
[Captivate Android Development] jon.groves:
Yes

Sent from Captivate with Serendipity 6.3 and Onix 2.0.3
[Captivate Android Development] shoman94:
Just get the latest from the market.
[Captivate Android Development] topiratiko:
Tried. Says signature incorrect?!?

Not signed correctly.

Sent from Paragon Blue
[Captivate Android Development] shoman94:
OK maybe I'm on to something..... did you re-root after changing the system over to ext4?

If not then go into CWM and Root the phone using the simple option.
[Captivate Android Development] shoman94:
Under applications is your unknown sources checked?
[Captivate Android Development] topiratiko:
Yes sir!

Sent from Paragon Blue
[Captivate Android Development] shoman94:
You could try what goodolsen said: But back it up in TiBU first.
[Captivate Android Development] halfsoul:
Uninstall voltage control with TiBu. Reboot. Install voltage control from market.
[Captivate Android Development] topiratiko:
Right away!

Sent from Paragon Blue
[Captivate Android Development] topiratiko:
Cannot uninstall! WTF

Sent from Paragon Blue
[Captivate Android Development] jon.groves:
Actually I just figured it out. Apparently the last time I flashed my ROM, and reloaded my apps with TiBu, I also reloaded RyanZ's OCLF which was setting my scheduler at boot to deadline. I didn't even know it was installed. Thanks for the help! It led me to the issue.

Sent from Captivate with Serendipity 6.3 and Onix 2.0.3
[Captivate Android Development] halfsoul:
1. Reboot & try again.

2. Make sure chuck norris mode is enabled in TiBu preferences
[Captivate Android Development] shoman94:
Excellent!

Did you try uninstalling it through applications? If you still can't you should be able to use supermanager or root explorer etc... and delete the APK then reboot...
[Captivate Android Development] topiratiko:
Chuck norris mode? Lol wtf is that?

Sent from Paragon Blue
[Captivate Android Development] Johnny Paranoid:
It allows the removal of bloatware apps that are part of the system apps (such as clock, calendar, etc.) that would normally cause major problems if you deleted them. Nobody says no to Chuck Norris, not even system apps.
[Captivate Android Development] topiratiko:
Totally screwed now. Deleted and STILL wont install

Sent from Paragon Blue
[Captivate Android Development] existz:
Did you reboot after you uninstalled? After you uninstall it , reboot then re-install
[Captivate Android Development] topiratiko:
NEVERMIND. Reboot handled it. Big thanks to you guys once i hit the desktop.

Sent from Paragon Blue
[Captivate Android Development] bballer182:
I posted this question quite a few pages back and must have gotten lost...

Hey Existz, when using antutu benchmark I have noticed that the database IO scores are pretty low compared to some other phone models. We, as in, captivates are scoring a consistant 30 maybe 40 when everyone else is in the hundreds. Is this problem anything that can be fixed within a kernel or is it just the way our phones are?
[Captivate Android Development] topiratiko:
Good call existz lol thanks again!

Sent from Paragon Blue
[Captivate Android Development] sixstringsg:
Does it work day to day? If so, why does it matter?

Sent from my CM7 powered captivate
[Captivate Android Development] existz:
I say a few extra points might be able to be squeezed, but pretty much that's just the way our phones are..
[Captivate Android Development] shoman94:
I did tell you to reboot...:(

Glad you got it working!:D
[Captivate Android Development] abee_13:
So existz dont know if you need more feedback but after a few more days of testing with the script everything is still running great no COD's,lockups, or reboots.

Sent from my cappy UC'd 900mhz and UV'd running di11is rom/ Onix kernel
[Captivate Android Development] AReynante:
My phone is running very smooth as well (after applying the script). I am not totally sure if my battery is lasting any longer between script/no script, but Onix 2.0.3 in general is longer than any other kernel for me, even with my 1.4 OC.
[Captivate Android Development] topiratiko:
You did shoman. I overlooked cuz i get in these trances when it comes to the cappy....i WILL click yur thanks button for sure!

Sent from Paragon Blue
[Captivate Android Development] bballer182:
Yeah it works day to day. Didn't your phone work day to day before you put CM7 on it? It was a simple little question, geez. I'm not a dev and probably never will be but it was just a though that maybe this area could be improved and make the phone overall run better/faster/smother?!?!?!

Thanks man, Just wondering why we (captivates) are so low on the DB IO's. I don't know much at all about the internal workings of a kernel or the Android OS, so i was just curious if a kernel could cure the low scores on the DB IOs or not. Thanks for the reply!

Love the kernel BTW, it's my favorite so far!!!
[Captivate Android Development] shoman94:
I feel your pain....
[Captivate Android Development] halfsoul:
me too.

Oh well.
[Captivate Android Development] osendott:
My db io is around 170?
[Captivate Android Development] existz:
It might score higher in Antutu, iono...never ran that benchmark (i never use them)..so I really cant comment...maybe 30-40 is really low and the captivate does score higher, like I said ..iono
[Captivate Android Development] pizz0wn3d:
Question, has anyone actually gotten their phone to run at 1.6 stable? I tried enabled it and switched to linpack to see what kind of lulzy MFLOPS I could get and my phone just froze, resulting in a battery pull and a XD face. Just curious. I may give 1.5 a shot later on and see if it stays stable for more than a couple of seconds :P

Could be useful as far as bragging rights go. :)
[Captivate Android Development] johan8:
I think most of us can't run higher than 1.4G.

But it is worth to try, see if you have any luck ;)

For your info, you don't need to pull battery when freezing.

Just hold VolUp+Pwn,

hold these two buttons until phone reboot itself

.
[Captivate Android Development] pizz0wn3d:
Yeah I've used Vol+Power plenty of times, I just wanted to get the phone turned off as soon as possible in case it began to overheat.

I'll give 1.5 a shot and report back in the morning, or at least sometime tomorrow. Right now, however, I've been up wayyy to long and I'm exhausted from the day's efforts.

Herp derp Captivate XDA app.
[Captivate Android Development] aalh:
It had a sleepdeath again last night. I missed some important msgs due to it...

Please Help
[Captivate Android Development] bballer182:
Which tweaks do you have enabled and which kernel? (100hz or 1000hz)
[Captivate Android Development] existz:
Ill have to try a few things, ive been getting it as well..but its been random..2/5 nights. But for me it might still be from the S_cpufreq_tweak.sh, i tweaked it some but it could be the issue...but ill do what I can to reproduce it without the script and then work from there..

When did it first start for you..do you remember? did it not happen with Suckerpunch but started with the first Onix, or did it just start with the last build or 2 of Onix?
[Captivate Android Development] WirelessMike:
Mine started with onix 2.0.2 and happened again on 2.0.3 with default settings.

A shame, too, because it was the best batt uptime and data speeds (always figured that was the modem more than the kernel, but I suppose they both contribute) of anything I've used.
[Captivate Android Development] noside12123:
Whats the difference between suckerpunch and onix? My freind sthodupunuri is too lazy to ask himself -.-
[Captivate Android Development] Johnny Paranoid:
Take a look at the front page/OP of each thread and you'll have your answer.
[Captivate Android Development] existz:
Read the very first line in the OP.. Onix is the original SuckerPunch, just v2 and with new features.. such as Onix recovery, now up to 1.6ghz, cpu threshold tweak..etc..etc

SP-Voodoo is voodoo based...it has voodoo lagfix and color, which is different than Onix. Plus a few more differences .. the differences are in OP of both kernels
[Captivate Android Development] aalh:
I was using SP#58 without issue I think

it started during or just after the first onix I used which was test#6

it has shutdown at widely varied bat levels so it isnt limited to any region of charge

I have had juiceplotter running since SP#55 so I have a good record of previous behavior before and after it started shutting down again, I havent seen any detectable pattern
[Captivate Android Development] goodolsen:
I had it once on 2.0.3, went back to#58 a few days ago and no problems since.
[Captivate Android Development] sthodupunuri:
does this kernel have fugu tweaks capability
[Captivate Android Development] aalh:
yes it works fine with fugu, just like suckerpunch did
[Captivate Android Development] topiratiko:
Loving this kernel! Very smooth very fast. Love the blue recovery.

Sent from Paragon Blue
[Captivate Android Development] shoman94:
Weird... is this a random issue? I have never had that issue....
[Captivate Android Development] harpo1:
Just happened to me for the first time tonght. I have the s_cpufreq_tweak.sh installed everything else is stock. Do I just delete that file and reboot?
[Captivate Android Development] existz:
Yup, just delete and reboot...it will set those settings back to default... let me know if that fixes it for you ..still testing it myself, been on the charger 12hrs now and no charge death, ill leave it on for the rest of the night, then drain it and charge again .. but I haven't had a charge death since I first made this kernel, then started getting them with the script
[Captivate Android Development] harpo1:
I didn't get charge death I had the random shutdown.
[Captivate Android Development] existz:
My bad ... but I also spoke to soon ..just got a CD after 13hrs ...ill move on to the next obvious thing ...the 900 step. Im trying to narrow it down from stuff that was not in Sp 59. So ill see how it goes with disabling the 900 step..if you guys try it without the 900, save VC settings twice, sometimes it wont stick when saving settings ..or best thing to do is save as boot settings and reboot ..that way it for sure sticks
[Captivate Android Development] aalh:
Just had a reboot after unplugging from the charger

Sent from your Id using XDAPremium
[Captivate Android Development] harpo1:
I went ahead and removed the script and 900. I'll report back if I have anymore random shutdowns.
[Captivate Android Development] existz:
It might be something from the newer oc/uv code im using for 1.6ghz since there were quite a few changes in the code...im going to try it with code I used for SP59 and below (will only be up to 1.4ghz then)..ill need to add the cpu threshold sysfs to it, but shouldnt be to hard...ill test it out and if it seems to work, ill put up a test build tomorrow or something for you guys to test
[Captivate Android Development] aalh:
900 has been deselected

and I still got sd and cd

and reboot upon charger disconnect
[Captivate Android Development] AReynante:
I'm one of the few (i suppose) running fine. OC to 1400, script is installed, don't have that performance tweak, no 900/600 step selected.
[Captivate Android Development] rajendra82:
you are not one of the few. I think most are running fine. I am overclocked to 1.4 GHz, have the 600 MHz step enabled, and am running the script to use the battery saving CPU frequency scaling. No lockups here except when I am trying to play with UV to see if I can go a bit lower at a frequency. On normal charging, sleeping, and usage conditions, the phone is as stable as the day it came out of the box stock.
[Captivate Android Development] Johnny Paranoid:
existz,

I've stopped using the cpufreqs tweak, but not because it caused any problems. I didn't notice any problems really of any kind. But I did notice that when some applications were running they were using more CPU (and presumably more battery) than with the tweak not active. Generally it was about a 10%-20% higher load difference. I also didn't notice any real appreciable difference in battery life on the whole. So while it wasn't bad for me, it wasn't really great either. For me, the kernel is fine without it.
[Captivate Android Development] caanda45:
So what is the best way to change or disable the tweaks in the kernel? Is their a disable in cwm? I have alsways enabled never disabled so far? Johnny P what method did you use for the cpu tweak?
[Captivate Android Development] Johnny Paranoid:
It's not in the kernel. It's a CPU frequency tweak script file that you place in /etc/init.d that further tweaks the CPU scaling. Here's a link for it in my dropbox if you want to try it: http://dl.dropbox.com/u/20220118/S_cpufreq_tweak.sh
[Captivate Android Development] shoman94:
I just got it for the first time. Was looking at the weather channel app and I had just plugged it in, Pushed the sleep button. Came back 5 min later and I couldn't wake it up... Had to reboot using power + vol up. No 900, no script tweak, cpu threshold default
[Captivate Android Development] rajendra82:
Isn't that the expected behavior? Wiithout the CPU tweak script, when the CPU utilization reaches. 70%, it would scale to a higher frequency, but with the tweak script in place, it would not scale up until it was being utilized 90%. As a result, you will see the load be higher when doing the same tasks, because the CPU is staying back. Since it is the same number of instructions being executed, but at a lower voltage, which is more appropriate for the lower frequency, power consumption should go down.
[Captivate Android Development] osendott:
All tweaks enabled except the timing tweak and im not using the scaling script. 100hz kernel. Oc/uv etc in signature.

Also 600 and 900 steps uv to -100 working fine. No sd/cd
[Captivate Android Development] geokhentix:
My chip is stable at 1600mhz, and I will say the cpufreqs tweak does a lot of good for me. I do notice that in task managers they use more than normal, but it's also ridiculously easy to see the benefit in battery life against it. I don't have the tweak enabled in CWM, if I do it just owns everything. :o I say any tweak that does things unknowingly to the hardware may or may not cause simple visual bugs, same way that flashing a ROM causes your battery to display out of whack charges. The battery life doesn't reflect the enhanced usage. The explanation given above by rajendra82 is correct. Hz is a measurement of cycles per second, "mega" is the multiplier for a million, while Giga is the multiplier for a billion. Going off of that, let's draw a mental picture.

A graph of sorts if you will, we'll do 800 vs. 1GHz. 1GHz has a higher potential for a maximum amount of cycles per second, so 1GH'z percentage is going to scale a lot smaller, because the processor can theoretically run 1 billion cycles per second as opposed to 800 million, so if we broke them down into 1-hz chunks and line them up, 1GHz will cover more ground than 800MHz. Saying that, 50% of 1GHz(500MHz!) is roughly 62% of 800MHz. Therefore, the CPU is obviously going to display a higher load, butttt...lower frequency = lower voltage, which is apparently good for the purple drank (juice) :p
[Captivate Android Development] 13_:
Ok, after a few days messing about....

I Had random shut downs (no charge death) and was about to take my phone back for replacement. Before taking it in I decided to change it up just to see what would happen and this is what I found out on my device, which may or may not be similar on other devices.

The random power offs and freezes occurred at any OC for me at or above 1.2Ghz

The scripts enabled or disabled. Had power off or freeze sooner/more often with cpu tweak on, mem timings did not seem to affect. At 1.2 it seemed stable ... but found that I still had the power off problem, happening at totally random times and levels of use.

Went back to SP#58. OC'd to 1.3Ghz. All fine.... but this led me to my next discovery......

Installed Cordy from market and found it will NOT play/run with SP/Onix at least with any OC ( didnt test at 1000, but did at 1.1,1.2,1.3 on SP#56,58,59,Onix/all)

So in an effort to test the Cordy issue I switched kernels... Used paragon. Found Cordy problem to be present for me with Paragon 1280. Found Cordy to work however with Paragon 1200. Also @ Paragon 1200, the random power offs are gone.

The only big thing I see is the unlocked fps in SP/Onix. Is it possible that is causing issues with Cordy. The other reason is because maybe the OC is unstable but ever so slightly so.

I have not used any of the recent scripts unless they were in Onix recovery.

Atm I'm still on Paragon 1200, lol, gonna give my phone some rest... but will be back for some Onix in a bit :cool: It is the smoothest, quickest responding kernel I have used, just these recent issues, and the Cordy thing.

tl:dr

Onix cause random boots/power off with OC

SP/Onix will not run cordy w/OC (not test @ 1000)

My phone is not broke

Tweaks work, good/bad idunno, seem good
[Captivate Android Development] H3llstorm:
Anyone else still have the Wifi bug?
[Captivate Android Development] Johnny Paranoid:
Well you guys all make an excellent point. I guess I'm just going to have to give it a day or so w/o the CPU frequency tweak and see what my battery looks like then. Also: I don't know what the problem you're all having with Cordy is (FC or won't load at all), but my phone is OC'd to 1.2Ghz and UV'd -75mV each step and Cordy runs fine for a while (although a bit laggy and definitely skipping frames) and then FC's on me. At 1Ghz (still UV'd) it's still laggy but otherwise runs fine. At 1.2Ghz, no UV it runs ok (still laggy and skipping frames) but no FC. At 1Ghz, no UV it runs fine (just a tad of lag) exactly as it did when I was using SP #58 and SP-Voodoo #8. Another thing of note, ever since I got it and no matter what my settings are, Cordy gives me the 1 vibrate; pause; 2 vibrates of a force close when I exit the app. It doesn't do anything other than vibrate like a FC and nothing happens on screen. Anybody else experience this?
[Captivate Android Development] existz:
I think you guys are talking about 2 different cpu tweaks ...there's the cpu threshold tweak in recovery and then there's a cpufreq_tweaks script I posted awhile back for a few to test. ..with the cpu threshold tweak, you are correct, but the cpufreq_tweaks script, it adjust the time the cpu checks the threshold and it adjust the percentage of max clock the cpu scales.
[Captivate Android Development] Delicate Donut:
I can play cordy fine on onix 2.0.1. OC'd to 1.2
[Captivate Android Development] theMaDHakkeR:
Fixed.. Ignor this.
[Captivate Android Development] elghouchd:
Oh nooo, everytime i boot up my phone every app i have force closes, and then my phone hangs up then restarts!!! aaah, then this whole process starts all over. I tried Odin but it kept saying failed (ive used odin 3 times before) and i tried wiping and did factory reset from the recovery, but nothing works!! somebody help PLEASEEEEE!!?!?! Thank you!
[Captivate Android Development] rajendra82:
You are right. I wasn't thinking about that. But now to think of it, wouldn't the frequency tweak also make the CPU hold back more when enabled?
[Captivate Android Development] pizz0wn3d:
Did you restore system settings from TiBu? if you did, then that's probably what's causing it.

Herp derp Captivate XDA app.
[Captivate Android Development] elghouchd:
Well no i didnt, but do you know anyway i can fix this?
[Captivate Android Development] LNJ:
Try reflashing and then restoring again but only do missing apps.
[Captivate Android Development] VFO:
Any update on the sleep death issue? I love this Kernal but the shutdowns are happening more frequent for me. So far I have tried all the suggestions in the thread but it is still happening.
[Captivate Android Development] existz:
Its getting there...taking awhile to test different situations, so far ive yet to have one, but i still need to drain battery and try a full charge, seems for me thats when it happens the most...to be honest im not sure what caused it to start happening with Onix and not SP #59.. but im working on it
[Captivate Android Development] VFO:
Thanks for the update. For me it seems to be very random and at different charge levels. Some days I may have one during the whole day and others like today I have one right after the other. Sometimes it happens right after I lock the screen and then try to unlock within a minute after it closes. I can see why the trouble shooting can be difficult. Other than that this is the best Kernel I have used. I have been using your kernels since SP#57 and they are by far top performers.
[Captivate Android Development] osendott:
Theres a sleep death issue? I know with sp 56-58 i had troubles, had to go back to paragon, but onix has been flawless since release.
[Captivate Android Development] existz:
Yea for some...seems its not happening to everyone and its random..I can have it one night, then for the next 3 nights its fine..then ill get another one out of no where...so thats making it harder for me to narrow it down..
[Captivate Android Development] H3llstorm:
I haven't had any sleep death issues, but I'm having issues connecting when turning on Wifi.
[Captivate Android Development] existz:
No problems here... try rebooting your router..also clear cache/dalvik cache..
[Captivate Android Development] Seanbest:
This kernel is running great so far for me.
[Captivate Android Development] aalh:
I am running Soft Locker till we come up with something else to try fixing the SD's with

I also reenabled 1200 and 1300, but am leaving the Threshold tweak off

my bat life isnt happy, but I dont miss calls