yashsingh1/xdaforums huggingface dataset:
[Captivate Themes and Apps] arffer:
Missing 'Interactive'

I just installed CF 3.5b on my phone, which is running Talon T20.

In the scaling governor, 'Interactive' is not listed as a choice. Even though I believe Talon's default setting is 'InteractiveX', CF is showing 'ondemand' as the currently selected choice.

Ideas or suggestions?
[Captivate Themes and Apps] shane87:
Well, can you get some info for me? Get a terminal emulator. If you don't have one, search the android market for "terminal emulator" and get one. In the terminal emulator, type the following and post back to tell me what it says.

"cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors"

"cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor"

Like I said, just post back in here with what those two commands return, and I will take a look into what is going on.

ROM: Perception II beta 3

Kernel: TalonDEV 0.1.4, Voodoo Sound v8, Voodoo Color, CFRoot ext4

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] aalh:
no interactive on t20 for me either

maybe it was removed from t20

that is why he doesnt release the test kernels

things are changed a lot

phone is fine without it (i use ondemand), I am playing with the lmk.conf settings now(Talon stuff)

Ondemand was the choice for all existz kernels before interactive came about
[Captivate Themes and Apps] shane87:
Hmm, not sure. I will send ex a pm here in a little bit and see if he removed it in t20. Untill then, I have no ideas, as I am still running 0.1.4.

ROM: Perception II beta 3

Kernel: TalonDEV 0.1.4, Voodoo Sound v8, Voodoo Color, CFRoot ext4

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] shane87:
Ok, so existz just confirmed, interactive WAS removed from t20. So not seeing interactive in cf on t20 is NORMAL!

ROM: Perception II beta 3

Kernel: TalonDEV 0.1.4, Voodoo Sound v8, Voodoo Color, CFRoot ext4

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] arffer:
Thanks! Mystery solved!
[Captivate Themes and Apps] shane87:
Ok, so I have been quiet on cf for a little while, but I am getting close to a new release. Me and aalh are currently testing a private build, and if all stays well for the next day or two, I will be putting it up as cf 0.4b. I have added logging capability, and deep sleep tis, along with tis percentages. Check back in a couple days for the release (hopefully!)

ROM: Perception II beta 3

Kernel: TalonDEV 0.1.4, Voodoo Sound v8, Voodoo Color, CFRoot ext4

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] j_bravo14:
Does this add any overhead on the scheduler?
[Captivate Themes and Apps] shane87:
Not really. All of the tis percentages are simply figured from the tis info all ready being loaded at start up, and the logging only records the raw system values as they are loaded, so it does affect start up. However, the difference is negligible.

ROM: Perception II beta 3

Kernel: TalonDEV 0.1.4, Voodoo Sound v8, Voodoo Color, CFRoot ext4

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] shane87:
Update!!

Control Freak 0.4b is LIVE!!

Changes:

- Added Deep Sleep TIS, and TIS percentages.

- Added logging of all major start up values as they are polled from sysfs.

See the OP to find the download link, and the full changelog.

As always, if you want to see Control Freak receive more new features, please consider donating! Your donations help immeasurably, and along with my passion for writing software ensure that I continue to develop!
[Captivate Themes and Apps] aalh:
to clarify, (I think)

you refer to start up of the app, NOT phone start up:D
[Captivate Themes and Apps] shane87:
Yeah, sorry if I confused anybody. I was reffering to the start up of ControlFreak, not the phone start up! For future refference, if I say start up, I am generally talking about an app launch. If I am talking about the phone start up, I will say "boot."

ROM: Perception II beta 3

Kernel: TalonDEV 0.1.4, Voodoo Sound v8, Voodoo Color, CFRoot ext4

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] CuriousTech:
I'm running TalonDEV 0.2.1 now and the max CPU freq is blank. No options. The UV list is correct though, going to 1200 and saves fine. I'm running BusyBox 1.19.0 which came with Continuum. That's probably it right? It's kind of strange that some parts work and some don't though.
[Captivate Themes and Apps] aalh:
yes, use 1.17.x

though that is usually the cause of setting not saving

I have not used 1.19 in GB speak from experience on the list not displaying

but after you downgrade BB to 1.17 just restart the app if it doesnt act right, that may fix it;)
[Captivate Themes and Apps] CuriousTech:
Nope. 1.17.1 didn't fix it. The Voltage Control that comes with Continuum works with both 1.18.x and 1.17.x though and it looks a lot like Control Freak now. :) It doesn't have TIS or Governer though.
[Captivate Themes and Apps] shane87:
Hmm, that is very odd. I have never seen problems usng bb 1.17.1. And I am running continuum 5.5 with existz's talon 0.2.1. I will look into it, but if I can't reproduce the problem, I don't know how much I can do.

ROM: Perception II beta 3

Kernel: TalonDEV 0.1.4, Voodoo Sound v8, Voodoo Color, CFRoot ext4

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] CuriousTech:
Well, I seem to be the only one experiencing it so it might not be worth messing with.

I just noticed Voltage Control had the states tab. It wasn't there when I had bb 1.19 on it. That's why it looked like yours. LOL
[Captivate Themes and Apps] shane87:
Hmm, if vc is pulling the states enabled tab, cf SHOULD be showing the available clock limits. The reason that cf is not showing the clock limits is due to it not being able to read what states are enabled. Since cf only shows enabled states in the clock limit dropdown, when it can't read the states enabled it won't show any clock limits. However, if vc is showing the states tab, it is reading the states enabled, so I am not sure as to why vc can read the states enabled and cf can't. Unless xan changed his sysfs polling code, his should work basically like mine.

All I know is that these phones rarely do what you think they will!

ROM: Perception II beta 3

Kernel: TalonDEV 0.1.4, Voodoo Sound v8, Voodoo Color, CFRoot ext4

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] CuriousTech:
Well, this might make more sense. I ran vc 40 times and it only showed the states once, so at least the two apps are doing what's expected. I guess I just ran it at the right time before.
[Captivate Themes and Apps] alexige:
If it would be possible to add in a way to reset the TIS without having to restart that'd be a nice little addition.
[Captivate Themes and Apps] shane87:
@CuriousTech - That is how vc has been on gb. It works once in a blue moon. On cf, I thought I had fixed it by switching to an asynctask start up function. However, I do still see the occasional start up when cf won't pull states enabled. It doesn't happen often, maybe once or twice per release, but restarting cf always fixes it for me.

@alexgie - I am planning on adding tis reset. However, I have other features that I feel are more important to add first, such as governor specific tweaks.

[EDIT]@CuriousTech - If you want, run Control Freak again. If it still does not show any options in the clock limit dropdown, do me a favor and export the log. Click menu > export log. Then send me /sdcard/cf.log @ eric.clothier@gmail.com and I will take a look at the log to see if I can pinpoint what is going on.[/EDIT]

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] CuriousTech:
Alrighty. Sent it. Send me anything and I'll run it and send debug logs back.

It could just be something goofy about this ROM flash. It's the first time I had to flash anything twice. The first time the phone wouldn't hang up, lagged, wouldn't dail, and other things strange things.
[Captivate Themes and Apps] shane87:
Ok, so I just took a look at your cf.log, and I see the problem immediately. Control Freak

IS

pulling states enabled. However, all of your states are disabled for some some reason, as evidenced by the line

ControlFreak @ 1307097875421: statesEnabledTemp val: 0 0 0 0 0 0

To fix it, simply launch CF, and open each state like you are going to edit the uv value, and check the check box. The check boxes enable/disable the states, so if you check all of the check boxes, then hit menu > apply settings and menu > save as boot settings, that will allow CF to read the states enabled values correctly.

If enabling the states does not work, and you still have issues, export the log again and send it back to me so I can take a look at what may be causing it.
[Captivate Themes and Apps] CuriousTech:
Ah, that would make sense. Thanks. I think I used VC the first time before installing anything so it failed to read the states and wrote zeros.

Here's S_volt_scheduler

echo "0 0 0 0 0 0 " > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

The phone's actually been running nicely. Checked every state and now it's:

echo "1 1 1 1 1 1 0 " > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

Notice the 6 states, now 7 with the last one 0.
[Captivate Themes and Apps] shane87:
Yeah. Hmm, that last state with a zero worries me. I know why it is there, but I didn't think about it til now. Where I added the deep sleep read out, it is getting treated like another state. Hence the extra zero. I don't think it will cause any ill effects, but my next release will make sure that no setting for deep sleep will manage to get written to file anywhere.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] CuriousTech:
Yeah, that's what I assumed. It's a very common mistake, at least for me, to add a special case in a list and miss adding conditional code somewhere. I'm showing 96% deep sleep from last night so it still works, but battery life was bad so I deleted the extra 0 and rebooted so I can see if it improves.
[Captivate Themes and Apps] shane87:
Yeah, I know what you mean. I added the conditional code to keep it from giving any controls to deep sleep, just forgot about tye minor fact of it trying to apply settings to deep sleep, lol. As far as battery life, mine has been pretty good so far. Of course, I have tweaked my ondemand governor a little, so I am not sure how much that has an effect on it. If anything, my tweak should cause slightly lower battery life, but better performance. I now have ondemand throttling up at 70 percent load instead of 95 percent load. And that is the next feature on my list, governor specific tweaks. But first I need to talk to ex and get some recommendations on the values for the tweaks, and possible side effects. Anyway, I hope things start working better for you.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] shane87:
Just did some checking on my phone, and the extra zero in s volt scheduler on states enabled shouldn't cause any side effects, since the states enabled table will only accept as many inputs as it has states. On my phone, my s voly scheduler echos 1 1 1 1 1 1 0 to the states enabled file, yet the states enabled file only shows 1 1 1 1 1 1. So obviously the kernel is smart enough to truncate any extra states that do not exist. Of course, I will still fix the s volt scheduler, since I hate dirty code, but for now it should be fine.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] CuriousTech:
I didn't notice any problems either. I'm surprised it worked with all the states disabled. Battery life was actually better and it wasn't stuck at 100MHz. Quadrant scores were only slightly lower and it ran smooth. Kinda strange.

Edit: Something else interesting. I've had 2 random reboots since editing the file. I may have to go back to all states off just to see if that's it.
[Captivate Themes and Apps] shane87:
Hmm, that is odd. I haven't had any random reboots, and I have yet to experience the wifi reboot bug that everyone has been talking about too. These phones truly have their own personalities. Remember the random sleep deaths on froyo? No one could reproduce why they happened, and some people, like myself, never experienced them.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] bballer182:
Ok i just ran into a problem with CF. I couldn't for the life of me get the 1200MHz state to stick. CF would show that i had UV 1200 step but the max limit was set to 1000MHz. So i check the S_volt_sheduler and i was limited to 1000MHz right after i enabled and saved 1200MHz... i did it numerous times and it wouldn't save that step. CF would write everything else like UV for all steps and governor and scheduler but wouldn't save the 1200 step. The only way i could get 1200 was to "apply for now" and leave CF running in the background. as soon as it closed cpu went back to 1000MHz. So i just edited the S_volt_scheduler to max the cpu to 1200000, reboot and it stuck fine... Dunno what that was all about. Oh running BB 1.18.4 if that make a difference on Serendipity 7 build 1. CF was working just fine on Continuum 5.5 dunno the BB version though...
[Captivate Themes and Apps] aalh:
Use bb 1.17.1

I had the same thing happen

The bb installer from the market will do it for you

XDA Premium Roast
[Captivate Themes and Apps] shane87:
Yeah, for some reason, bb1.18.x does not work right. I am not sure what the exact problem with it is, but 1.17.1 is the bb I would recommend. I have never had issues with 1.17.1. I know that stericson's bb installer on the market has 1.17.1, and it works great.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] CuriousTech:
Check for the extra 0 in UV as well.

I didn't have the sleep death in Froyo for a long time, then installed NoLED and it started. Uninstalled it and still had the bug. I run a nadroid backup every 4-5 days, so restored the last one and was back to good. Personally I think it was vulnerability in the kernel, possibly voodoo sound, that could crash it on random notification events. But we'll probably never know now. I'm loving GB so far and just can't go back. If nothing I try works, I'll restore a backup from 2-3 days ago and work from there.
[Captivate Themes and Apps] aalh:
I have had SD in GB but only after a full charge

the way I have stopped them is to pull the battery for a minute or two

I learned this trick as a solution to the charge drain bug (which I have never had)

I decided to try it as a solution to the SD after a full charge since that is what triggers the charge drain, and it seems to cure the SD until you overcharge again
[Captivate Themes and Apps] shane87:
I've never had sd or charge drain issues on gb. I mean, I have had the phone charge for several hours past full, unplug and have 96%, but that is normal, compared to people reporting having 80% or something after over charge. On continuum 5.5 with talon 0.2.1 I charged for about an hour after full charge, and had 99% when I unplugged. These phones just do what they please, regardless of what you want them to do.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] shane87:
I think I may have spoken too soon! I was at work, and had my phone on. When I got off my phone was off and would not turn on with the power key, no matter how long I held it.

However, I was able to boot into recovery by holding vol up + power key. Once in recovery, I selected reboot system, and it rebooted, but when it showed the continuum boot animation, it rebooted. The second time it booted fine. Very strange.

I am going to post this in existz's and cesar's thread as well, to let them know.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] aalh:
Just rebooted (by choice ;-)) and noticed that CF quit saving boot settings, not sure if it was during 0.3.9 or 0.4

The file stays set to 1000max even though it shows 1200 enabled in the states

and in the volt file

BB 1.17.1

TalonDEV 0.2.1

BTW

apply for now, does apply the settings, they just arent saved as boot settings by the other button
[Captivate Themes and Apps] shane87:
Ok, so I just checked on my phone, and I am showing the same thing. My s volt scheduler shows 1200max. After saving boot settings with 1000max, it still shows 1200 in s volt scheduler. I even tried applying first. I am going to try applying, exiting cf, restarting, then saving, to see if it is saving the current max freq that is loaded at start up. I will let you know as soon as I have a fix.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] aalh:
SVolt now written to

It decided to save settings after I changed the uv on 800MHz

I decided to test if it was saving the uv, but not the OC

changing the UV (or dumb luck) made it save, I have done nothing else
[Captivate Themes and Apps] shane87:
Hmm, very strange. I will ha e to start digging in my save boot settings code. Unfortunately, I didn't add any logging to the save/apply code, as I have made no major moddifications to it. That's how it goes, though. I add logging to the places I think will be most likely to mess up, and something different breaks!

I am going to change uv settings on my phone and see if that causes it to save max freq changes. I need to reduce uv anyways, as I just got my second sd. :(

Edit: ok, so this just keeps getting stranger. I launched cf, dropped all uv's by 25, and I changed my max limit. I hit apply, then save. Checked s volt scheduler, uv settings saved, but max freq did not. Launched cf again, changed uv on 1200mhz, hit save, checked s volt scheduler, max freq saved. Launched cf again, to try to get back to the settings I wanted. I had not applied change to 1200mhz step, so it showed old uv. I changed max freq back, hit apply, save, checked s volt scheduler, uv saved, max freq not saved. Launched cf again, which loaded with the settings I wanted saved since they were applied last run, hit save, checked s volt scheduler, max freq stuck.

It seems to be that changing settings, hitting apply, save, closing cf, relaunching cf, then hitting save will cause it to save max freq. It is almost as if I have it saving the current max freq, instead of the selected max freq. However, that should cause apply followed by save to work. Unless it is saving the initial value loaded at cf launch.

Anyway, I will look at my code tomorrow and see if I can narrow it down. I would work on it tonight, but 27+ hours with no sleep makes it hard to concentrate on code!!

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] shane87:
Update!!!

Control Freak 0.4.1b is LIVE!!!!

Full changelog is in the OP.

Basically, this update just fixes the save function, and specifically the max frequency save. I was right, I somehow managed to have it save the max frequency that is read from sysfs, instead of the max frequency selecte by the user. Now it works right! I also added logging to the apply and save functions, so that any future problems in those areas can be diagnosed much easier. Also changed the export log function to clear the log after an export, so that you end up with an empty log, making it easier to see what changes have been fixed between different logs.

If you like this app, consider making a donation to my beer & pizza think tank fund! Donation link is under my thanks meter, and can also be found in the about screen of the app!
[Captivate Themes and Apps] CuriousTech:
I'm now running Continuum 5.6 which comes with Talon 0.2.2 and BusyBox 1.19.0

ControlFreak 0.4.1b works perfect every time.
[Captivate Themes and Apps] Skkip:
Quick Feedback

ControlFreak 0.4.1b working great in i9000 with TalonDev 0.2.1 :)

Looking forward for other great features. Maybe a visual diagram on TIS like in SetCPU?

Thx in advance
[Captivate Themes and Apps] shane87:
Well, maybe, but I am not much of a graphic designer myself. First though, I uave a feature that has been my priority from day one. I have just had to get the app running right first. I am back to work on it now, though. I am adding in governor specific tweaks, such as up-threshold, which controls how much of a load the cpu must be under for the governor to decide to scale up. There are some awesome changes that can be made with some of these tweaks. I am just waiting on some info from existz, since he is the one who clued me in on these tweaks in the first place.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] shane87:
Ok, so I am still working on governor specific tweaks. These are a little more complex to implement than I had imagined, so it may be alittle bit before I get a new release. Also, I have a couple other projects I am working on that are taking considerable time.

I am also looking in to CM7 compatability. One of my other projects is a cm7 specific version, but I am not sure on whether to take the plunge into cm7.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] shane87:
Update!!!

Control Freak 0.4.2b is LIVE!!!

The changelog is in the OP, and chipin (if you want!)

Also, check out the new icon, designed by b_randon14! Let me know what you think of it!

And if you have a Samsung Intercept, or know someone with a Samsung Intercept, check out bROM, at sdx, a rooted, deodexed rom written by my brother, b_randon14
[Captivate Themes and Apps] ggonzalez7777:
Thank you so much!!!! I was lost without your app working!!! Had to reduce to using voltage control with talon 2.2. Keep up the awesome work.

Sent using tiny little gnomes.....
[Captivate Themes and Apps] shane87:
Not a problem man, lol.

I am working on some new stuff with Existz for his next Talon release, which is going to push back governor-specific tweaks, again, but I think it will be well worth it, considering what me and Ex are working on.
[Captivate Themes and Apps] Reynaldinho111:
Ive heard about this in the talon thread. Talon 0.2.3 is going to be fairly ridiculous. Especially with what youre cooking up for cf shane. Should be good

Sent from my beloved Cappy!!
[Captivate Themes and Apps] shane87:
Well, all of the credit goes to TheEscapist, for figuring it all out, and Existz for adding it to Talon. I am just going to make it easier to do!

For thise who don't know, existz is adding gpu overclocking to the Talon kernel. Our gpu's currently clock at 200mhz, even though they are designed to run at a stock frequency of 400mhz. I am working on adding controls to Control Freak to make gpu overclocking simple and easy for the end user, instead of having to use terminal emulator and echo commands.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Themes and Apps] geokilla:
Our GPUs are designed to run at 400Mhz but it's running at 200Mhz atm? Why would Samsung do that? Or is it because Samsung just doesn't know how to code their firmwares and stuff?
[Captivate Themes and Apps] aalh:
battery life, and mtbf