[Q] Features Missing in pengus77's CM10-20130514 - LG Optimus 2x

Flashed this CM10 based ROM yesterday. Found that 2 key features that were baked into system in previous release are missing from this release.
First is Overclocking/underclocking of CPU through Settings->Performance. Now this options is missing altogether from the list.
Though this drawback can be mitigated by using Trickster Mod or similar app.
And second one is the option to "customize auto-brightness settings". There are some apps in the store that promise similar utility, but they never worked for me. This option wasn't needed if auto-brightness levels were not as super low as they are in this release.
Anyone noticed this?

Diljinder said:
Flashed this CM10 based ROM yesterday. Found that 2 key features that were baked into system in previous release are missing from this release.
First is Overclocking/underclocking of CPU through Settings->Performance. Now this options is missing altogether from the list.
Though this drawback can be mitigated by using Trickster Mod or similar app.
And second one is the option to "customize auto-brightness settings". There are some apps in the store that promise similar utility, but they never worked for me. This option wasn't needed if auto-brightness levels were not as super low as they are in this release.
Anyone noticed this?
Click to expand...
Click to collapse
1) I removed the CPU Settings because they're limited and don't work with this device as they should (Tegra needs a different kind of love).
2) I removed the auto brightness settings because they rely on the light sensor exposed to the rom... which we don't have. All the auto brightness is handled in the kernel (on ICS as on CM) so every operation in that menu is basically a no-op.
For 1, use CPU Adjuster or Trickster Mod from the market and you get a load more options that are guaranteed to work.
And for 2, check my kernel thread. You can mod the auto-brightness settings via sysfs, or wait a bit until wfd adds that feature to Kowalski Manager
Hope this clarifies why those two things are gone

pengus77 said:
1) I removed the CPU Settings because they're limited and don't work with this device as they should (Tegra needs a different kind of love).
2) I removed the auto brightness settings because they rely on the light sensor exposed to the rom... which we don't have. All the auto brightness is handled in the kernel (on ICS as on CM) so every operation in that menu is basically a no-op.
For 1, use CPU Adjuster or Trickster Mod from the market and you get a load more options that are guaranteed to work.
And for 2, check my kernel thread. You can mod the auto-brightness settings via sysfs, or wait a bit until wfd adds that feature to Kowalski Manager
Hope this clarifies why those two things are gone
Click to expand...
Click to collapse
Thanks for clarification. I appreciate it.

Related

SetCPU for Root Users [2.2.4] Undervolting and more 07/07/2011

ROM developers: Please do not include SetCPU in your ROM. I appreciate the work you're doing, but link to this thread instead, and I'd really appreciate it if you mention that SetCPU is available on the Android Market.
SetCPU is a CPU speed tweaking application for Android. More specifically, it allows control of certain aspects of the Linux cpufreq driver, allowing for overclocking, underclocking, or tweaking speeds and settings on many Android devices. It will work with most if not all rooted Android 1.5/1.6/2.0/2.1/2.2/2.3/3.0/3.1 builds on most devices.
The program is free here for XDA members. It costs 1.99 on the Android Market and available for purchase on the Amazon Appstore for users in the US.
QR code (please donate by buying it on the market ):
Warning: Extremely low or higher than normal frequencies may freeze your phone. Especially high frequencies (such as those enabled in certain custom kernels) have a risk of shortening the life of your phone. If your phone freezes, just yank out the battery.
Please buy it on the Market to donate if you like it.
Documentation and more information can be found here: http://www.setcpu.com/
Changelog:
1.4.0: Revamped the main interface quite a bit, and fixed a few minor bugs.
1.4.0a: fixed a bug where 122MHz was being called 128MHz.
1.4.1: * Using Eclair API. Will work on QVGA devices (Tattoo) and WVGA devices (Sholes)
* Major performance enhancements - setting frequencies should be much faster in every situation (in the main application, profiles, upon startup, etc.).
* Added a small home screen widget that shows the current maximum and minimum frequencies. Clicking this widget launches SetCPU.
* Frequency lists for Snapdragon devices, Samsung Galaxy, Motorola Cliq, and HTC Tattoo have been included, though support for these devices is experimental. The device can be selected on the introduction screen.
* Custom frequency lists are now supported. To enable custom frequencies, place a file called setcpu.txt on /sdcard/ or /system/sd/, sorting frequencies in kHz, separated by comma, from lowest to highest, then select the corresponding option on the introduction screen.
* There is no longer a "set" button - changing the seekbar positions will immediately set the frequency. As a result, all seekbars in the application will now snap back if the user attempts to place the maximum frequency below minimum.
* Instead of refusing to work at all, SetCPU will now operate in a read-only mode if root access is not detected.
1.4.2: Instead of choosing between performance (always max) and ondemand CPU governors, there is now a drop down list with all the available governors on the device. Thanks morfic! Added CPU scaling configurations for the OMAP3 processor of the Motorola Sholes/Droid/Milestone. This is strictly in beta. Custom frequency list now reads from /system/setcpu in addition to setcpu.txt on SD FAT or EXT.
1.4.3: Includes compatibility fixes for HDPI devices and UI enhancements. Frequency lists for the Samsung Moment (untested), the T-Mobile Pulse, and the Acer Liquid have been included. The application will no longer sometimes re-set CPU frequencies upon launch.
1.4.3a: Added more frequencies for the Nexus One.
1.4.3b: Fixed a widget issue on the Nexus One. Sorry for the rather rapid succession of updates the past few days!
1.4.3c: Adds support for 600MHz kernel patches on the Motorola Droid. On the Droid configuration. SetCPU will attempt to detect the existence of 600MHz and adjust the frequency list accordingly.
1.4.4: Adds an "autodetect" option that works on newer kernels (at the bottom of the device selection screen). This should enable the supercharged speeds in some of tasmanian_droid's newer kernels. Fixes a force close crash when selecting some frequency lists that were not compatible with the device (thanks Julian).
1.4.5: - Streamlined/refactored profiles code.
- Added "battery temperature" profile. SetCPU is now able to set a certain speed when the battery goes above a user-defined threshold. This would optimally be set to throttle the CPU lower at a high temperature. To ensure compatibility with your device, see if a valid temperature is displayed in the "System Info" menu. This profile does not take effect immediately and does not replace being cautious - it is not based on CPU core temperature, and must wait for a battery state change before reacting.
- Added an "About" button to the main screen with simple themes. Default color scheme is now "Dark"
- Adjusted the widget to display four digit speeds properly (thanks Berzerker).
- Various bugfixes and UI tweaks.
1.4.6: Fixed issues with the battery profile. Included a much better icon thanks to Josh Deere (dphase).
1.5.0: * CPU governors can now be defined in profiles.
* Included a notifications service for profiles - turn this on using the relevant checkbox in the profiles menu.
* Profiles now log which speed and governor is being set.
* Added "advanced" tweaking capability for conservative governor.
* The system info menu and profiles menu now show temperature in both Celsius and Fahrenheit, and the widget also now displays battery temperature in Celsius and Fahrenheit.
* Added a "long benchmark" option to the system info menu, which should be more consistent than the "short benchmark."
* Also added a simple stress test to the system info panel to test the stability of overclocks.
* Autodetect is now the default for devices that support it, and will be the first option in the menu if available.
* Improved I/O performance.
* Various bugfixes, especially in profiles.
1.5.0a: * Charging profile now no longer takes effect when the phone is at 100% battery and unplugged.
1.5.1: * Two more battery profiles added. Lower battery readings will always take priority (eg. under 80% will always take priority over under 100%).
* Governor will now refresh alongside the other readings. Added governor reading under current frequency reading.
* Added an auto-refresh checkbox to the main screen. If checked, SetCPU will periodically refresh the current frequency reading without the need for pressing the refresh button. This checkbox applies to the system info panel as well.
* Tweaked the widget, and attempted to fix the elusive bug where the widget did not update correctly sometimes.
1.5.1a: * Fixed widget being cut off in landscape mode.
* Fixed Fahrenheit temperature reading in profiles.
1.5.2: * Added optional failsafe notification warning system that plays a ringtone and flashes the LED red when the failsafe profile is active (thanks WootRoot!).
* Added "copy to clipboard" function for the System Info menu (press Menu).
* Added an optional "active" widget, which will refresh CPU speeds at an interval like the main interface.
* Added support for the OMAP3 temperature sensor for the Droid. If present, use of the OMAP3 temperature sensor can be enabled in the failsafe profile.
* If available, the OMAP3 temperature can also be read in the system info menu.
* CPU temperature settings will only appear if the sensor is present and support for the temperature sensor is enabled in the kernel! Right now, this is only for the Droid.
* The about menu now defaults to a "default" theme where SetCPU will not mess with any backgrounds defined in the XML layout.
* Fixed stress test failing when JIT is enabled.
1.5.2a: * Temperature sensor used in the widget for the Droid is now controlled by the failsafe setting. I will implement a proper appwidget configuration activity in a later update.
* Fixed an issue with the audible warning notification not being properly dismissed.
* Profiles optimizations.
1.5.3: * Memory/performance footprint decreased.
* Battery drain should be fixed on the Droid.
1.5.3a: * Active widget CPU usage optimized.
* Further profiles optimization for the Droid.
* Uncommon I/O force close fixed.
1.5.4: * Switched to the Android 2.2 SDK.
* Enabled external storage support (install location is automatic).
* Eliminated the distinction between the active and passive widgets, and replaced it with an appwidget configuration activity for the widget, allowing the user to choose the color of the max/min text, temperature display, temperature sensor (Droid), and refresh interval.
* Optimized the active widget refreshing.
* SetCPU will now hide non-autodetect frequencies by default on devices where autodetect is available, but hard coded frequencies and the custom option can be re-enabled with a button.
* Custom frequency list can now read from this exact file: /data/local/setcpu (in addition to the previous setcpu.txt on SD fat or ext).
* Includes various bug fixes and minor UI changes.
1.6.0: * Ported parts of the app to the NDK to improve performance.
* Fixed a bug where the widget was resetting colors upon reboot or launcher orientation change.
* Autodetect now works for all devices. It is recommended by default.
2.0.0: * User interface has been completely redesigned, and now uses tabs for switching between menus instead of buttons. Landscape mode in the main tab no longer requires scrolling down. The Advanced menu and Profiles menu have also been redesigned for a better landscape experience.
* The "auto-refresh" option and refresh button in the main interface and system info menu have been retired - SetCPU always auto-refreshes automatically.
* The profiles menu and service have been recoded from scratch, and now allows the creation of unlimited profiles with custom priorities. The "priority" meter for each profile determines the order in which it is evaluated - if two profiles apply to a given situation, the profile with the higher priority will be set. If you had profiles set before 2.0.0, you will need to set them again.
* Profiles have been further optimized for performance footprint as a result of the re-structure.
* Added "Charging AC/Full" and "Charging USB/Full" profile conditions to distinguish between fast charging and slow charging modes on some devices (thanks Julian).
* Added a beta "perflock disabler" feature that will enable frequency changing on stock HTC 2.6.29 kernels. Access the perflock disabler this by pressing Menu in the main interface. If this gives you an error, does not work, or crashes your phone, your kernel is not compatible - pull your battery to reset if necessary. E-mail me with your ROM, phone model and kernel information in "System Info" (thanks to Richard for a lot of help with the low-level stuff, and no thanks to HTC for implementing perflock in such a way . To access the perflock disabler, press Menu in SetCPU's main interface.
* Code cleanup and more.
* A big thanks to everyone who tested, especially those who gave feedback on this one, all the people who purchased SetCPU from the Android Market, as well as all my users.
2.0.0a: * Fixed a permissions error that was causing SetCPU to autodetect incorrectly and force close on some ROMs.
2.0.0b: * More fixes, sorry guys.
* Fixed an issue with profiles and custom frequency lists.
* Clarified the profiles priorities introduction.
* Fixed a bug with the Advanced menu erroneously reporting values if the governor was changed after onResume was called, and fixed a crash that sometimes occurred as a result.
* Fixed a bug where the passive widget acted like the active widget after frequencies were manually set.
2.0.0c: * Fixed issues with the Advanced menu and Advanced settings not being
applied on boot.
* Fixed an issue in where temperature warnings were not being dismissed
properly.
* SetCPU 2.0.0 no longer force closes on Android 1.5 devices, but the UI in
some menus is flawed. I recommend that you update to a more recent version of
Android if possible.
2.0.1: * Added a few widget backgrounds. Configure this when adding the widget.
* Added the ability to "swipe" to the next tab.
* Fixed various bugs.
* New documentation is up.
2.0.2: ** End of life for Android 1.5 support.
- Perflock disabler support for HTC-kernel 2.6.32.15.
- New native benchmark button in the system info menu. The results of this benchmark is unaffected by VM optimizations like JIT, so it's ideal for speed comparisons across different devices.
- Added support for tweaking the "min sample time" of the interactive governor, if available.
- Fixed a bug where the scaling governor would not change when the profile switched and SetCPU's main tab was visible.
- Fixed an ANR bug in the "set on boot" function which sometimes caused the Advanced settings to not apply.
- Fixed an issue where SetCPU sometimes did not start on boot when used with Superuser Permissions 2.2.x.
- Fixed a force close issue that occurred when SetCPU could not autodetect frequencies due to permissions errors in the ROM.
2.0.3 - Added a "safe mode" function that prevents SetCPU from running any tasks during boot if a file called "setcpu_safemode" exists in /sdcard or /data/local. This is useful if unstable settings were saved with "set on boot" checked.
- Reverted changes originally made to compensate for the old Superuser Permissions startup bug. SetCPU should perform startup tasks expediently again.
- Perflock disabler has been tested to be stable on supported kernels. The perflock disabler menu now has a "set on boot" function. Always disable this when switching to a new kernel or ROM. If you forget to do this and you get crashes, you can use the safe mode function above to disable it.
- Fixed crash issues with read-only (no root) mode, and disabled perflock disabler in read-only mode.
- Fixed a crash related to the widget service.
2.0.4 - Added the ability to back up and restore profiles to and from the SD card by pressing the Menu button in the Profiles tab. A "send" option is also available to send the profiles file as an attachment. Save the .setcpudb file to the SD card to restore it.
- Added perflock disabler support for HTC kernels 2.6.32.17 and 2.6.32.21 (T-Mobile G2, myTouch HD, Desire Z, Desire HD). "Set on boot" will not yet work on these devices because they only have temporary root.
- Fixed another crash in the widget.
2.1.0 - Significant UI and user experience revamp, including a new background for the widget, and new notification icons
- Added a quick priority swap button to the profile lists
- Significantly improved the reliability of autodetect on certain kernels
- Numerous bug fixes and crash fixes
2.1.1 - Fixed an issue with profiles backup in CM7.
- Added support for the Motorola Xoom, Atrix 4G, and other Tegra 2 devices.
- Fixed various bugs.
- Tablet optimized UI and more profiles coming soon!
2.1.1a - Fixed the 0 MHz display issue on some devices.
2.1.2 - Minor update. Adds a time of day based profile which will trigger based on a set time range. Fixes a bug with profiles and certain dual core kernels. Switched to the Android 3.0 SDK. Note that on some Tegra 2 kernels, scaling is completely controlled by the driver.
2.1.2.1 - Fixed a crash that occurred when updating from certain versions of the profiles database.
2.1.3 - Added perflock disabler support for HTC kernel 2.6.35.10 (in beta). Enhanced the Time in State readings in the System Info menu to include percentages. Removed WiFi permission until this feature is added to profiles. Fixed another database crash, and other bugfixes.
2.1.4 - Revamped Info tab UI. In portrait, clicking on an item in the Info tab will launch information on that category, and pressing back will return to the menu. In landscape, the content and the menu are split into two columns. Benchmarks are at the bottom. Added a chart for Time In State readings. Widget reliability fixes and optimizations. The main screen now indicates which kind of profile is currently active with an icon. Miscellaneous bugfixes and optimized performance.
2.2.0 - Added an "In Call" profile. Improved the Set on Boot safemode function by including a flashable zip that toggles SetCPU's safemode. Press menu on the main tab for more details. Added autodetect support for all Tegra 2 fakeShmoo kernels (ie. G2x). Added a "Voltage" tab for undervolting the CPU on fakeShmoo kernels, some custom Galaxy S kernels, and some Nexus S kernels. This is a full-fledged interface for undervolting these devices, and includes backing up and restoring and a Set on Boot checkbox. Improved the way SetCPU initially requests root. Various miscellaneous bugfixes.
2.2.1 - Fixed the voltage force close bug on some Galaxy S devices by adding undervolt support for older Galaxy S undervolt kernel patches. Added perflock disabler support for HTC kernel 2.6.35.9 (beta).
2.2.3 - Fixed an issue where the voltage menu displayed frequencies backwards on certain devices capable of voltage control. Added support for additional CPU temperature sensors.
2.2.4 - Improved support for the new MSM 8x60 devices (such as the HTC EVO 3D and Sensation).
thanks dude, that was a fast update!
I wonder if it is possible to add some more freq. between the range of 384 and 528 for the next udpate, e.g. like 500 or 480 for the non 1.5 cupcake build.
smagicmans said:
thanks dude, that was a fast update!
I wonder if it is possible to add some more freq. between the range of 384 and 528 for the next udpate, e.g. like 500 or 480 for the non 1.5 cupcake build.
Click to expand...
Click to collapse
The CPU won't set to anything else, unfortunately (if you set it to 500 for example nothing actually happens).
Sweet.. looking for something like this.
Works great
Faster Open Home load and no longer lags as much.
THANKS!!
Great app !!
Simple and efficient, the best cloacking app for Haykuro IMO. Just a question : how to keep the cpu running at 528 after reboot?
I know this may not be included in your app right now but I think with a script it might be possible. Any idea?
Thibaud
Thibale said:
Great app !!
Simple and efficient, the best cloacking app for Haykuro IMO. Just a question : how to keep the cpu running at 528 after reboot?
I know this may not be included in your app right now but I think with a script it might be possible. Any idea?
Thibaud
Click to expand...
Click to collapse
I'm kind of reluctant to add that feature because if someone's processor can't handle 528MHz I'm afraid peoples' phones will crash every time they start up forcing a wipe.
It has issues with Shake Awake app, everytime single time all day long shake awake forces close when I use SetCPU. Im I the only one with this issue?
Lakers3408 said:
It has issues with Shake Awake app, everytime single time all day long shake awake forces close when I use SetCPU. Im I the only one with this issue?
Click to expand...
Click to collapse
Do you have the lock feature "on?" SetCPU will query a file to see if the phone is awake if lock is on.
lol, i actually havent had any issues with the phone locking up at 528Mhz, and im using 1.5. However, I hate taking out the battery cover ( i manage to kill my phone in other ways) so something else to do woulld just be
-adb shell
-reboot
Voltage concerns
I've noticed that when using the 528 MHz setting, my phone freezes quite often, but only when the phone is not charging. When the phone is charging, freezing never occurs. This probably means that the voltage going to the CPU is probably inadequate to power the CPU at that frequency.
No freezing at all for me! Maybe some CPU are more tolerant to O/C than some others. That would explain why HTC/Google currently block the G1 to 384 Mhz max.
I installed Haykuro 5.0.2Hr3 and SetCPU works perfectly fine now. It would not work on my JF 1.42 RC33 build as I mentioned in the other thread for the overclock app. Im wondering if the Power Manger app could of been causing something or if simply 1.5 is better able to handle it. Don't know, I have had 0 freezes with the current setup though. Retro defense runs much better now when I have many towers setup and enemies attacking (on default clock it gets really laggy when the towers are firing) Thanks for the app cool!
SetCPU for Root Users has been updated to 1.1.6.
Reminder: *SetCPU supports all rooted 1.5 builds, including JF, Haykuro G/H, the Dude's, etc.
Pressing the "Menu" button allows you to read the introduction message again and choose your version of Android.
1.5 features only: Various bugfixes and enhancements. Added a green colored maximum/minimum reading to the top.
Android 1.1/1.0 support has been kept, but this feature will no longer be supported because the 1.5 Android OS is already very widespread. Please update to 1.5 as the overclocking is much more stable!
I just made a very quick hotfix to a bug that I found through the app's own max/min readings.
1.1.6a: Fixed a minor bug when some CPU settings required two presses to "Set Frequency" to set.
Hey I was wondering if there's a way to confirm that the phone's processor is actually stepping down to 128mhz. I have the processor set to max at 528 which is great and then step down to min 128 to save battery power. The phone's been idle for only a few hours and I've lost 30% battery. That makes me think the phone's not stepping down.
Pardon the n00b question, but what's the point of 19mhz? Is there any phone that can step down that low? Mine certainly couldn't.
Great app though! Thanks for you hard work.
There was some discussion about the additional energy consumption of the mode switching when the frequency step is too great. Also, idling your CPU too low will result in it stepping up more frequently when demand increases. Basically, if you set the minimum to 384 and max to 528, it may use less battery than setting the lower frequency as low as you have.
ah that's interesting. Another thing that makes me think the phone isn't stepping down is that the "Current Frequency" reading on the setcup screen never changes from maximum.
Does the processor only step down when the screen goes blank?
Could more frequency options besides max at 528 be added? A 428, 458 and 488 would be nice to have extra zip but stay away from the higher clock for battery and stability reasons (if stability is an issue for some).
Thanks
rushless said:
Could more frequency options besides max at 528 be added? A 428, 458 and 488 would be nice to have extra zip but stay away from the higher clock for battery and stability reasons (if stability is an issue for some).
Thanks
Click to expand...
Click to collapse
Only certain clock speeds are actually possible. The ones listed in the program are tested by me to working.
The point of 19.2MHz is to make that speed available. I don't think the phone will ever step down that low (the idle CPU load is more than enough to make it step up 19.MHz) but you can force 19.2MHz by setting both maximum and minimum to it. Be careful though, it's REALLY slow and you might think your phone is frozen.
ah that's interesting. Another thing that makes me think the phone isn't stepping down is that the "Current Frequency" reading on the setcup screen never changes from maximum.
Click to expand...
Click to collapse
Press "refresh" a few times and it might go down (it does for me when set to 528/384). Remember that simply refreshing the speed causes CPU load and might make the phone change the frequency before it is read. Same with reading the CPU Info dump.

[APP][3 May]Voltage Control EX 1.6.0b

I cannot promise that this app will not brick your phone!!
I also cannot promise compatability with any kernels other than existz Onix and kb1 beta kernel!!
Voltage Control EX - An app for managing oc/uv settings on Samsung Captivates
Based heavily on source from xan's Voltage Control App. In fact, this is Voltage Control, just with added features designed primarily for existz's Onix kernel.
Features:
Compatibility with Gingerbread *** See known Issues!!!!
OC/UV settings, identical to the original Voltage Control
Max Clock limit, identical to Voltage Control
Scheduler control, identical to Voltage Control
Updated States enable tab - provides the basic functionality of xan's Voltage Control, with added time in state stats
Added a CPU Threshold settings chooser
Updated About screen, and donate info
Added option to hide/show status bar on main menu
Reorganized main menu, and included a sub menu
Time In States read out in hour:minute:second format with percentages included
Deep Sleep time in state information
Fully implemented reset option, returns all settings, except for scheduler, to stock
Logging enabled, does NOT use logcat
Added log control options to Menu:
-Clear Log clears the log, then restarts logging
-Export Log exports vcex.log to /sdcard
Note: CPU Threshold settings is only available when using Onix kernel by existz!! I think existz plans on adding CPU Threshold support to kb1 beta, but I am not sure, as I am not existz!!
CPU Threshold settings gives you the option to activate one of three pre-defined settings: Performance, Battery Saver, or Stock. These settings adjust when your CPU decides to scale its clock speed up or down, which obviously has an effect on performance and battery life.
Find the app below, as well as the source code.
To install, make sure you have uninstalled previous version!! This version has a new package name, and so will NOT overwrite previous version! If you don't uninstall VC EX 1.0, 1.01, or 1.10, whichever you have, you WILL have two VC EX apps installed!!
Download voltage-control-ex-1.2.0b.apk, save on your computer
Enable usb debugging on your phone, and hook it to computer
Run "adb install path/to/voltage-control-ex-1.2.0b.apk" - where /path/to is replaced with the path to where you saved the apk
Disconnect our phone, and enjoy your new app!
Also, you may download this directly to your phone
To install, use a file explorer, any will work but I suggest Root Explorer, to navigate to where you downloaded the apk
Click on the apk and select yes, install, etc.
NOTE: This method ONLY works if you have rooted your phone, AND enabled non-market apps! Of course, if your phone is not rooted, this app will not work anyway, but you get the point
If you use the app, and enjoy it, please consider donating to my think tank aka beer and pizza) fund!!
Report any issues you have on this thread or by sending me a private message. Make sure to include your system setup in any issue reports, such as kernel and rom versions. Your feedback and bug reports help me know what to fix! And as always, check the thread to make sure someone else has not posted the same issue. If they have, just quote it and let me know your system setup.
Note on reporting issues!! PLEASE READ!!!
All bug/issue reports need to be addressed to [email protected]. Please select "Menu > More > Export Log" from within VCEX and include the vcex.log file with your bug report!
Known Issues:
Please read this section if you are having an issue!!
If your issue is here, I already know about it and I am working on it!
In Gingerbread, States tab does not show up occasionally, restart app and it SHOULD work, if not, try again
This issue has also been reported on FroYo!!
NOTE: If you launch vcex several times in a row (i.e. more than 5) with no States tab, please let me know. The issue is caused by the ShellInterface used to get info from the kernel not liking the states_enabled_table file for whatever reason. Typically, the issue will show up on occasion, more of a nuisance than anything. However, if it consistently does NOT show States tab, I want to know about it!
Changelog:
1.6.0b:
Fixed (sort of, see Known Issues above) issue with States tab not showing in Gingerbread
Added app-hosted logging
Added options to menu for clearing and exporting log file
1.5.0 FINAL:
Identical to 1.4.0bRC, except debuggable is set to false.
NOTE: If you are using GingerBread, do NOT use 1.4.0 or 1.5.0!!
They DO NOT WORK with GingerBread!!
I am working on a full rewrite designed for existz's Talon GB Kernel
Until I release it, use VCEX 1.3.0 or earlier!!
1.4.0bRC:
Changed States drawer layout to "TIS: hh:mm:ss | pp%"
Added reset option, will restore settings to stock, except for Scheduler settings
Changed Max CPU Dropdown to only include enabled states
NOTE: If you like this version, let me know!! This is my release candidate, and aside from any bugs found, I will not be adding anything else!! If this version proves to be stable, I will re-release it as 1.5.0 FINAL!
1.3.0b:
Changed States drawer layout to always include percentage, new layout is "TIS: hh:mm:ss pp%"
Fixed CPU Limit settings. If max cpu is set to 400mhz, it will show 400mhz in the spinner, instead of 1400mhz. The same goes for 600mhz and 1600mhz and 200mhz and 1200mhz
Added code to make Show/Hide Status Bar "sticky." This means it will save your full screen preferences so that if you want it to be in full screen mode, it will set it up at launch
1.2.1b:
Fixed version as shown in About screen, thanks to iXNyNe for pointing it out!
Changed "Visit us on XDA" button on About screen to reference this thread
Changed "More Info" button on "No Root Page" to come here
Changed "Get kernel from XDA" button on "Wrong Kernel" page to reference Onix kernel, since this is built for Onix.
1.2.0b:
Changed package name to com.shane87.voltagecontrolex
Consolidated the Show/Hide Status Bar option into one button
Added an option to toggle percentage of time in states/ time in states
Changed time in states readout, when selected, to hour:minutes:seconds format
Added a readout for Deep Sleep state
1.10b:
Fixed saving CPU Threshold settings for bootup. Will now overwrite CPU Threshold settings applied through Onix Recovery.
Added Hide Status Bar and Show Status Bar options to main menu.
Reorganized main menu, including a sub menu.
Menu>About is now located at Menu>More>About
Menu>Reset is now at Menu>More>Reset
Menu>Exit is now at Menu>More>Exit
Note that Menu>More>Reset is still not implemented yet!!
1.01b:
Fixed a minor bug that prevented the app from hiding CPU Threshold Settings when they are not supported by your kernel
1.0b:
Inital release.
[EDIT]This will be going on Android Market, but first I have to come up with the registration fee![/EDIT]
A HUGE thank you goes out to xan, for his ground work that this app is based on, and to existz, for writting the awesome kernels this is designed for, and for pointing me in the right direction on this project.
And of course, an ENORMOUS thank you to everyone who uses this app, and especially to those who report bugs/issues. Your reports are how I know what is broken and needs fixing!!
Note that I took down the old versions due to making this final. The only old version I left is 1.3.0, as it is the latest release that works with GingerBread!
If you want other releases, pm me, I would be more than happy to forward them to you!
awesome!
cant see time of state 100mhz though. if status bar were hidden while app was open it would give that little extra.
Must un-install regular Voltage Control for install to complete. For the best though.
Scheduler is blank with no options in the drop down menu for me.
Trusselo said:
awesome!
cant see time of state 100mhz though. if status bar were hidden while app was open it would give that little extra.
Must un-install regular Voltage Control for install to complete. For the best though.
Click to expand...
Click to collapse
Hmm, thats odd, as on my Captivate, which I did all of my testing on, the time in state for the 100Mhz state was visible. I know I had that problem on previous builds, but finaly got the layout to work for me. I will look into hiding the task bar to get the extra room for the states to show properly. I am working on a new build anyway, as the cpu threshold settings does is not properly hidden, plus I forgot to have it remove any existing cpu threshold settings when it finds the kernel does not support cpu threshold. Of course, the only time that would be an issue is when changing from a cpu threshold enabled kernel, such as Onix, to a kernel without cpu threshold, such as kb1 beta. Anyway, I hope to have a new version up tonight or tomorrow at the latest.
wonner said:
Scheduler is blank with no options in the drop down menu for me.
Click to expand...
Click to collapse
Hmm, thats odd. Does the original Volatage Control work with your kernel? If it does, I can't understand why the Scheduler settings wouldn't load, as I made no changes to the Scheduler settings implementation. As far as any other feature, and the app in general as well, I can't promise compatibility with any kernels other than those created by existz, and at this time I can't even promise compatibility with suckerpunch-voodoo by existz, as I have done no testing with sp-voodoo yet.
Scheduler shows fine for me
Sent from my SAMSUNG-SGH-I897 using XDA App
shane87 said:
Hmm, thats odd. Does the original Volatage Control work with your kernel? If it does, I can't understand why the Scheduler settings wouldn't load, as I made no changes to the Scheduler settings implementation. As far as any other feature, and the app in general as well, I can't promise compatibility with any kernels other than those created by existz, and at this time I can't even promise compatibility with suckerpunch-voodoo by existz, as I have done no testing with sp-voodoo yet.
Click to expand...
Click to collapse
Yes, I uninstalled VC 3.0.3 to install your app and scheduler was working fine. Regardless, I uninstalled VC EX and reinstalled it and scheduler is working fine now. I am using Onix, I was just too lazy to change my sig.
Great app BTW!
wonner said:
Yes, I uninstalled VC 3.0.3 to install your app and scheduler was working fine. Regardless, I uninstalled VC EX and reinstalled it and scheduler is working fine now. I am using Onix, I was just too lazy to change my sig.
Great app BTW!
Click to expand...
Click to collapse
Awesome, I'm glad it is working for you now!! I understand about being to lazy to change your sig, I am back on kb1 for now, but I ran onix for about 4 days while testing this app, and never changed my sig. Quick question, can you see the time in state for the 100mhz state? I am planning on a release of the next version, a minor update, tonight or tomorrow. All I am changing in the update is hiding the status bar, cuz someone reported being unable to see the 100mhz time in state, and I have fixed the code to remove the cpu threshold spinner for kernels that don't support it.
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: eXistZ kb1 beta #8, Voodoo Sound v7, Voodoo Color, Voodoo lagfix
Modem: I897 UCJJ4
HW Build Number: 1101
Running continuum and latest onix everything works fine and I can see everything.
Sent from my SGH-I897 using XDA Premium App
shane87 said:
Quick question, can you see the time in state for the 100mhz state?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awesome! I'm glad most of you are having good results with this app! For anyone who is not seeing the time in state for 100Mhz, I am adding the code to hide the status bar, just to give it a little extra room. And I may add an option to switch whether it hides the status bar or not, but I haven't decided yet. I personally like seeing the status bar, but that is simply my opinion. Either way, I will definitely have a new version up some time tonight, as I had to go back and fix a little bug I found. Due to the way I wrote the code for implementing the CPU Threshold spinner, it should have disabled the spinner and hit it if you were running a kernel without CPU Threshold support, but I made a small mistake that proper debugging would have picked up. I have it fixed now, so I will post the new version soon, after I tinker around with hiding the status bar.
Just uploaded 1.01beta! This is a minor update, as all that I changed was how the app checks for support of CPU Threshold settings. This change allows the app to hide the CPU Threshold settings options on kernels that do not implement CPU Threshold settings, such as existz kb1 beta kernel. I am looking into adding an option to make the app full screen, thus getting a little more room on the display for anyone having difficulty seeing the 100Mhz time in state. However, I have been up for 28hrs+ so my mind is not at its best! I will, hopefully, get some work done on this tomorrow. Till then, happy modding.
P.S. For those wondering, I left the original apk up, as the update, 1.01b, only really affects users who do NOT have Onix kernel installed. Plus, I haven't tested the update against Onix kernel yet, as I said above, lack of sleep makes things fuzzy, and I try not to flash when fuzzy. When I get a confirmation, preferably from a few users plus my own tests, that the new version does indeed work on Onix, I may remove the old version.
Ok, so I have been awake for entirely way to long, but before I retire for the night, I realized that neither version of the app had been zipaligned. So I took down the files posted before, renamed everything in a uniform matter, zipaligned both apks, and reposted them. If you have either version installed, you should re-download it, as they run slightly smoother after zipaligning. Nighty night xda! And to everyone, especiall the devs and rom cookers, keep up the good work!
So far, so good.
hmm having trouble with the state when i use cpu spy the there are only 3 available state 800 1000 1300, but when i check on the voltage control ex the other state are check, so im confuse now can someone explain it to me clearly why the other state doesnt show up on cpu spy app? does that mean the other state is not working even its check? And also i cant get the threshold to stick to performance whenerver i try to reboot it always go back to battery saver, im using onix nighty the latest
sinichi21 said:
hmm having trouble with the state when i use cpu spy the there are only 3 available state 800 1000 1300, but when i check on the voltage control ex the other state are check, so im confuse now can someone explain it to me clearly why the other state doesnt show up on cpu spy app? does that mean the other state is not working even its check? And also i cant get the threshold to stick to performance whenerver i try to reboot it always go back to battery saver, im using onix nighty the latest
Click to expand...
Click to collapse
Hmm, that's very odd. I have checked against cpu spy, and I am seeing the same states enabled in cpu spy as I am in VC EX. Do you have a terminal emulator? If you do, could you run the command
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
and give me the output? As far as it not saving the threshold settings, have you saved boot settings? If you don't save boot settings after a change to the Threshold settings, it will not copy the right script over to /etc/init.d
the problem might be with larger check boxes or fonts in my rom/theme
shane87 said:
Hmm, that's very odd. I have checked against cpu spy, and I am seeing the same states enabled in cpu spy as I am in VC EX. Do you have a terminal emulator? If you do, could you run the command
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
and give me the output? As far as it not saving the threshold settings, have you saved boot settings? If you don't save boot settings after a change to the Threshold settings, it will not copy the right script over to /etc/init.d
Click to expand...
Click to collapse
my frequency is showing now on the cpu spy it's just seems to load slow maybe in 3 mins every states will show from the time or your first boot, but my threshold still wont stick to any of it if i enable the tweak on onix my threshold will be on performance but when i try to save it on battery save and save on boot while the tweak of onix is on after a reboot it will return to performance. but when i disable the cpu tweak on onix it wil stay on battery save and when i save it on performance after a reboot it will stick on battery save. It still depends on the onix setting I think sorry for the bad english I hope you get it
Trusselo said:
the problem might be with larger check boxes or fonts in my rom/theme
Click to expand...
Click to collapse
Yeah, it looks like your rom/theme has latger checkboxes. I am running Cog4.3 with the stock theme. Don't worry, I am working on adding a hide status bar option to the main menu, hopefully today I will have it ready for release. I also have another issue I am working on as well, that may take a little figuring to fix, but I hope to have a new update sometime today.
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: eXistZ kb1 beta #8, Voodoo Sound v7, Voodoo Color, Voodoo lagfix
Modem: I897 UCJJ4
HW Build Number: 1101
sinichi21 said:
my frequency is showing now on the cpu spy it's just seems to load slow maybe in 3 mins every states will show from the time or your first boot, but my threshold still wont stick to any of it if i enable the tweak on onix my threshold will be on performance but when i try to save it on battery save and save on boot while the tweak of onix is on after a reboot it will return to performance. but when i disable the cpu tweak on onix it wil stay on battery save and when i save it on performance after a reboot it will stick on battery save. It still depends on the onix setting I think sorry for the bad english I hope you get it
Click to expand...
Click to collapse
I just did a reboot to see if performance or stock would stick on mine at reboot, and it is defaulting to battery saver as well. I think it has something to do with the way existz has the cpu threshold settings applied by the kernel at boot-time. I am working on fixing this as we speak, as well as adding the hide status bar option mentioned in my last post. Hopefully I will have something for release today that addresses both issues. As far as the threshold settings not sticking at boot, just re-apply them after boot and they will stick, untill next boot anyway. And I knew about the threshold settings defaulting to performance when the threshold tweak was activated on onix, I meant to add a note in the op about it, but it slipped my mind. Like I said, I hope to have this fixed today. Until then, just make sure to open vc ex and re apply your settings after a boot. Keep up the good work everyone, and let me know about any and all issues. That's how I know what needs to be fixed to make this app as good as possible!!
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: eXistZ kb1 beta #8, Voodoo Sound v7, Voodoo Color, Voodoo lagfix
Modem: I897 UCJJ4
HW Build Number: 1101

[APP][OC/UV/Governor][GPU OC][GB][21 June]Control Freak 0.5beta (NEW!!)

Control Freak, the OC/UV app for Gingerbread!
PLEASE READ THE FULL POST! !!
NEW RULE! Read the ENTIRE op, plus the last few pages BEFORE posting a question!! I don't mind sharing information and helping people, but answering the same question on every page is getting old!!
Control Freak is a re-write of xan's Voltage Control app, designed to work with Gingerbread based kernels. It has (most of) the features of my Voltage Control EX.
Beware!! This app is still in development! Any issues are being worked on, but it may not run perfectly!! Also, I, nor anyone who has helped to make this app or the kernels/roms it works with are responsible for any damages caused by use of this app or any kernels/roms supported by this app!!
Features:
Designed for use with JVx based Gingerbread kernels
Works with cm7 kernels that support OC/UV
Specifically designed around features present in existz's Talon kernel
Allows enable/disable specific states
Allows undervoltage control on a state-by-state basis
Allows limiting clock to a specific speed
Allows changing of governors
Allows control of Cpu Threshold settings - see note2 bellow.
States enabled info is found by opening each UV control.
TIS info is now shown on the main screen
TIS info for Deep Sleep
TIS percentages
Logs all major start up values as they are polled from the sysfs.
Logs all settings to be applied when Apply is selected
Logs all settings to be saved when Save As Boot is selected
Controls GPU Clock settings on compatible kernels!!
GPU O/C Capable Kernels for Captivate:
Talon 0.3.1 by eXistZ -Released to public
Le Kernel du Jour by TheEscapist - CM7, may be only available on private test versions, talk to TheEscapist for more info
Glitch Kernel by glitch - CM7, may be only available on test versions, talk to glitch for more info
Note: On Gingerbread, the conservative governor is NOT recommended! Interactive/ondemand/smartass governors are supported, and interactive is the preferred governor! Talon does not have smartass implemented yet, so smartass will not show up in the Governor dropdown on Talon.
Additional Note: As of Talon 0.2.1, interactive governor is NOT included anymore! Existz removed it in favor of the ondemand governor.
Note2: Cpu Threshold control is NOT supported on most Gingerbread kernels, since Cpu Threshold is used by conservative governor. I just added the Cpu Threshold settings, so that I can make this backwards compatible with FroYo kernels/roms.
NOTE 3:If you are experiencing issues with settings not sticking on reboot, go to the Market, download the busybox installer by stericson, and install busybox 1.17.1. Some roms, including Perception II, have a version of busybox 1.18.4 that does not have run-parts compiled into it. Without run-parts, nothing in /etc/init.d gets loaded at boot. The version of 1.17.1 included in stericson's busybox installer DOES have run-parts, so it will work.
Change log -
Control Freak 0.5b:
- Added GPU Overclocking controls! Please note that your kernel must support GPU Overclocking for this feature to work! Also note that this version has NOT been tested on kernels without GPU Overclocking, so if anyone has a kernel that does not have GPU Overclocking, test this out and let me know how it goes!!
- Fixed the states enabled command to remove the extra 0 at the end that was being added due to Deep Sleep info
Control Freak 0.4.2b:
- Fixed fc issue on kernels with higher number of states available
- Changed the icon, the new icon was designed by b_randon14
Control Freak 0.4.1b:
- Fixed save function, now the proper max frequency is written to S_volt_scheduler
- Added logging to save function
- Added logging to apply function
- Log is now cleared when it is exported, so the log starts from scratch after each export
Control Freak 0.4b:
- Added Deep Sleep TIS info.
- Added TIS percentages.
- Added logging
- NOTE: Logging DOES NOT use logcat, so there is no need to enable logcat to generate logs, or to view/export the logs.
Control Freak 0.3.5b:
- Fixed the Max Frequency issue where any changes to the Max Frequency dropdown were not being saved. Now it writes the proper value to the proper place.
- Fixed another issue with Max Frequency dropdown. If you applied a Max Frequency LESS THAN the highest state enabled, on closing and restarting CF, it would show the highest enabled state as the max frequency, regardless of current setting. Now, if you set limit to 1000MHz, it will show 1000MHz at launch, no matter how many states above that freq that are enabled.
- Fixed the SI unit prefix for frequency. Forgot that 'm' is for "milli" and 'M' is for "Mega." And I was even arrogant enough to tell someone that I was right!!! Anyway, it is fixed now. And a HUGE thank you to aalh for pointing out my mistake!
Control Freak 0.3b:
- Fixed the TIS info issue. Now each state shows it's own TIS, instead of the
the TIS for the first state.
- Moved the TIS info to the main screen, so that it is visible all the time.
Control Freak 0.2b:
- States info issue resolved
- Unsupported kernel issue resolved (Same underlying cause as the states info issue)
Control Freak 0.1b:
- Initial Release
Known Issues -
- Sometimes, gpu read out will disappear for some states at random. If you open the uv/gpu controls, it will show the read out again. Closing the controls may cause that state's readout to stay and cause other states to loose their displays at random. May have to do with a glitch in the code to hide gpu controls for non-gpu compatible kernels.
- Sometimes it will not pull states_enabled_table info. This causes the CPU Limit dropdown to be empty. As an interim solution, until I can track down why this is happening, either exit Control Freak and launch it again, or simply enable each state, and they will be added back to the dropdown.
- Occasionally will report an unsupported kernel. If you are sure your kernel IS supported, simply restart.
Sources available at https://github.com/shane87/ControlFreak
Report any issues by posting IN THIS THREAD or sending me a PM. But please, read through the thread, and check the known issues section of this post before posting an issue. If your issue is listed, quote the original issue report, and add details about your system and set up. "Me too!" comments are not helpful and will be ignored.
Issues may also be reported by sending an email to [email protected] If you use this method to report bugs/issues, please export the log from Control Freak and attach it to the email. To export Control Freak's log, launch Control Freak, press Menu > Export log. The log will be exported to /sdcard/cf.log. Please attach this file to any emails addressed to me using the above link.
NOTE: I removed CF 0.3b due to the number of bugs in that software. Granted, all of them were fairly minor bugs, and primarily affected the UI, other than the Max CPU Limit issue. But with that issue, on top of the inability to enable/disable a state since you couldnt see the checkboxes, ther wasnt a whole lot you could do with 0.3b. Anyway, 0.3.5b takes care of those problems.
I removed CF 0.4b due to the Save errors, 0.4.1b has the same functionality, and it works right!
A HUGE thank you and shoutout to b_randon14 for designing the new icon!
Keep up the good work!!
If anyone has a Samsung Intercept, or knows anyone with a Samsung Intercept, check out bROM over at sdx, a deodexed, rooted rom designed by my brother, b_randon14!
Anyone interested in contributing, drop me an email at [email protected], and I will get you added as a contributor on github!
Reserved +++
I know its still in development but with JVH out and existz already working on a JVH talon build (continuum rom has it for now), you might have to implement that too.
grkmaster said:
I know its still in development but with JVH out and existz already working on a JVH talon build (continuum rom has it for now), you might have to implement that too.
Click to expand...
Click to collapse
Yeah, I am aware of JVH, and I plan on adding JVH compatibility as soon as existz's begins to release JVH-based kernels. Actually, as long as the sysfs is still implemented the same way, there SHOULDN'T be any issues. Of course, I thought the same thing about going from FroYo to to Gingerbread, and it wasn't quite that easy. But compared to the full re-write, which has taken almost three weeks, going from JVB to JVH shouldn't be as bad.
Anyone interested in looking at the sources on github, I have committed fix that prevents the app from fc'ing at launch. As it turns out, calling the inflater function to inflate a view does NOT save that view unless you specifically tell it to! Seriously though, it was a simple issue of forgetting to add a word or two of code. It is amazing how one messed up variable, or even a missing period, can complete crash an app. Now, just to get the layout setup so that everything is visible and positioned correctly.
Hopefully, I will have a running release ready by the end of the day.
P.S. If you intend to DIVIDE by 1000, and you accidentally put SUBTRACT 1000, Java/Android won't tell you that you are an idiot. It will just cause the app to crash, lol.
Release
Control Freak is live!!
Please read the OP, especially the known issues section.
Using this app right now! Let's see how it goes! Im accutally excited cause I don't really like setcpu or voltage control
Sent from my GT-I9000 using XDA App
will this app also work with cm7 gb or just the i9000 ones
superj3211 said:
will this app also work with cm7 gb or just the i9000 ones
Click to expand...
Click to collapse
I do not know. I don't have cm7 installed, and have not tested it against cm7. If cm7 implements oc/uv in the sysfs like Talon does, it SHOULD work, but again, no guarantees.
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
Anyone interested in designing a new icon for Control Freak? I have zero graphics design abilities, and would seriously appreciate if someone could design a nice icon. I will give a bounty of $5 US to the best design!!!
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
Cool. Something new to play with.
sent from my cappy rocking gingerbread (CM7)
shane87 said:
Anyone interested in designing a new icon for Control Freak? I have zero graphics design abilities, and would seriously appreciate if someone could design a nice icon. I will give a bounty of $5 US to the best design!!!
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
Click to expand...
Click to collapse
If i had any design ability Id help out but just like you they suck lol ..
Hope someone helps out since there is plenty of great graphic designers aroud here
Control Freak does not seem to pull up the states table at all under TalonDEV 0.1.7-JVH-Test_11 for Continuum, but Voltage Control EX does it most of the time.
Sent from my GT-I9100 using XDA App
rajendra82 said:
Control Freak does not seem to pull up the states table at all under TalonDEV 0.1.7-JVH-Test_11 for Continuum, but Voltage Control EX does it most of the time.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Read the OP. Control Freak does not use the States tab. If you press on the state, like you are going to change uv settings, it will show the enable/disable checkbox and the tis info.
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
shane87 said:
Read the OP. Control Freak does not use the States tab. If you press on the state, like you are going to change uv settings, it will show the enable/disable checkbox and the tis info.
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
Click to expand...
Click to collapse
Sorry. I missed that at first.
shane87 said:
Read the OP. Control Freak does not use the States tab. If you press on the state, like you are going to change uv settings, it will show the enable/disable checkbox and the tis info.
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
Click to expand...
Click to collapse
I think its a great alternative way and possibly keep it that way. State tab shuoldnt be that big oa deal if we have a option like that to enable and disable a checkbox under the states
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
iXNyNe said:
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
Click to expand...
Click to collapse
Yeah, I am planning on adding tis info, plus an indicator for enabled/disabled status on the line with the uv, so you can see everything in one glance.
I knew that the states info still isn't getting pulled right sometimes. You said vc lite has that issue fixed? Do you know if vc lite has sources available, so I can see how it got fixed?
I didn't know that the tis was messed up. I'll take a look at it tomorrow and see if I can track it down.
And for future reference, please report issues by clicking the link in the op. I check this thread often, but I check my issue tracker on github more often, usually, lol.
Also, I am working on adding governor specific tweaks, that will be displayed in a sliding drawer like vcex's states tab.
And an enormous thanks to all who use this app and give me feedback!!
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
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))
Question
Interactive, just sits at 1.2, unlike whatever VCEX did which made it scale (or hop, depending on semantics)

[MOD] IncrediControl - Easy control of voltages and kernel settings!

Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
In addition, if you are an Incredikernel user, the app may also be used to toggle Incredikernel specific features on and off, namely USB fast charging and audio boost.
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work. Most non-stock gingerbread kernels have the HAVS adjustment. Very few sense kernels have the adjustment. I believe ziggy's latest is the only one that does.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
This excites me.
Neat
Sent from my Synergy Rom using Tapatalk
Great chad! Finally an app that does all the work.
Sent from my ADR6300 using XDA App
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
mikeymop said:
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
Click to expand...
Click to collapse
I concur. And will this work on the incredikernel?
J/k on the the question part (because I know someone will take that seriously ). Great work, chad.
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Great thanks!
I know viperboy was working on something similar.
I have to say though your aggressive undervolt package is the tits. It is rock solid for me, and I can't lower anything -25v from there without crashing.
RebelShadow said:
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Click to expand...
Click to collapse
That may come in the future.
@everyone: Anyone try it on other devices that have havs + sysfs interface? Evo, desire?
effing sweet..... no more term emulator for me
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
POQbum said:
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
Click to expand...
Click to collapse
The boxes are unticked on purpose, so that the file is only written when you specify that you want to set the current settings on boot. The other option is to have it ticked when the boot script is found, but then you would have to untick it when you want to just play with voltages (but not change your boot script) and then tick it again to set on boot. Would everyone prefer it that way?
I should also specify that when you tick set on boot, you also must click set in order to truly set it on boot. There is also the option to have it write the file when set on boot is ticked. I just need to know what everyone's preference is.
SDspeed might be added to a future release and would have the set on boot option.
PonsAsinorem said:
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
Click to expand...
Click to collapse
That's because new nightlies overwrite the /system folder where the boot script is stored. I'll probably add a backup option too so you can load the defaults, either that or change over to storing the values in a database and loading them via the app on boot as opposed to the boot script.
Looks cool.
Backup database - yes!
Default set on boot once it's been ticked - yes!
Thanks for this, Chad!
Zeam & Incredikernel
CM7 latest Nightly
7/19/2011 - Preview 3:
Changes include:
Added +/- All Min and All Max buttons
Reordered the + and – buttons to flank the voltages to clean up the layout a bit.
Removed the title bar for more vertical screen space
Next up is feature checking / disabling of functions your kernel doesn’t support as well as voltage checking.
Get it at http://www.incredikernel.com
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
nagasgura said:
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
Click to expand...
Click to collapse
Thanks, I'll add it for the next release.
The + on the Max voltage doesn't display for me.
Love it, fast and simple volt changing.. Makes viperMOD ancient news.

[20130727]CM 10.1+HALO+OpenPDroid+Hardware Customisation

This is completely compatible with the official CyanogenMod 10.1 (and I'm planning to keep it that way), so you can switch to and from official without any problems.
The main focus of this ROM is to stay up to date with CyanogenMod 10.1 git branch and add features that allow finer grain customisation of hardware specific to the 4X.
What's added:
LG QuickMemo (hold Vol+ and Vol- to activate) [framework change]
Enable wake by pressing volume key setting [settings app change]
Control button backlight in System Settings (can stop it turning on whenever you touch the screen) [settings app + framework + hardware library change]
Button backlight used as notification light (can be enabled/disabled in System Settings) [settings app + hardware library change]
Button backlight used as battery light (recommend disabling in System Settings) [settings app + hardware library change]
Ability to dim backlight more than minimum (activate from ArararagiToolbox, otherwise like stock) [kernel change]
Ability to force fast charge even higher than default AC levels (activate from ArararagiToolbox, otherwise like stock) [kernel change]
20130502: Fix headset button (thanks to Wenque) Now in official CM
20130505: Disable baseband_xmm_power wake lock [kernel change]
20130512: Torch brightness control. You need to clear data for the Torch app. Default is the minimum possible brightness, rather than the stock CM 10.1 brightness. [Torch app + kernel change]
20130515: Fix known issues in torch brightness control caused by 20130512 changes. Clear Torch app data. [Torch app change] Disable touch debug printing in kernel. [kernel change]
20130602: Use new vibrator implementation in line with CM. Add baseband_xmm_power wake lock back in.
20130609: Uncap screen brightness
20130611: Disable baseband_xmm_power wake lock again. Now using Linaro 13.05 GCC 4.7 to build (user + kernel).
20130612: HALO ported from ParanoidAndroid
20130613.1: OpenPDroid
20130623: Enable ODEX
20130623: Use -O3 for compiling native components
20130623: Increase vibrator PWM duty cycle (should increase vibrator strength)
20130625: Tweak background process parameters
20130630: Add QuickMemo quick settings tile
20130707: Add LG Hidden Menu (only GNSS Test works at the moment)
20130713: Allow control of which backlight HVLEDs are enabled. Lets you make the screen even dimmer
20130716: Allow control of gamma LUT from user space. Let's you over saturate the screen colours
20130727: Add support for external GPS (http://review.cyanogenmod.org/#/q/owner:ich%40morphew.de+status:open,n,z)
Check github for full changelog. Each release also includes changes from official CM.
Optional (can be installed as normal app):
Memobin.apk: LG Notes
AraragiToolbox.apk: Actually activating some of the features mentioned above
CameraApp3.apk: 20130606. LG Jelly Bean stock camera app ported to Android 4.2/CM 10.1.
ArararagiToolbox features that work on any ROM:
Check battery current (drain/charge in mA)
Disable USB (for charging on untrusted computers)
Check KSM (kernel same page merging) stats
Note: Anything changed from AraragiToolbox won't stay across reboots, as it's more of a tool for testing. I'm planning to add them into the System Settings later on.
Install by flashing zip from ClockworkMod (Find "Optimus 4X" on the page). No need to wipe data if you are already using CM 10.1.
Download: cm-10.1-20130727-UNOFFICIAL-p880.zip (md5sum: 99d7acca2d33fcdac8c6faed57f44f0b)
Source: https://github.com/mzhou/arararagi_lge_p880_patches
Planned:
Overclocking, Schedulers, I/O Schedulers, Governors
Vibration strength Make it configurable
Control camera flash/torch brightness
USB mass storage
Fast charge tile
How to HALO:
See http://forum.xda-developers.com/showthread.php?t=2117444&page=976 (Thanks to kubics for original posting and Namor Noditz for linking) on how to configure.
Just mentally replace "Settings > RootBox Settings > HALO Settings" with "Settings > System".
This YouTube video goes through all the gestures: http://www.youtube.com/watch?v=d5WljHcOyXs
can we install only the APK files or we have to flash the unofficial Cm10.1?
donkanmcklaus said:
can we install only the APK files or we have to flash the unofficial Cm10.1?
Click to expand...
Click to collapse
The ROM is needed as it is modded to support the features
Sent from my rooted P880
What happened if I flash official CM10.1 nightly update over it?
LGaljo said:
What happened if I flash official CM10.1 nightly update over it?
Click to expand...
Click to collapse
My immediate guess would be the same as with any modified CM - you lose the additions to the ROM.
SimonTS said:
My immediate guess would be the same as with any modified CM - you lose the additions to the ROM.
Click to expand...
Click to collapse
I think it would change just the moddified files, I guess. I will try an report.
can create a zip file to add QuickMemo, Fast Charge, Backlight Dim, Notification Light, etc. to official CM 10.1?
Black_X said:
can create a zip file to add QuickMemo, Fast Charge, Backlight Dim, Notification Light, etc. to official CM 10.1?
Click to expand...
Click to collapse
+1 i think that will better ... now we will have mess official CM ... and this great fixes ... lot of things to monitor.
LGaljo said:
I think it would change just the moddified files, I guess. I will try an report.
Click to expand...
Click to collapse
It doesn't work. I have installed today's update then this modded ROM and then today's update again.
How often is you going to be updated this ROM?
LGaljo said:
What happened if I flash official CM10.1 nightly update over it?
Click to expand...
Click to collapse
SimonTS said:
My immediate guess would be the same as with any modified CM - you lose the additions to the ROM.
Click to expand...
Click to collapse
LGaljo said:
I think it would change just the moddified files, I guess. I will try an report.
Click to expand...
Click to collapse
LGaljo said:
It doesn't work. I have installed today's update then this modded ROM and then today's update again.
How often is you going to be updated this ROM?
Click to expand...
Click to collapse
Does that mean it did what I suggested and wiped out the additions? That's certainly what used to happen with older versions of CM and I would expect exactly the same to happen still.
It's the same as with the PDroid version - unless the OP sets up his own automated build system you can often find the build lagging behind the nightlies. That's why they often choose to base a modded version on the most recent 'stable' CM and then have to update it less frequently.
I think I found a bug. When I am charging my phone over USB or AC the button's lights are always on.
LGaljo said:
I think I found a bug. When I am charging my phone over USB or AC the button's lights are always on.
Click to expand...
Click to collapse
That's not a bug. You've got the screen set to "Always On" when charging, and the buttons set to "Always On" - therefore the buttons will always be on when charging?
Awesome!!!!This is what i need.Great job!
If qmemo can also turn on by long press menu/quick setting panel,that will be perfect.
LGaljo said:
I think I found a bug. When I am charging my phone over USB or AC the button's lights are always on.
Click to expand...
Click to collapse
The button lights function as battery lights by default. Disable it in settings -> system -> battery lights.
It's difficult to release just modified files (as you can see from my kernel and other QuickMemo thread, it becomes a mess) and now that framework modifications are involved, it can cause conflicts if they are flashed over a CyanogenMod version that it wasn't designed for.
It might be possible to get the button backlight feature upstreamed in CM, but I doubt they'd accept any of the rest.
I'll look into setting up automated build, and also getting the source modifications organised on github or similar.
20130428 is now available.
No changes from me, just updating upstream.
Well nothing changed after I flash this rom. Still cant use the Quickmemo
never_comeback said:
Well nothing changed after I flash this rom. Still cant use the Quickmemo
Click to expand...
Click to collapse
What happens when you try to use it?
Did you hold vol+ and vol- at the same time?
arararagi said:
What happens when you try to use it?
Did you hold vol+ and vol- at the same time?
Click to expand...
Click to collapse
OK I did it, thank you so much. Great effort :good:
Awesome, exactly what I've been looking for, thanks!
20130429 uploaded. Still no changes from me.
I'm thinking of adding an accelerometer spoofer since I'm sick of apps being smart and rotating themselves when I'm uesing my phone on protrait lying in bed.

Categories

Resources