yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] cumanzor:
What is VSF?

I'm trying out 1400 with different UV settings, following a post in the previous page I think. I tried yesterday (during class... :p) 1400, but it crashed while playing Angry Birds with a weird graphical glitch. Same thing happened with 1360.

What bothers me know is that I'm getting the exact same Linpack score of 15. 1400 checked and selected as the limit... and obviously applied... :confused:
[Captivate Android Development] existz:
VSF= Variable Screen Frequency ... its actually a good idea, and everything is user configrable via scripts, you can set your max screen frequency (stock is 60hz) and then the min screen frequency. Without VSF, it runs 60hz all the time, with VSF, you can choose to have the screen frequency lower based on variable things, like after x amount of milliseconds and if the cpu drops below xxxmhz, the way mine is right now (still fine tuning it) my max screen freq is 45hz and after 100ms / under 800mhz it drops to 35hz. You can also set the color gain via script, during max freq mine is 256 256 256 , during low freq its 240 256 256. Its hard to explain, its like the screen gets darker without actually getting darker... VSF is still in kind of early development and I think after some tuning, its gonna be awesome. It will probley be awhile before I release my version of it, I might have an open beta via my IRC channel, It probably wont be for awhile, ill still continue to work on SuckerPunch-SmR daily, it will be my #1 priority ..so just check this thread after awhile on info for the new version
[Captivate Android Development] cumanzor:
^ cool. I assume this is good for battery life?
[Captivate Android Development] existz:
Yea, it should really help. With VSF it can kinda be annoying, with the screen switching so often, that's why I want to try and find the best middle ground so its not such a drastic change in the screen when switching. It kind of reminds you of auto brightness going wild, with it at 60/25 its a pretty good jump, with 45/35 its not near as bad, just looks like its just dimming some when not touching the screen after so many milliseconds / set min cpu freq, then when u touch the screen it goes back to max freq setting, but all of this is configurable via startup scripts
[Captivate Android Development] lrs421:
For those of us who aren't quite familiar with VSF will there be an auto option or a way to disable it all together? Gives us a little time to familiarize ourselves with it.
[Captivate Android Development] existz:
Yep, if you don't want to use VSF simply drop a script (ill provide scripts to dload) in /etc/init.d , there will be scripts to set color gain, set min/max screen freq and a script to disable vsf.
[Captivate Android Development] cumanzor:
Would be cool to make an app that allows you to enable/disable these scripts easily. Hey I'm learning Android programming maybe I can help at some point :p

(or an option in CWM, that I can't help you with).
[Captivate Android Development] existz:
*UPDATE*

Build #34

hpcall fixed (actually works this time)

Its been verifed by about 5 different people that hpcall works this time, lol sorry for taking so long to get it to work
[Captivate Android Development] existz:
Yea an app or widget to enable/disable would be good...what i do is use gscript (best app ever) and add in my script, then you can set a widget for gscript for that script, only bad thing is you have to have a gscript widget for on and one for off...
[Captivate Android Development] crazililazn:
Woah, build 34 made my phone unstable x.x my settings were perfectly stable on build 32, but once I flash build 34, my phone is crashing when I watch videos and browse the web. Both never happened on build 32 with the same settings x.x

EDIT: switched back to build 32, and everything is stable again.

Sent from.... Waiting for Location....
[Captivate Android Development] RonH54:
I am sure this posted somewhere but why is it recommended to enable LagFix with this Kernel?
[Captivate Android Development] existz:
I prefer ext4 over RFS, its faster, doesnt use any more battery than rfs, if anything it could be better on battery, The kernel is actually tweaked for ext4, some of the tweaks in cwm only effect ext4, Samsung must of had a reason to ditch RFS seeing how the Nexus S only uses ext4... its not really if you should or should not have a lagfix, its using a better file system all together, you might not have lag, but still i recommend ext4 over rfs
[Captivate Android Development] RonH54:
Thanks for reply. I have always used ext4 I was just wondering for own info.
[Captivate Android Development] lrs421:
34 is just as smooth and stable as 32 for me.
[Captivate Android Development] xreflection:
So why does this kernel have the charge death, but the original speedmod kernel doesn't even though this one is based on speedmod?
[Captivate Android Development] RonH54:
Ok I am getting ready to try 34. Yesterday when I went from 26 to 27 I had problems with Voltage App which was easy to correct but I was wondering should I do anything in Voltage App settings prior to Flashing new Version of this Kernel?
[Captivate Android Development] LimaI896:
Hey existz can I just keep the update from yesterday or did you do more changes?
[Captivate Android Development] LimaI896:
Did you UV? Try deleting you s_volt_schedule and flash again. Should be stable again.
[Captivate Android Development] existz:
Cause the charge death is related to oc/uv ... glitterball says in his OP that the problem was in the uv code. I've tried about everything I know to fix it, but since I don't get charge death its hard for me to find the problem. So im gonna have to wait till he or someone else can tell me what the problem is
[Captivate Android Development] existz:
The test version I had you try for hpcall is the same as this, no need to change, version numbers might be off, so don't pay attention to that
[Captivate Android Development] sixstringsg:
Earlier I had charge death, but when I decreased my uv settings on the low end it went away.
[Captivate Android Development] RonH54:
I got 34 Flash but at the moment I am going to set Limit at 1280. Since I am doing this do I need to fool with Voltage settings on 1360 and 1400?
[Captivate Android Development] TRusselo:
i just flashed to #34 and can NOT get to run stable limited to 1000mhz no o/c no u/v. (STOCK basically)

cant get to run stable with o/c u/v either

it will fail stabilitytest in under 5 tests everytime. tested over and over for an hour always failing quickly.

testing #32 now at max 1000 no u/v. surpassed #34 already still going...

thats not right...
[Captivate Android Development] RonH54:
I have question about the Stability Test App. One time it did Fail and I got the Error message that my phone might be unstable. I make some adjustments and Start test again and after a few test Passes the App shuts down but No error message. Does this shut down also indicate a Failure and I need to make more changes?

Thanks
[Captivate Android Development] MexicanAmerican:
Quick question, and forgive me for displaying my newbie ignorance:

What's hpcall? I've attempted looking it up, but if the answer is out there, I missed it. Most of the posts just cite that hpcall is fixed, but never explains what hpcall is.

Obviously I haven't a use for it since I don't even know what it is, but I'd like to know.

Also, I got charge death with Build #32, so reverted back to #31 and all is well.
[Captivate Android Development] RonH54:
Never mind I found shaolin95 OC/UV Post and it seems if it does Crash to Homescreen I need to make adjustments.
[Captivate Android Development] sixstringsg:
If it doesn't lock up on you during day to day tests, Stability Test is irrelevant.

Calling while headphones are plugged in.
[Captivate Android Development] TRusselo:
read back couple pages.. it has to do with the plug-in headset and calls.
[Captivate Android Development] TRusselo:
it says in OP :
[Captivate Android Development] existz:
With hpcall, its pretty cool cause you don't need headphones with a mic now, you can have regular headphones on and the caller comes through the headphones and you use the phone mic, like a regular call but sound comes through headphones when plugged in
[Captivate Android Development] MexicanAmerican:
Thanks for the clarification. Hpcall seems to work fine on my phone using Build 31. No charge death, either, and stable. Great work, existz.
[Captivate Android Development] MexicanAmerican:
Nevermind about hpcall working on Build 31. The mic doesn't work with the headphones plugged in. I guess that's the bug, huh? Not a big deal, though. Thanks for the help, folks.
[Captivate Android Development] MexicanAmerican:
Another question for you helpful folks out there:

Is there an archive where all the past builds are located? I see that when new builds are posted, existz removes the prior build download links. Thanks in advance.
[Captivate Android Development] existz:
I use to keep my previous builds on my server, but started deleting them, I will look and see if I happened to leave any on there, bit I will start to keep old builds up and post a link to them .. also I might have some older ones on my phone if I do I will check and see, if so ill also post em up with a link

EDIT

I checked and I have #24-25 (1120/1280 100hz and 500hz) and #26-27 (1120/1280 100hz and 500hz) and #32, ill post em after while and post a link, ill look for the others and see if I have them

As for hpcall, up to build #31 I believe it didn't work, build #32 I thought I fixed it but it wasn't, finally fixed it on new #34
[Captivate Android Development] MexicanAmerican:
Thanks, existz. Don't put yourself out, though. I was just curious. I can always go back to Build 31 if things don't work out with subsequent builds. I know you spend a ton of time working on this project for the benefit of the community, and it's much appreciated. Don't want to add yet another thing to your already full plate.
[Captivate Android Development] sjavvaji:
im still completely aghast by how long my battery lasts even on 1.4ghz...it might be because the phone still downclocks to the uv'ed 100mhz to 200mhz when sleeping...if u move to the new base can u please make sure it has same or better battery life than our speedmod base
[Captivate Android Development] existz:
Oh yea, if its not as good I wont replace this one with it. If battery is not as good, ill probably make it like a XT version for those that want speed over battery, than keep this one for ppl like me who want best possible battery ... for me I get more than enough performance with 1.12ghz so battery life is most important and always will be
[Captivate Android Development] Loggik:
I know that this is based off of the SpeedMod kernel, but does this have supercuriou's Sharpness fix? I didn't see it listed in the features list...
[Captivate Android Development] Nickel Dime Bay:
i set the max clock to 1.4 but was getting like 13 and 14 in linpack (yes i know it means nothing) shouldnt it be in the 18 or 19's?

#32 btw
[Captivate Android Development] existz:
Did you make sure the states was enabled in VC (not the max clock) cause if the frequency is not set to active, setting just the max clock will not do anything, since the frequency is not enabled (and yes you should be getting 17-18-19 in linpack, anytime you get 12-13-14 after a few runs it usually means its still at lower speeds)
[Captivate Android Development] existz:
Im not sure if Hardcore used supercurios sharpness and just tweaked it or if he used just his own settings since in his thread it says inspired by supercurio sharpness...either way it has a sharpness fix
[Captivate Android Development] Nickel Dime Bay:
No I didn't im not sure how to activate the states, I've never had to do this before so im clueless on this one.
[Captivate Android Development] r3ferrei:
In the voltage control app its the bottom middle button. Check off the states you want to enable. Also make sure you read the disclaimer at the bottom.
[Captivate Android Development] lrs421:
At the bottom of the app click the states button and select the desired frequencies.
[Captivate Android Development] WickedNite:
At the botton of Voltage Control there is a States option that you need to drag up to see the states. Check what state you want.

Sent from my Muscles using Brain Cells
[Captivate Android Development] evrionis:
In this build #34 release, which version of speedmon was this version started with?
[Captivate Android Development] existz:
The actual source is built off of K12P, which has since been updated by me
[Captivate Android Development] evrionis:
Ok thanks, I would have thought you would have taken the lastest K12s or t versions. No worries.
[Captivate Android Development] existz:
I thought about updating, but i will have to play with Hardcores own sound/video tweaks since the newer releases and see if I like them or not, other than that it has basically the same things
[Captivate Android Development] evrionis:
no problem, I luv the kernel anyway.
[Captivate Android Development] evrionis:
Hey existz's !

Is it easy to enable the ability to OC one of speedmon's standard kernel's? How would you do it?
[Captivate Android Development] RonH54:
For the guys on 34 using 1400 or 1360 as Max, what other States do you recommend? Or does it really matter?

Thanks
[Captivate Android Development] existz:
Hardcores does not support oc, that's the purpose of this kernel
[Captivate Android Development] ccdoggy:
Just wanted to pop in with some experience with the kernel after a few days. I finally got my battery drain found as it looks like my cell data was never turning off and was draining my battery pretty quick. I used to be at 20% by about 9:00 pm, now that i am using an app to turn it off when wifi is on its 9:33 right now and am at 62% and the drop of 10% is only because I was using it for GPS directions.

the battery life is fantastic! thank you so much for putting so much effort into developing a battery focused kernel.
[Captivate Android Development] iXNyNe:
Reporting on 100 vs 500 - just tried 500 for the first time bandit burned up battery like a beast. Back on 100 now

Also just to mention this is on #34 for both. Haven't yet tested #34 @ 100 but all my previous flashes were on 100 and battery life was excellent
[Captivate Android Development] sicmadek:
how do you know if its 100 or not? in the op there is a #34 zip and a #34 500 zip. is the #34 the 100?
[Captivate Android Development] :
does anybody have suckerpunch#26 download link please?

cheers :)
[Captivate Android Development] mrbloog:
At 1.4Ghz my phone crashes on 3d games, so I guess I'm stuck with 1.36Ghz.

Edit: X-Plane was crashing at 1.36, so now down to 1.28. Can anyone tell me what the problem is?
[Captivate Android Development] :
Not all chips overclock the same

Just be satisfied that you can even overclock:p

Swyped from my captivate
[Captivate Android Development] meridianblade:
FYI, I just flashed to the latest phoenix 4.5 and then flashed to #34 here and the phone kept crashing on boot. Earlier versions didn't do this. Has anyone else experienced this?
[Captivate Android Development] neffarious:
I love the kernel hate the charge death. I never got charge death with any of the other kernels that were prone to it. Sucker Punch is my charge death kryptonite :(
[Captivate Android Development] LimaI896:
Im sure he will have it fixed soon enough.

Im just excited for 900/600 voltage.
[Captivate Android Development] neffarious:
I hope so :) Its got everything you could want, except the Charge issue ;)
[Captivate Android Development] RonH54:
I have been tweaking #34. Phone been stable so far and I have run all kinds of Tests and nothing failed except I had NenaMark Freeze my phone and I had to remove battery and reboot. I assume I need to increase Voltage somewhere? Like I said this the only Test that caused any problems.
[Captivate Android Development] ryude:
Which one? 100HZ or 500HZ?
[Captivate Android Development] iXNyNe:
Yes. The one that just says 34 is the 100
[Captivate Android Development] ryude:
The 100HZ has been giving me a lot of trouble, 500HZ is flawless though.
[Captivate Android Development] slider2828:
Agreed the 100 freezes on heavy operations it looks like... Sucks... This really does save a noticeable amount of battery power though. Where can I edit the volt table on this kernel or is it rom specific for the volt table? thanks!
[Captivate Android Development] ryude:
Xan's Voltage Control app is what lets you control the voltage table.
[Captivate Android Development] capita:
Same here. Another incident this morning. I rely on m phone as my alarm as well, so I can't use this atm. Love the kernel though.

Hopefully it all gets worked out. In the meantime I guess its back to speedmod.
[Captivate Android Development] ryude:
Just had charge death :(

#34 500HZ
[Captivate Android Development] cumanzor:
I haven't had any charge death so far (been since rel#26). I do use Sleep as an Droid, so maybe keeping the phone "active" while charging avoids this issue. (which could possibly mean a problem with lower frequencies on certain UV settings while being on AC power??)
[Captivate Android Development] ryude:
I'm beginning to think it's a problem with the lower frequencies period, it never does this while active.
[Captivate Android Development] cumanzor:
But does it die when it's inactive but no plugged in to AC?
[Captivate Android Development] slider2828:
Nah Xan's voltage allows you to control the volt table, but first I believe you need entries for the given frequencies first and then it gets overrided by VC....
[Captivate Android Development] slider2828:
Possibly lower voltages are UC'ed too much?
[Captivate Android Development] sixstringsg:
At 100, 200, and 400 I'm running -50 and getting no charge death. I did earlier when I undervolted more.
[Captivate Android Development] capita:
I was running -50 at the 100 and 200 steps and -75 on 400.....charge death this morning. I guess I'll try bumping everything down a notch to see if that helps.
[Captivate Android Development] LimaI896:
Going to try out this theory as I didnt get one either today while having a less aggressive UV.
[Captivate Android Development] sicmadek:
I havent had any problems with the 100hz so far
[Captivate Android Development] WickedNite:
Yep, me too. Running 100hz since the 1st release and had no problems.
[Captivate Android Development] sjavvaji:
great...no charge death after the move to xan's (lower ur uv on 100mhz and 200mhz if u have it)

Doc's YWJS3 Base

scheduler: cfq

batch: 1009

1400: 0

1200:50

1000:125

800: 125

400:125

200: 100

100: 100
[Captivate Android Development] opcow:
I've never had the charge shutdown with this kernel, but I haven't had the phone on the AC charger in weeks (I just use USB).
[Captivate Android Development] slider2828:
Run some nenmark OC'ing your phone to 1280... Let me know if it is stable and what the FPS is....
[Captivate Android Development] slider2828:
Hey existz... maybe you can answer this. I flashed your #34 kernel and for some reason in VC I get ? next to the freq's above 1200...

Can you help?
[Captivate Android Development] pizz0wn3d:
I think you're talking about about the voltage frequencies? They don't show up. I was actually just about to ask what the voltages for the higher frequencies were. I can't seem to find them on the op

Herp derp Captivate XDA App
[Captivate Android Development] silverslotcar:
Correct me if I am wrong, but I think 1200 and 1280 run at stock voltage the same as 1000hz
[Captivate Android Development] existz:
according to xans thread on VC, i think he has only added what should show up, up to 1120, so anything above 1200 will show ?
[Captivate Android Development] meridianblade:
I flashed the 500HZ version
[Captivate Android Development] slider2828:
I think it needs to be detected in a file. I remember setiron's kernel didn't have this issue
[Captivate Android Development] meridianblade:
Tried flashing the 100HZ version as well and still locks the phone up. This is coming from a flashed to stock, master cleared, flashed to Phoenix 4.5 clean rom... Any ideas? I really want UV :-(
[Captivate Android Development] slider2828:
Try deleting all the volt files in your /etc/init.d directory? Maybe Firebird writes something in there. else.... maybe not compat with this kernel
[Captivate Android Development] silverslotcar:
If the S_volt_scheduler file was still present in system\etc\init.d that would just cause the Voltage Control App to have problems. It wouldn't keep his phone from booting though.
[Captivate Android Development] meridianblade:
Phoenix 4.5 ships with speedmod kernel so that shouldn't be causing it.. Also I don't have a S_volt_scheduler in /etc/init.d/.

I'm going to try disabling all tweaks and lagfixes, then flash the kernel, then flash SuckerPunch and re enable it that way.

I didn't have a problem flashing to SP #32 from speedmod with lagfix enabled before, so im trying this to see if it works...

Any other ideas?
[Captivate Android Development] froli13:
Never had charging death with these settings:

Scheduler: Noop

1200Mhz - 50mV
1120Mhz - 50mV
1000Mhz - 0mV
800Mhz - 100mV
400Mhz - 125mV
200Mhz - 125mV
100Mhz - 125mV
[Captivate Android Development] meridianblade:
Existz, I narrowed it down to the kernel scheduler tweak that's causing my phone to lockup on boot. This happens when it starts to do a media scan on the sd cards
[Captivate Android Development] goob1284:
Idk why, but this kernal seems more laggy than setirons. I have the 500 oc with 1.4. Sane settings except the 500 oc
[Captivate Android Development] silverslotcar:
When I was running this kernel, I had almost those exact same settings, but I still had charger death constantly. It just varies with your device.
[Captivate Android Development] lpsi2000:
Xans app detects it on other kernels, so I don't think that is the issue.
[Captivate Android Development] existz:
Most of the other kernels (glitterball, setiron) use faster mount options and other settings, I didn't optimize this kernel for speed, but for battery life. But, this kernel shouldn't be laggy, you can try setting the mount options to FASTER instead of safe in recovery, and make sure you have the tweaks enabled via recovery, that should help also...

And another note, I usually keep 1,3,4 of the kernel tweaks enabled in recovery, but I got my first charge death yet after enabling the Kernel VM tweak. I've been using the same build for about 2 days, #35, and have had probably 3-4 full charges and only got a charge death after enabling this. Now it might have been random, but I im going to test this further, for those of you that's always had charge death, which of the first 4 tweaks in recovery are you using? You can check /etc/tweaks.conf to see without rebooting...if you don't have any selected you probably wont have this file..or its blank. It might not be anything, but its what caused it for me.
[Captivate Android Development] froli13:
I know, but it's always worthy to try something that works for some users.
[Captivate Android Development] existz:
I really don't know then, just assumed since he says he has only added voltages up to 1120 in his OP, either way its no big deal, not going to effect anything
[Captivate Android Development] capita:
I've been running with all tweaks on, and getting charge death on just about every build from #30 up. I'll try turning off the kernel VM tonight.
[Captivate Android Development] WickedNite:
I changed the default setting on my lagfix, it says ext4nj so I changed it to ext4. What's the difference btw?

Sent from my Muscles using Brain Cells
[Captivate Android Development] silverslotcar:
Search for ext4 no journaling

sent from my SGH-I897 running whatever rom is fresh with HC's k12t kernel and the kp1 modem!!
[Captivate Android Development] existz:
It should only be on the cache partition, which doesn't require it to be as stable as system, hence you can clear the cache partition via cwm with no problems, having it set as ext4nj it doesnt use as much space since there is no journal allowing you to download larger apps via market. I wouldn't use ext4nj on system or data because its more likely to get corrupted , but its perfectly safe on cache partition