yashsingh1/xdaforums huggingface dataset:
[Captivate Themes and Apps] shane87:
Ok, so I think I have VC EX where I want it! I have successfully implemented the reset menu option. That option will apply stock settings, except for the scheduler, as mentioned above. It will not remove boot settings, that has to be done manually, by click menu > remove boot settings. It also does not cause a refresh of the ui, so you will have to exit and relaunch VC EX to see the stock settings.

I have also done a little tinkering with the max cpu limit dropdown. When VCEX launches, it will poll the states enabled settings to see what states are enabled, and only show those states in the dropdown. When you close the states tab, it will remove all frequencies from the max cpu dropdown, and add the enabled frequencies again, so that if you enable/disable frequencies, it will update the max cpu dropdown. Also, by doing this, it will automatically select the highest frequency you have enabled.

As soon as I get the version settings updated, I am going to be exporting the apk, signing it, and zipaligning it. Then I will be on here to post VC EX 1.4.0betaRC!!

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:
Woohoo!! VCEX 1.4.0b Release Candidate is live!! Try it out, see what you think!!

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] grkmaster:
With exists new kernel for GB - (Talon) - Limit Clock to box is blank and and when u click the drop down, there is nothing there. Is it cause the app wasnt adjusted for that kernel? Also when i click apply now it saved the settings and FCed

Edit: I went back to version 1.2.1b and the Clocks show
[Captivate Themes and Apps] shane87:
Hmm, not sure why it would show no clocks in 1.4.0, but 1.2.1 shows them. Unless it has to do with the way I add/remove states based on enabled states. I really have no way to test it, as I have not flashed gb yet. I do have to say that this app is NOT designed for gb or gb kernels. I am currently working on a new app for gb kernels, to be dubbed "Control Freak." It is going to be a full re write, with a different layout. I am holding off on flashing, though, until I get this app as stable as possible on froyo kernels. Once I get a final version of this app, I am going to flash to gb and hopefully by next week I will have an early beta release for talon gb.

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] grkmaster:
Good to know. Well at least the undervolting works, so for now im happy :-)
[Captivate Themes and Apps] TRusselo:
you forgot to change the date in the title...
[Captivate Themes and Apps] shane87:
Thanks, just fixed it!

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:
Update!!

Ok, so here it is, VCEX 1.5.0 FINAL!! This is identical to VCEX 1.4.0bRC, with the only change being that I disabled debugging on this version. Note that 1.4.0 and 1.5.0 will not work on Gingerbread! Use 1.3.0 for Gingerbread, at least until I get my rewrite for Talon kernel going! I left 1.3.0 up for anyone who wants to use this with Gingerbread. If you want any of the other versions, shoot me a pm, and I will forward it to you!
[Captivate Themes and Apps] rajendra82:
VC EX 1.3.0b doesn't always show the states drawer tab when running on GB (Talon with Continuum V5 RC3 ROM). In fact more times than not, the states drawer tab is invisible, thus having no way to change that portion of the script file. When the GB rewrite is started, you might want to set up a different way to provide a states checklist.
[Captivate Themes and Apps] wonner:
I believe existz said that he had trouble getting States activated on the newest Talon. I know that I couldn't see States on either VC EX (1.3) or original VC (3.0.1).
[Captivate Themes and Apps] TRusselo:
i havent been getting deep sleep the past few days whats going on? ff 3.0 onix 1.0.5 still 1.5 vcex
[Captivate Themes and Apps] shane87:
I am currently looking into why the States tab does not show up in gb. I just flashed gb yesterday, and I noticed the same thing. The really odd part is that gingerbread stores the states enabled information in the same location as froyo does. I will have to look into my vcex code and see just why it is not getting the information.
[Captivate Themes and Apps] shane87:
Another user, aalh I think, had the same issue. Rebooting the phone caused the deep sleep info to come back. I think the issue is the way I find deep sleep. To find deep sleep, I ask android how long the phone has been turned on since last reboot, then I ask how long the cpu has been turned on since last boot. However, the function that pulls the time since last boot has a note that states "Real time since last boot may be reset at anytime for reasons uncontrollable by the user." I think the issue is that the time since last boot is getting reset, which causes the cpu on time to be more than the time since last boot, so the app will show no time in deep sleep. As of right now, I know of no other way to get deep sleep time, but I am looking for a new method.

Even though I released a "FINAL" version of vcex, I am thinking about fixing the gb states bug, which causes the states drawer to not show in gb, even with older versions of vcex, and the deep sleep issue, if I can find another way to calculate time in deep sleep.
[Captivate Themes and Apps] TRusselo:
it was working great a few days ago before i flashed / bricked/ flashed back everything fresh.... rebooting not helping...
[Captivate Themes and Apps] wonner:
What kernel are you using? Talon 1.1 showed States with VC EX 1.3. Talon 1.3 does not show states on VC or VC EX.
[Captivate Themes and Apps] shane87:
I just flashed Talon 0.1.3, but I could not get the States to show up on Talon 0.1.1 either. I am looking into right now.
[Captivate Themes and Apps] shane87:
Thats very odd. Do you possibly have an app similar to Captivate Keep Alive running that could be preventing your phone from going into deep sleep mode?
[Captivate Themes and Apps] TRusselo:
no... nothing and i mean nothing, i probably have one of the cleanest no crap systems here... as far as user apps.
[Captivate Themes and Apps] shane87:
That is very odd. Unfortunately, I really have no way to test it, as I have now flashed over to Gingerbread. I have tracked down the issue with Gingerbread and states enabled. I just don't know why it is happening. For whatever reason, on TalonDEV kernel, the ShellInterface module, which handles all calls to the su shell, is returning an empty string when it tries to get the information from

/sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

The odd thing, however, is that the states enabled file does exist, and has the correct information in it. Even odder is the fact that the call is successful if the app is connected to the DDMS debugger. I am checking through logcat, trying to find the reason for it, and it just makes absolutely no sense. Anyway, hopefully I will have it tracked down soon, and then I can begin work on Control Freak for gb. And I am also looking into the deep sleep issue, but I have to get states enabled right first, or I can't even check deep sleep!!
[Captivate Themes and Apps] TRusselo:
so it is deep sleeping just not reporting for me?
[Captivate Themes and Apps] shane87:
Its possible. I have gotten vcex to work on gb, sort of, by running it with the ddms debugger attached. My deep sleep is showing correctly. I will be looking into a new way to find deep sleep time once I get the states enabled bug in gb completely fixed.

ROM: Perception II beta 1

Kernel: TALONDEV 0.1.1, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] TRusselo:
im not on GB eh?

EDIT addition:

i charged a battery on a wall charger,

put it into my phone,

bump charged it (tried to it was full),

then wiped battery stats

deep sleep not registering anymore - so that would not go along with the theory about the calculation getting messed up... no??

so might be looking at something else...

--vcex1.5 firefly 3.0(full rom install) onix 2.0.5
[Captivate Themes and Apps] shane87:
Well, I'm kind of trying to get vcex to work on both gb and froyo, and I am probably going to make my rewrite backwards compatible, so it will run on both too. And be glad you aren't trying to run vcex on gb. It works, sort of. Except that most of the time, like 99 times out of 100, it will not pull the states enabled info, so you can't really do anything besides uv, unless you have 1.3.0 or earlier. And with 1.3.0, all you can do is uv and max cpu limit, since the states tab still doesn't work. I know that it is a headache trying to figure this out, cuz all of the features in vcex are implemented in the same way, by calling shellinterface with a command to get/set the settings, and yet the only thing it won't do is pull the states enabled info.

ROM: Perception II beta 1

Kernel: TALONDEV 0.1.1, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] TRusselo:
well i appreciate all you do.

i just wasnt sure by your answers earlier if you remembered i was GB or not.

and see my edit above about my battery pull

EDIT:

well i think i may have fixed it for now... flashed back to stock, (to flash custom boot image), then reinstalled firefly, theme, dialer, lagfixed, rebooted and tibu restored...

all is good now.. 10 minutes of deep sleep!! - though havent UV yet...

- sh!t happens... without explanation sometimes....

although the last 2 nights i flashed from stock to this i was using nandroid backups of user apps + data then. this time only tibu and fresh zips. feeling snappy as crap!
[Captivate Themes and Apps] shane87:
Yeah, I knew you were still on froyo. I was trying to say that I couldn't really test because I am on gb and I have to get vcex working for gb before I can start investigating anything else. On gb, the states button at the bottom is disappearing because, for whatever reason, the app can't pull the states enabled table even though it is there. Without the states button at the bottom, I can't see any time in state info, and definately not deep sleep. The tis for all of the states except for deep sleep is written in a file. For deep sleep, however, the tis is figured by calling os functions. With the states tab being disabled, I can't get the app to run the function, so no way to test it.

I am going to send you a pm, because I have an idea about shedding some light on this issue, if you are agreeable to my idea.

ROM: Perception II beta 1

Kernel: TALONDEV 0.1.1, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] grkmaster:
what is odd that a couple times i have see the states tab on the bottom and it only happened when i wasnt paying attention, so it was at random even before OC. Then when existz did the OC and i kept opening and closing vcex to get it and no luck
[Captivate Themes and Apps] shane87:
Yeah. I have gotten States a few times on Talon 0.1.3, but I can't get it to show up consistently. It makes absolutely no sense. I have only had problems with the states, except one time it didn't get the available schedulers. The really bizarre thing, though, is when I select Run>Debug from within eclipse, it ALWAYS pulls the States info. So I can't even debug the problem.

The app gets the states info by calling a shell, the running "cat /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table" and getting the output, which on my device should be "1 1 1 1 1 1" Yet it will usually just return "", which then causes the app to hide the states info, since it can't find it, and on vcex 1.4.0+ it will also cause the max cpu limit dropdown to be emptied, since that dropdown is filled based on what states are enabled.

If I open Terminal Emulator, and type su, to get a root shell, followed by the exact same command VCEX uses, "cat /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table" I ALWAYS get the correct output. It just does not make sense at all.

Anyone who has any ideas, let me know. I have tried everything I can think of, from updating busybox, rolling busybox back to 1.17.1, using catv instead of cat, manually specifying /system/xbin/cat, and even having the app try up to 20 times, checking for the correct output after each pass.

I think I am going to try skipping the shell interface all together, and just opening the file with a standard file input stream reader, and see if that works. Hopefully I will figure this out soon.

I also have TRusselo running a version of VCEX 1.5.0 with some added logcat lines to see if I can track down the sporadic issue of no Deep Sleep time, so when he gets back to me I may have a fix for that as well.
[Captivate Themes and Apps] grkmaster:
Cant it just be something in the talon kernel? or the GB kernel itself being so different? Odd that it shows the states once and not again.
[Captivate Themes and Apps] shane87:
It could be. I sent a message to existz with my shellinterface logcat dump, so he can see that it is getting all of the calls right, except for the call to states, so maybe he can figure something ot on the kernel end. It may even be something in the dalvik vm that is different.
[Captivate Themes and Apps] TRusselo:
you get my email? states tab disappeared on onix with the debugging version you sent me lol
[Captivate Themes and Apps] shane87:
Yeah I see that! I think it is because I forgot to undo the changes I was working on for GB!! I'll get a new one put together after while and send it to ya!

[EDIT]I just sent you a new debugging version. I had forgotten to undo all of the changes I had made trying to get States to work in GB!![/EDIT]
[Captivate Themes and Apps] shane87:
Ok, so I am at a complete loss as to why States info will not show up in Gingerbread. I have tried everything I can think of. I have tried different commands (catv instead of cat), I wrote my own shell interface, I tried opening states_enabled_table with the standard java.io.inputstreamreader, I tried manually typing the command in as opposed to using the global variable with the command in it, and I have even tried requesting the information up to 25 times in a row, checking for output after each try. I just do not understand why it will not work, especially as running the command in a terminal emulator ALWAYS works, and the app ALWAYS works when I try to debug it using the DDMS debugger through eclipse. I just defies all logic. At this point, anyone who has any knowledge of app writing in Android, please download my sources and see if you can come up with anything. I think I may take a break for a few days, see if I can come up with something after I have not been looking at the code for several days straight.

Of course, this also throws a wrench in my plans for the re write of VCEX for Gingerbread, as it will use the same methods to request the information.
[Captivate Themes and Apps] TRusselo:
maybe check google android resources, maybe something got changed in gingerbread, handled or called different...? just throwing out ideas.. no expert...
[Captivate Themes and Apps] shane87:
Yeah. I think it has to do with the dalvik vm. Because if it was a kernel issue, it should affect the command when you type it in a terminal emulator as well. I will spend the next couple of days looking through the google dev resources, see if anything changed in the vm that would cause the issue, and see if there is a work around for it.

ROM: Perception II beta 1

Kernel: TALONDEV 0.1.1, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] aalh:
I was able to stop use of deep sleep by disabling 100Mhz

all it did was make my phone use 100Mhz instead of Deep Sleep

I re-enabled it but the phone still wasnt sleeping

I just rebooted to see if it comes back

Yes, rebooting after re-enabling 100Mhz brought back sleep again
[Captivate Themes and Apps] aalh:
here's an odd one

cpuspy shows 600Mhz in the used states, but with no time

I have 600Mhz disabled in EX, (which btw also correctly shows no time for it)

HUH?????????

Why does CPUspy think 600 is enabled? I havent had it enabled for almost a month
[Captivate Themes and Apps] shane87:
Hmm, thats very strange. I am not sure how cpuspy goes about checking times and enabled/disabled states, I have only looked at the cpuspy code long enough to see how to get the deep sleep time. If it is showing not time in state for 600mhz, then it is obviously disabled, so I wouldn't worry about it too much, although it is odd, because I think the way cpuspy determines if a state is used or not is based on the time spent in the state. If it shows no time in the state, it shows up as being disabled, but I am not sure.
[Captivate Themes and Apps] shane87:
Possible fix for GB

Ok, so I think I have the States issue fixed in GB! Out of twenty runs, the States tab showed up in 18 of them. I need some testers though, before I release this thing into the wild. Specifically, I need testers that are still running froyo. So if you want to test this release, hit me up with your email and I will send it to you!

I am also adding in some logging code that operates separate from logcat, as I know most people are running kernels with logcat disabled.

Anyone who wants to test will get instructions on how to include logs with any problem reports, and I will post the instructions up in the OP when I release this version.
[Captivate Themes and Apps] aalh:
I had a COD tonight.....l 600 finally went away....

but

I now notice I have 0 TIS for sleep again

I have been letting it sit and checking every hr or longer

no time in sleep

I am revisiting recovery to see what I see

......

I went to recovery and enabled the VM tweak. I now have the noatime & VM tweaks enabled (that is all)

and on reboot I have sleep again

on a side note:

I have lots of data in juiceplotter that shows a definite difference between when I have SD, and when I dont

as long as sleep is working the battery makes a steady fall over time, if sleep is enabled AND I am suffering SD's the plot will show the phone staying at the same % for HOURS. Either the phone loses track of the voltage, or when SD's are happening the phone gets crazy efficient
[Captivate Themes and Apps] aalh:
OK now it is REALLY weird

after rebooting to get sleep back

then letting it sleep for an hour...

both cpuspy AND EX show 14% of TIS in a speed that is NOT enabled

1120 shows use, and I havent had that speed ever enabled on this rom!!!!

WTH???
[Captivate Themes and Apps] shane87:
Update!!!

Ok, so I have re-visited VCEX, and I have a new release. For whatever reason, as many of you may know, VCEX was not working properly with Gingerbread. Well, I have fixed it, sort of. The issue of the States tab not showing still occurs occasionally, and I have had a report of the States tab disappearing in FroYo, although I can't personally test it. Please read the OP, as I have made some changes in how I want bugs reported as well. Enjoy!!
[Captivate Themes and Apps] Rrryan2:
Mixed results here... 1.6.0b indeed seems to have reliably brought back the States tab. However, UV/OC settings no longer appear in Voltage Cotnrol EX after reboot. States enabled *do* stick and appear correctly when pulling up the states tab. Although they don't appear to be enabled in the VCEX homescreen, OC settings do seem to actually be applied as the 1200 state is shown being active 8% of the time in VCEX and CPUspy.

Weird.
[Captivate Themes and Apps] shane87:
What do you mean the uv/oc settings don't appear after a reboot? Are you saying that the expandable list, where you can select undervoltage settings, is disappearing?

I am having no trouble after multiple reboots, aside from the states tab disappearing occasionaly. Restarting VCEX always brings states back though. If you continue to experience the issue, read the OP and send me the vcex.log file.

ROM: Perception II beta 2

Kernel: TALONDEV 0.1.4, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] grkmaster:
If he is talking about UV not sticking then its a common issue with couple roms not the kernel or your app. Busybox needs to be updated. Seems Continuum doesnt have this issue but on Perception and i think GR-x, it had the issue.
[Captivate Themes and Apps] shane87:
Yeah, if the settings are not sticking on reboot, it is a busybox problem. I rolled back to busybox v1.17.1, and have had no issues.

ROM: Perception II beta 2

Kernel: TALONDEV 0.1.4, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] grkmaster:
Hope this info helps you. Seems to be a kernel issue but not sure..With Cezar setting the OC to stock on Continuum 5.2, VCEX1.6B crashed trying to apply or save boot. The states tab below shows everything unchecked and the box up top is blank.
[Captivate Themes and Apps] shane87:
The reason it crashed on apply settings and save boot settings is due to having all of the states unchecked. When all of the states are unchecked, it will remove all of the options from the CPU Max limit dropdown. When there is nothing selected in CPU Max limit, it WILL force close on apply. I mean, it can't apply a max limit of null.

With that said, was everything unchecked in the States tab at start up?

Try launching VCEX again, and see if the States tab shows up. If it does, see if any States are checked. Check at least one State, and apply settings again. Then close VCEX, launch it again, and see if the settings are sticking. They should stick, but if they don't, or if you have any other issues, such as fc's, hangs, crashes, or a disappearing States tab that is NOT fixed by restarting VCEX, follow the directions in the OP to export the log, and attach it to an email that describes the issue(s), and send all of it to eric.clothier@gmail.com
[Captivate Themes and Apps] Rrryan2:
Sorry if I described it poorly, maybe these will help:

Not sure what's happening - maybe OC settings stick but UV don't...?

This is after applying OC/UV and then rebooting. Already tried a difft. Busybox using the 'Problems' button in TiBu.
[Captivate Themes and Apps] shane87:
Hmm. The issue is with busybox or init.d script support, as I had the same issue. However, to fix it on my phone, I needed to downgrade my busybox. Perception II comes with busybox 1.18, and I downgraded to 1.17.1. After the change, everything worked again. If you are still having issues, copy your boot settings, found in "etc/init.d/s_volt_scheduler" to you computer, and send it to me at eric.clothier@gmail.com

ROM: Perception II beta 2

Kernel: TALONDEV 0.1.5, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Themes and Apps] grkmaster:
VCEX showed states tab pretty much every time i opened it but everything was always unchecked. I noticed something as I was playing with it. I check 1000mhz and another tab and when it pulled down the stats tab it shows 1000mhz in the box, so then i enabled the rest of the states clicked on the box and selected the 1000mhz option and then clicked apply now and it didnt crash