Originally Posted by aalh

AHA
Here you are

subscribed
I will start playing with CF now

And I will think about an icon
(I did the one for Moneydance a few years back, a Linux personal Finance app))

Glad you found me! And I would love to see any ideas you have on an icon. The current icon is kinda bland and crappy, lol, but then again, I threw it together in about 5 minutes, so that's to be expected, lol.

Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101

Originally Posted by iXNyNe

I like the states enable/disable being in there with the UV setting, but I miss being able to see tis all in one place without having to scroll. Maybe the tis could be put on the line where the mV. Is displayed? I don't much miss the tis % but I can see that's not included and it is slightly handy.

More importantly than appearance I've noticed that all states show the same time for tis. Using cpuspy I see the real results. Also I'm still having issues sometimes where opening the app no states are selected and the Max clock is empty until I check at least one state. I also sometimes have blanks for scheduler and governor.

The new voltage control lite does not seem to suffer these issues, however I have noticed an inconsistency across the board about being able to save boot settings (sometimes works,sometimes not). And yes my init.d folder is chmodded correctly.

Rom continuum 5.4.1
Kernel talon 0.1.7

Nevermind about the sources for VC lite, I am looking at them now. It is very strange. You can confirm that VC Lite ALWAYS shows States Enabled info? Because xan is still using his original strings to access the states_enabled_table, and there are no changes to the ShellInterface either that would account for the difference. I know that VC Lite will always show all of the States in the Limit CPU drop down. I added code to make the Limit CPU drop down only show enabled states. Therefore, if it is not getting the states_enabled_table info correctly, you get nothing in the Limit CPU drop down. Is there any way that you could give me a confirmation that VC Lite always shows the States tab?

This issue has been driving me nuts since people started posting it for GingerBread. I just can not understand why it happens. And, as I have stated before, it is made even stranger by the fact that attaching the DDMS debugger makes the command work every time. I mean, how can I debug the issue if the issue will not occur while the debugger is attached?

Originally Posted by shane87

Nevermind about the sources for VC lite, I am looking at them now. It is very strange. You can confirm that VC Lite ALWAYS shows States Enabled info? Because xan is still using his original strings to access the states_enabled_table, and there are no changes to the ShellInterface either that would account for the difference. I know that VC Lite will always show all of the States in the Limit CPU drop down. I added code to make the Limit CPU drop down only show enabled states. Therefore, if it is not getting the states_enabled_table info correctly, you get nothing in the Limit CPU drop down. Is there any way that you could give me a confirmation that VC Lite always shows the States tab?

This issue has been driving me nuts since people started posting it for GingerBread. I just can not understand why it happens. And, as I have stated before, it is made even stranger by the fact that attaching the DDMS debugger makes the command work every time. I mean, how can I debug the issue if the issue will not occur while the debugger is attached?

vc lite actually NEVER shows the states tab, but it always shows my current voltage settings, whereas CF sometimes shows 0 uv for all states (which is also when it seems that all the states are disabled)

just an idea, since it seems like the max clock menu in your app seems to attempt to read which states are live and not show the ones that are disabled, maybe that code is interfering with the states being picked up elsewhere in the app (also causing them to display 0 uv)
that idea is based on no relevant information, but maybe something to look into if it sounds plausable

anyway if you upload a version with the debugger enabled and i'd be happy to provide logs of what the program is doing and maybe more than one set of eyes could catch the program misbehaving and then you'd be able to narrow it down
maybe with debugger enabled it always works for YOU, but others may still be able to reproduce the error

The debugger is enabled in the release I made. To use the debugger, you have to get the android sdk, and use the ddms debugger to launch the app. Of course, without having the sources, the debug output won't make much sense. It will tell you what function the error is in, but you couldn't see specific lines or anything.

Hopefully, in the next day or two, I am going to add in the logging code I added to vcex, so that users with issues can dump the log files and send them to me so I can see where it is messing up. As of right now, the only place that uses any kind of debugging is the shellinterface. And it only works if you have logcat enabled. Unfortunately, almost every rom that has talon baked in uses the version with logcat disabled. Once I add the logging code, it will all be logged seperate from logcat, so it will work even on kernels with logcat disabled.

Anyway, the issue seems to be caused with compatibility issues between busybox and/or shellinterface and gingerbread. The really odd thing, though, is that busybox works perfectly when called from a terminal emulator. I think it has to do with the shellinterface code I use. I have tried writing my own shellinterface code, and it has the same results. So I really have no clue, it has me stumped.

Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101

I cant find the interactive governor described anywhere (Linux kernel threads, or here)
What is it's profile?

Originally Posted by aalh

I cant find the interactive governor described anywhere (Linux kernel threads, or here)
What is it's profile?

Basically, the interactive governor will check the cpu load on a set interval. The stock setting for talon is to check no sooner than 50000 microseconds since the last check. (I am working on adding the ability to tweak this setting) If the cpu is above a certain load, it will scale up, like conservative. However, instead of going from 100 to 200, then to 400, etc... interactive will jump from 100 to max_freq (i.e. 1200 if you have the limit set to 1200). It scales down the same way.

I am unsure of the cpu load required for scale up/scale down decisions, as they are not enumerated in the sysfs, so no moddifying them either . Of course, that may be something that is hardbaked into interactive and is not supposed to be changeable.

Hope this answers your question!

Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101

thanks for the good work

My voltages dont stick after reboot is this a common problem ?

Edit: Nevermind reflashed and everything is better

Anyone having issues with boot settings not sticking, please read the OP, I included instructions on how to solve this issue.

Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101

So I have been playing around with some ideas that xan passed along to me. I was talking to him about the states_enabled_table info not getting pulled right. He suggested maybe switching from the way things are run right now, which is to manually create a new thread to run all of the initialization code, then update the ui once the new thread finishes. His idea was to use an AsyncTask instead of manually creating a new thread. I have (finally) got the AsyncTask setup and running the initialization code, and so far so good. I have not had any issues yet. Hopefully, by tomorrow, I will have done enough testing to be sure it is working right, and then I will release an update.