yashsingh1/xdaforums huggingface dataset:
[Captivate Themes and Apps] shane87:
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.

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Themes and Apps] 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?
[Captivate Themes and Apps] iXNyNe:
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
[Captivate Themes and Apps] shane87:
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.

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Themes and Apps] aalh:
I cant find the interactive governor described anywhere (Linux kernel threads, or here)

What is it's profile?
[Captivate Themes and Apps] shane87:
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!

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Themes and Apps] zenosteam:
thanks for the good work:)
[Captivate Themes and Apps] abee_13:
My voltages dont stick after reboot is this a common problem ?

Edit: Nevermind reflashed and everything is better
[Captivate Themes and Apps] shane87:
Anyone having issues with boot settings not sticking, please read the OP, I included instructions on how to solve this issue.

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Themes and Apps] shane87:
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.
[Captivate Themes and Apps] aalh:
sounds cool

async is where it's at dude!:cool:
[Captivate Themes and Apps] shane87:
Update!

Control Freak 0.2b is live!!

Changes:

- Switched initialization code over into an AsyncTask. This seems to have fixed the main issues found in VC/VCEX/ControlFreak since switching to Gingerbread. I have started Control Freak 100+ times, and the states_enabled_table info is always pulled correctly. If you still have difficulties with the States info, or any other issues, follow the "Report an issue" link in the OP.
[Captivate Themes and Apps] aalh:
just install on top of 0.1?
[Captivate Themes and Apps] shane87:
Yeah. Noth are signed with the same key, and I have the version values setup so that installing on top of 0.1 will be seen as an update.
[Captivate Themes and Apps] aalh:
ooops

wrong place
[Captivate Themes and Apps] shane87:
Just edited the issue reporting procedures. All issues should be reported IN THIS THREAD or via PM (preferably in this thread, so other users can see it).

Apparently, to report an issue through github, you MUST be a member of github. So I took the link down, since most users are probably not github members!

If you ARE a github member, feel free to post an issue through my github issue tracker, by visiting my source code link in the OP and selecting Issues. Please also post a breif description in this thread, so other users can see it.

A HUGE thank you to aalh for pointing out that the github issue tracker only works for registered github users!!
[Captivate Themes and Apps] shane87:
Ok, so I have the tis issue fixed. It was a simple matter of accidentaly always calling for the tis info from state 0. But I have it grabbing the right tis info now.

I'm also working on adding the tis readout to the main screen, so you don't have to open each state to see the tis info.

Hopefully I will have an update here in an hour or two.

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.3b is live!!

All that is changed in this release is the TIS issue is fixed, and I moved the TIS info to the main screen, so you can always see it.

Remember, if you use this app and want to see it continue to be developed, consider making a donation!!
[Captivate Themes and Apps] shane87:
Hmm, just noticed a new bug. For some reason, the enable/disable checkbox is not visible. I think it has to do with how I changed the layout when I removed the tis info from the open uv control and put it on the main screen. I will have to dig into this a little, see if I can figure it out. Has anyone else noticed this?

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] alexige:
With 0.3 I noticed that after a reboot the max clock speed selector shows 1200mhz even after saving 1000mhz as boot. I even retried by saving and restarting again and saw the same results. It did stay while the phone was on but after reboot it reverted back. I have cpu spy and havent seen it hit 1200mhz. This is my first time using this app so not sure if this is a known issue.
[Captivate Themes and Apps] shane87:
No, this was not a known issue. I just quickly checked on my phone, and I am seeing the same thing. I had never noticed it, since I always keep mine running at 1200mhz. I will look into this as well, hopefully have something in the next few days.

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:
Hit about and look at the version number at the top. ;)

It's kind of hard to use in landscape mode, but then what isn't?

It's been reading all the data every time, but sometimes doesn't save S_volt_scheduler. Not very often though and that could all be a problem with busybox on GB.
[Captivate Themes and Apps] shane87:
Well, it is supposed to disable the auto rotate and print everything in portrait, but I haven't really tested it myself. I'm glad everything is working great for you. Unfortunately, these phones seem to have minds of their own, and for some reason, the max cpu limit is not being set properly. I have never had an issue with s_volt_scheduler not getting saved, but it could be due to issues with gb and busybox.

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:
Yeah, pretty strange. It seem like it would either write the file or not, but every time I change UV it seems to work and change the scheduler it sometime fails. Maybe some kind of write, verify, retry?
[Captivate Themes and Apps] shane87:
That is strange, because, when you hit save as boot settings, it saves uv, scheduler, states, governor, and max cpu limit everytime, even if only one thing has changed. It just creates a new s_volt_scheduler file with all of the current settings, then gives it execute permissions and copies it over to the init.d folder. Unless it has something to do with having dificulty reading the changed scheduler settings, I'm not sure. I am planning on adding logging info on the next release so I can get some more info when issues happen, find out exactly what the problem is.

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:
OK, I finally decided to plunge back into TalonDEV so I could OC Mosaic again

running TalonDEV0.1.7 test 15

CFreak 0.3b

I cant get into 1200

I have reflashed the kernel, cleared caches

CF shows everything set for 1200max

but I have 0 TIS in 1200 according to CF, CPUSpy, and my linpack scores

what is keeping me from OC'ing?
[Captivate Themes and Apps] CuriousTech:
Get BusyBox installer and make sure you have 1.17.1 installed and not 1.18 or higher.

That seems to be the biggest problem, and I'm thinking even 1.17 is failing sometimes but works much better.
[Captivate Themes and Apps] shane87:
To answer your question, let me ask you a question. Can you see the checkbox when you open 1200mhz uv control?

If not, I know exactly what your problem is. Talon 0.1.7 comes with oc to 1200, but is limited to 1000 unless you enable 1200 and set your limit to 1200. When I moved the tis info to the main screen, I goofed the checkbox layout, so it is practically impossible to enable a disabled state, since you can't see the checkbox. I am working on a fix, but life is kinda hectic right now, so I haven't had much time for cf. My best suggestion for right now is to grab cf 0.2b and install it. It still has tis in the uv control section, and you can still see the checkboxes.

So grab cf 0.2, enable 1200 and set your limit, hit apply, and see if it works right. If not, let me know asap!!

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:
I could not see the checkbox, I downgraded ans saw the checkboxes

1200 was enabled

I toggled it

no difference

I even rebooted for good measure;)
[Captivate Themes and Apps] shane87:
Now that IS odd. What version of busybox are you running?

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:
I have tried 1.16 (from tibu)

1.19

1.17

1.18

I cant find any older than 1.16(which is the built in for TiBu)

BB Installer wont do older than 1.17

I will be back after sleep, at least I am not hving Sd's eh?
[Captivate Themes and Apps] aalh:
OK new oddity

I still havent got over 1000

I noticed that when I select 1000 max and disable 1200

after closing and reopening CF the max is set to 800

And yet the cpu still runs 1000

I am starting to think my phone is cursed

if I am not having SD's (and I am not) other stuff is screwy
[Captivate Themes and Apps] shane87:
That is very odd. Do me a favor. Open up a terminal emulator, and type "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" and tell me what it says. Then enable 1200, set your limit to 1200, and type the same thing in a terminal emulator and tell me what it says again.

It may be that I have messed up the apply function. If that is the case, I should be able to fix it fairly easy.

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:
it shows 100000 both times

and actually, when I opened cf after the first cat, it showed 100MHz as the max?!?!?!

the "M" in MHz is lowercase in the Max pull down (if that was a tag for a codeversion of yours)
[Captivate Themes and Apps] shane87:
Thanks a million man! That confirms what I already thought. For whatever reason, the settings are NOT getting saved to the sysfs. I will have to go back into my code and see what the issue is. Obviously, in fixing the reading of settings, I broke the writing of settings. Ah well, that is typically the case, you fix one thing and break another.

And a side note, the 'm' in mHz is supposed to be lowercase. Technically speaking, the SI prefix for "Mega-" is 'm', and the "official" shorthand for "Hertz" is "Hz", so "Mega-Hertz" would be "mHz." And that is something that I added in myself. Basically, the app pulls the current scaling_max_freq just like you did with the terminal emulator. Then the scaling_max_freq value is divided by 1000 to get mHz, and as I add the frequency to the list, I have the app add "mHz" to the end. Otherwise, you would just have "1000."

Anyway, I will dig through my app and see where I messed up. It will probably be tomorrow, since I have to go to work soon, but I will try to get it fixed as quickly as possible.
[Captivate Themes and Apps] aalh:
actually

lower-case m is mili 1/1000

upper-case M is Mega 10^6

I am an old HAM radio operator, I know my prefixes;)
[Captivate Themes and Apps] shane87:
Ahhh, I see. Well, in that case, I guess I need to change the strings to uave "MHz" oops!! I thought it was the other way around, probably due to people like me, saying I know something that I don't!!!!

Thanks for the info, and hopefully I will have an update by tomorrow or the next day.

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 I have tracked down the max cpu limit bug. And I now feel like a moron! I used the wrong variable to apply the settings. The variable I used collects the max frequency that is set when the app is launched. The variable I SHOULD have used is the one that gets updated when the cpu limit dropdown is changed. DOH! I also have the module layout fixed so that the state enabled checkbox is visible.

Now I am fixing another bug I just discovered. It is a minor bug, but it annoys me. :) Basically, if you apply a cpu limit without disabling the states ABOVE that limit (i.e. leave 1200 state enabled but apply a limit of 1000) it will show the max cpu limit to be the highest enabled state at next launch instead of the current max freq (to return to the above example, after you exit cf and re-launch it, it will show 1200 as the max, even though 1000 is the current limit) Like I said, it is not a big thing, and most people would not notice it, since most people would disable higher states when they lower their max cpu limit. I normally do that, and only caught it since I was testing max cpu limit application and had no reason to change anything else. But I will get it sorted out soon (hopefully) and have a release sometime soon after (again, hopefully)

And a HUGE thank you to aalh for letting me know about the frequency limit bug in the first place!!!

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.3.5b is LIVE!!!

Changes (full changelog in OP):

Fixed a few issues with the Max CPU Limit dropdown.

Fixed the module layout so that the enable/disable checkboxes are visible again.

The new app is up in the OP. Consider making a small donation if you like my work!!

NOTE: I removed CF 0.3b, since 0.3b has so many bugs. I mean, other than basic information gathering, not much of it works!
[Captivate Themes and Apps] aalh:
All working now:D

Not to be a whiner, but adding a % in bold or a different color at the end of the TIS line would be cherry
[Captivate Themes and Apps] iXNyNe:
So in 0.3.5 and 0.3 I've noticed the lovely improvement of seeing the voltage and time in state without the need to tap to see, however they are quite spaced out, I'm wondering if the verticle space between the voltage line and the tis line can be reduced, and such the row cell also be reduced in height making the total verticle space consumed by the information displayed less and there would be no need to scroll as there is now.
[Captivate Themes and Apps] shane87:
Yeah, I know what you mean, and I am planning on polishing the ui layout a little. However, there are features that I am still working on getting added, such as tweaks specific to each governor and possibly some profiles like setcpu uses. Once I get done adding features, then I will be focusing on ui improvement.

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:
Tis percentages, and deep sleep tis, is coming! But I have other features that I am more concerned with adding first. See the post above.

Also, the way I handle tis right now makes it slightly more difficult to do percentages, although that should not be a big problem. Deep sleep, on the other hand, is going to be a pain. And until I have deep sleep sorted out, I can't do percentages. But they are coming!

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] superj3211:
anyone ever find out if this works on cm7?
[Captivate Themes and Apps] geokilla:
I'm having trouble with overclocking using Control Freak. Every time I enable 1200Mhz in the Max CPU Frequency tab, it goes back to 1000Mhz. It can however hold my UV settings just fine.
[Captivate Themes and Apps] aalh:
get busybox installer from the market

install the lowest version of busybox (1.17)

then you should be ok

you may have to use root explorer to delete the old busybox(s) first

look in

/system/bin

/system/xbin

/sbin

delete anything called "busybox" no extension

then when you install BB it will be the only version on the phone
[Captivate Themes and Apps] shane87:
What version of CF are you using? That was an issue with 0.3b, and possibly earlier releases as well. 0.3.5b fixed that issue.

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] geokilla:
The latest version. However it seems that reinstalling Busybox fixed it. Let's see if it is a permanent fix.

Sent from my Samsung i896
[Captivate Themes and Apps] shane87:
Cool. I know that I had messed up 0.3 to where it wouldn't set max frequency even with the correct busybox installed. I had it setting the max frequency to the value it read at startup intead of the changed value. I'm hoping to be able to work on cf some this coming week, but I am not positive.

Also, when I do get back to work on cf, I will need a few testers, so if anyone is interested in testing new features and bug fixes, send me a pm and I will get back to you once I start working on this again.

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] RashaMatt:
States not working?

Control Freak 0.3.5b LOOKS like it's working correctly as far as saving settings, etc.

BUT, "time in states" shows that 400MHz is the lowest state that my phone actually spends any time in - even though I've enabled 100 and 200, and DISABLED 400.

Why would that be?

# pwd
/sys/devices/system/cpu/cpu0/cpufreq

# find . -type f -print -exec cat '{}' \; -exec echo '' \;

./cpuinfo_min_freq
100000

./cpuinfo_max_freq
1200000

./cpuinfo_transition_latency
40000

./scaling_min_freq
100000

./scaling_max_freq
1200000

./affected_cpus
0

./related_cpus
0

./scaling_governor
interactiveX

./scaling_driver
s5pv210

./scaling_available_governors
conservative ondemand userspace powersave performance interactiveX

./scaling_setspeed
<unsupported>

./UV_mV_table
75 75 100 150 150 150

./frequency_voltage_table
1200000 1275 1225
1000000 1275 1200
800000 1200 1100
400000 1050 900
200000 950 950
100000 950 950

./states_enabled_table
1 0 1 0 0 1
./cpuinfo_cur_freq
400000

./scaling_cur_freq
400000

./stats/total_trans
6201

./stats/time_in_state
1200000 34614
1000000 15920
800000 5238
400000 321142
200000 0
100000 0

SGS Captivate AT&T build 1010

ROM: Continuum 5.4.1

Kernel: TalonDEV 0.1.7 TEST17r2

Modem: KC1
[Captivate Themes and Apps] shane87:
Hmm, that is very odd. Do you possibly have something running in the background that could be keeping your phone from sleeping?

Can you get CPU Spy from the market, and see if it is spending any time in Deep Sleep? I haven't added the code to show Deep Sleep yet, due to difficulties with the current layout, but after I get some logging code added in, that is the next feature I am working on, is Deep Sleep, and TIS percentages.

If your phone is spending time in Deep Sleep, I don't see anything in the files you dumped that would keep the phone from running below 400MHz. It just doesn't make any sense, as my phone shows time in every state, although most of them except for 1200, 1000, and 100 are less than 5 minutes.