Related
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.
Check out the review by Blair at GizmoNinja! Droid X ROM Review, rubiX ROMs! Updated 12/26/2010 NEW rubiX ROM 1.9.5 Release!!
YOU MUST BE ON 2.3.340 OTA FOR THIS TO WORK
ALSO NOTE: IF YOU INSTALLED THE NEW TRANQUILITY, THE TOOLBOX WILL INSTALL UNLESS YOU SBF BEFORE INSTALL. THIS IS TRUE FOR ANY ROM, NOT JUST RUBIX.
IF YOU USED THE NEW SCRIPT, YOU MUST REBOOT AFTER INSTALL AND INITIAL SETUP
This script runs on first boot to scan the SDCard rubiX Folder for apps. If they are there, it copies them to /data/app and corrects their permissions. Reboot for this to take effect.
YOU MUST wipe data before install.
Change Log for 2.0:
* Sysctl.conf adjustments:
Changed vm.dirty_background_ratio to 70 from 60
* Added rm /dev/log/main for extra performance/free memory
* Changed NO_NEW_FAIR_SLEEPERS to NO_FAIR_SLEEPERS; this was a typo, as there are no new fair sleepers in the dx kernel already.
* Cleaned up the /system/app folder
The following market apps were further removed:
Talkback
Kickback
Soundback
* Added new Interactive and Conservative kernel scaling governors (credit Milestone team)
This is a Droid X first. These two governors bring a big difference to the table; here is what they do:
(Credit Cyanogenmod GITHub for this, source is here: https://github.com/CyanogenMod/cm-k...60f39120/Documentation/cpu-freq/governors.txt)
Interactive:
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a workqueue context, the 'interactive' governor does this in a timer context, which gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.
Conservative:
The CPUfreq governor "conservative", much like the "ondemand"
governor, sets the CPU depending on the current usage. It differs in
behaviour in that it gracefully increases and decreases the CPU speed
rather than jumping to max speed the moment there is any load on the
CPU. This behaviour more suitable in a battery powered environment.
The governor is tweaked in the same manner as the "ondemand" governor
through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be
increased and decreased smoothly by. By default the cpu frequency will
increase in 5% chunks of your maximum cpu frequency. You can change this
value to anywhere between 0 and 100 where '0' will effectively lock your
CPU at a speed regardless of its load whilst '100' will, in theory, make
it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand"
governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
Basically, this means more speed and battery life control
* Adjusted 01cpu for a better sampling rate if the new conservative governor is found.
* Added script: gov
gov allows you to control which governor you use; ondemand, conservative, or interactive. The function is:
gov -ondem for the ondemand governor
gov -cons for the conservative governor
gov -inter for the interactive governor
Alternately, these can be changed via SetCPU or Droid Overclock.
To remove data throttling, click this:
http://www.droidforums.net/forum/dr...-9-7-back-better-than-ever-3.html#post1228193
Credit to Plower.Net
How to install:
Download
Place on SDCard
Bootstrap Recovery via Bootstrap App
Reboot to Clockwork Mod Recovery
Wipe data/factory reset
Select install from sdcard
Choose zip from sdcard
select rubiXFocused2.0.zip
Select yes
Reboot
Enjoy!
Download:
http://www.mediafire.com/?6s32joduwkwyhwa
Will have a mirror up shortly as well.
If you like my work, please support me going to Google I/O Developer's Conference 2011! All donations received are going towards a plane ticket.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=TYYWQBR78DW7U
reserved for me
drod2169 said:
reserved for me
Click to expand...
Click to collapse
what this says ^^^^
Hey drod, thanks for the new release! Will def give this a try!
Sent from my DROIDX using XDA App
SysAdmin-X said:
Hey drod, thanks for the new release! Will def give this a try!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Is this fo real Rubix Focus 1.9.7 is it only released on here because i can't find 1.9.7 anywhere else ? .
Hey Drod, Keep Bangin em out.Rubix in General Is StR8 up Sik lookin forward to this one!
about to start installing in 2 min
Got my Approval bruh..Bring on Tron Theme..LOL
d/ling now. Can't wait to try it. Thank you for bring the art of the DX forward a notch or two!
drod2169 said:
reserved for me
Click to expand...
Click to collapse
jawonder said:
Is this fo real Rubix Focus 1.9.7 is it only released on here because i can't find 1.9.7 anywhere else ? .
Click to expand...
Click to collapse
Yes it's really rubiX Focused 1.9.7
will the themes for 1.95 work on this rom (black jiuce)?
Will this work for the droid 2 ? Since the
Old rubix was said to be working for the droid 2..
Just wanted to say the clock-speed/voltage optimization app is amazing. I get better battery life on RubiX than on any other ROM (and I have tried them all).
This is faster than liberty was for me. Glad I came back to RubiX.
Is there a zip to remove animation and put it back to stock. This is rom is so fast that I hit the quadrant score of 1500 without overclocking. Thxs for a great rom. I tried them all.
Sent from my DROIDX using XDA App
I am going to install this rom tonight. I currently have liberty installed and am happy with it and not having any trouble but unless I try other ones I won't know if I like any others better. I would like to see better battery life and it sounds like I might see it with this rom.
drod2169 said:
ALSO NOTE: IF YOU INSTALLED THE NEW TRANQUILITY, THE TOOLBOX WILL INSTALL UNLESS YOU SBF BEFORE INSTALL. THIS IS TRUE FOR ANY ROM, NOT JUST RUBIX.
Click to expand...
Click to collapse
I was able to permanently get rid of the TranQ Toolbox without SBF. Basically, you just need Root Explorer (or equivalent) to remove all the TranQ files from /data, /data/data, /data/dalvik-cache, /data/preinstall_md5, /preinstall/app, /preinstall/md5, etc. The easiest way is to do a search (at /) in Root Explorer for tranq, and then manually remove them.
Does anybody know how to enable 3 d gallery through terminal emulator. Everytime I try to enable it, it tells me not found. Yes I give it SU permission. It gives me the options either 3d or 2d. I type 3d hit enter, then it tells me not found.
Sent from my DROIDX using XDA App
Never mind I figured it out.
I'm having problems with images showing up as black in any of the galleries or image viewers. Sometimes the thumbnails will display properly, though. In the camera app, if I take a picture and then look at the gallery, thumbnails of images on my sd card will show up, but only one for each picture I took. Pictures taken with the camera never show up. What is going on here and is there a way to fix it? I think rubix is great, otherwise, and would really like to continue using it if the camera and image problems can be fixed.
-------------------------------------
Sent via the XDA Tapatalk App
inokumum said:
I'm having problems with images showing up as black in any of the galleries or image viewers. Sometimes the thumbnails will display properly, though. In the camera app, if I take a picture and then look at the gallery, thumbnails of images on my sd card will show up, but only one for each picture I took. Pictures taken with the camera never show up. What is going on here and is there a way to fix it? I think rubix is great, otherwise, and would really like to continue using it if the camera and image problems can be fixed.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
try swapping to the 3d gallery
type in terminal emulator:
su
gallery -3d
Did anyone by any chance make a flashable zip of the modified services.jar file for this rom for uncapped data? That would be awesome if someone can post it!
Sent from my DROIDX using XDA App
There are a lot of fun, geeky tweaks we can do to these tablets, so I thought I would collect them in one place. It would be great if someone could add this to the sticky at the top of the Dev section. Please add suggestions!!!
User Interface changes:
Voodoo Screen tuning - Hardware level tweaks of the color profile
Display all apps in full screen mode - Force all apps to display in full screen
Hide system bar via power menu - Add function to hide status bar in power menu for ROMs with no framework changes to power-button menu
*Tweak Touchscreen responsiveness - App to change various settings in touch screen.
System Features:
Enable USB Charging - Charge your tab by computer or regular USB adapters
Init.d support - Enable init.d scripts to run at boot
*** Zip align at boot - Align apks at boot for efficient reading
*** V6 SuperCharger - Get V6 Supercharger RAM tweaks working
Monitor android.process.media - Monitor process android.process.media for high cpu usage
Enable ad-hoc Wifi - Enable ad-hoc wifi funtionality
* Set Model to German region code - Allow non-German bought tabs to be CSC (German) region code
* Disable Dolphin Browser collection - Disable excessive browser data collection
*, **, ***Build.prop & init.d Edits - Change boot settings
Mount Network Shares - Mount Network shares on Galaxy Tab
build.prop Tweaks - Long list of changes you can make to your build.prop
Unlock your 3G/4G Tab - Unlock your (at least T-mobile) Tab from a specific carrier
App Changes:
Selectable user agent in default browser - Enable selectable "Desktop" mode in Browser
Force Browser to Desktop - Force Browser to always be in "Desktop" mode
Revert Market to pre-3.2 version - Revert to old market to install all compatible apps (for those having issues installing apps)
Disable Swype license check - Disable the license check for Swype to prevent issues with modified system properties.
Unconfirmed mods from other devices
WARNING! make a backup before testing these as they have yet to be confirmed safe and working on Galaxy Tabs.
Increase speaker/headphone volume - Increase the volume output (Transformer)
Increase volume tweak 2 - Increase the volume output V2 (Transformer)
USB to Ethernet Drivers - Connect to the internet via USB to Ethernet (Transformer)
Change auto-brightness levels - Reduce or increase auto brightness levels to save battery or improve visual appearance (Galaxy S II)
* NOTE 1: Root Explorer has issues with setting permissions correctly in Honeycomb, use ES File Explorer for root file edits. Just go to settings and enable root and mount as R/W
** NOTE 2: Not all of these functions work with the Tab 10.1
*** NOTE 3: May require "Enable Init.d scripts" to function
I was expecting this, thanks m8
It should be sticky thread
Great collection..
Plz put it as sticky, it is perfect.
Sent from my GT-P7500 using xda premium
Great! Sticky is in order here.
This is really good, I'm using some of these features myself so I can attest to it's well-functionality. While I was perusing these threads, I came across a post by reputable developer who said that V6 Super charger causes nothing but problems; If so should I risk it? What are your opinion?
task650 and others pointed out that the ram levels set by v6 are lower than our stock settings. That is v6 was designed for phones with less ram, so the free ram levels are lower than optimum on our tabs. I set them manually with system tuner pro.
Updated to include touch screen tuning tweaks, build.prop & init.d references, and notes
How much RAM does our Tab have guys?
BeNicePlz said:
This is really good, I'm using some of these features myself so I can attest to it's well-functionality. While I was perusing these threads, I came across a post by reputable developer who said that V6 Super charger causes nothing but problems; If so should I risk it? What are your opinion?
Click to expand...
Click to collapse
Personally,i feel the V6 supercharger makes my tab run smoother,less stutter..I'm on KI2, pershoot oc 1.2, v6 update 9.
mark.m.moran said:
How much RAM does our Tab have guys?
Click to expand...
Click to collapse
1 GB
Bus Driver said:
Personally,i feel the V6 supercharger makes my tab run smoother,less stutter..I'm on KI2, pershoot oc 1.2, v6 update 9.
Click to expand...
Click to collapse
I've heard it does other things than just altering the min free values, so maybe that's why task did an about face regarding v6 by integrating it into v1. 1 of 3.2
UPDATE
Added sypwe license check mod, and removedmwarning for v6 supercharger
Nice post
Thks
UPDATE 11/15
* Organized a bit more
* Added some mods from other devices
* Added unlock app
i've figured out the best settings without the supercharger. supercharger may allow multitasking but it makes the system crawl, barely any apps go to cache, app launches are slow etc, AND IT EATS BATTERY LIKE A CANNIBAL on it-self on the ICS beta roms.
what i have done to get incredibly smooth operation is by that i have changed a few and added a few more lines to my build.prop
1) change/add the dalvik.vm.heapsize to 96m from 64m (for lesser multitaskig but smoother apps - i get two apps to multitask with this) or reduce to 48m for more multitasking (i am getting 3 apps multitasking with this 2do, officesuite N email).
2) add MAX_HIDDEN_APPS=1 and MAX_ACTIVITIES=6 (this seems to prevent multiple apps for trying to access the memory and the cpu power at the same time, giving you a better experience, i haven't had any problems with notifications for my facebook, email, pulse n whatsapp)
3) delete the 99supercharger* script from your system/etc/init.d folder
4) i am using the supercharger's bulletproof apps thing for my phone, aNag, phone dialer (option 17) get the ICS services.jar from http://forum.xda-developers.com/show....php?t=1533044 (apparantly its needed to make ICS understand OOM adjustments.
5) go to cwm to clear the dalvik cache or just do superclean-restart with the supercharger script (option 30)
btw, you have to use the DoomLoRD's advanced stock kernel with the stock wifi modules - the doomkernel v4 is superbuggy and unstable. the stock kernel itself doesnt have init.d support for the bulletproofing so you'll need the advanced stock kernel
UPDATE : 5.5) force GPU rendering under developer options in settings.
UPDATE : 6) also add 3 more things via rom toolbox's kernel tweaks for faster launches : vfs_cache_pressure=10 dirty_background_ratio=60 dirty_ratio=95 (i got this from kickasskernelizer) n make em load on reboot. also in kernel tweaks under advanced change up threshold to 75 (higher battery but slower initiations) or 30 (super fast scaling, but lower battery) sampling rate to 200000, powersave bias to 30 (make this 0 for supersmooth, or 60 for more battery life) and i/o scheduler to noop.
UPDATE 7) if you want better multitasking (albeit lesser smooth) apply the superharger OOM+bulletproof launcher settings N lower the screen updates (**** i forgot its name) thing from 200 to 120 (supercharger changes it to 200, which causes lags n a hyper accelerated scrolling)
(I had posted this under JJ's rom, but since its applicable to all ICS beta based roms (out of which i find jj's rom to be the leanest n the meanest) I am posting this here to see what others say about it. also, try his Fold Animations w/buttons (if you like buttons, albeit with a smaller screen area) or my favorite Twister animations.
p.s. devs, please suggest other pros n cons of doing the above.
please press thanks if you like this
I'll try this too.
Thanks
Thanks for the info this weekend I test these things if I can. Looks nice
This is how I setup my rom after flash, and device is working very well with 52 installed apps
1. Configure settings
-Go to wifi and disable scanning always on
-Open mobile network and chose 2G (use 3G only when you need it)
-Go to more and then to mobile broadcasts and disable all (when it enabled, consume RAM)
-configure sound,display, and interface... As you want
-go to accounts and disable sync which you don't need.
-go to About and taping on blablabla, you know to enable Developer options and rom performance.
-Go to developer options set all animations(you have three) to 0.5
-Performance??
-you don't need it, I will show you in next step.
2. Flash this:
L Speed
Or make this manualy
2.1. Install&Configure TricksterMod
-For cpu freq the best is to set device default, like on stock rom, don't forget to press Lock freq.
-Minfree setup
-8mb
-12mb
-17mb
-25mb
-29mb
-33mb
-Syscontrol setup
-Set swappiness to 60
-Set vm.vfs_cache_pressure to 40
-vm.dirty_ratio = 90
-vm.dirty_background_ratio = 70
Set this from tricksterMOD
-CPU freq
The best is
-Min freq
320Mhz
-Max freq
1008mhz
-Scheduler
SIO
-Governor
SmartassV2 or SmartassH3
-GPU freq
-That is your choice min freq will increase battery life, but some laggs is possible, max freq will drain battery faster, but there is less possibility to have lag.
After all don't forget to set run on boot.
3.Install&Configure Greenify
-You already know Hibernate what you want expect Alarm clock, messaging apps, trickster mod, etc.
You already know if you hibernate app with push notifications, you don't get it.
4. Apps
-what about apps??
There is too much apps which user don't use, that apps use ram like other.
Now you need to delete everything what you don't use (live wallpapers, cm wallpapers, etc.) or change apps with some lightweigh, like gallery and keyboard. Download QuickPIC and google keyboard (lollipop themed) {{i will add link later }}
5.build.prop
-leave build.prop to default as much as possible.
-change DPI to device standard, in some reasons my device lag on 200, then I move back to 240 as default. This is for L7.
For L5, there is no line that define DPI, you can skip this step.
-Change ro.max.fling from 4000 to 8000 (don't add ro.min)
-Change vm.heapsize to 64m (I don't go under that, but difference is big from 128 to96 choose between 96 or 64
-Change lowRAM from false to true (you will get little more free RAM).
When you change it to true, you will lose transparent statusbar.
6.init.d
-keep device without any special tweaks, devs which make this rom, they choose the best.
Helpful tips:
-Don't use battery boosters, ram boosters and apps call like that. System do better than one app. There is low memory killer (lmk).
Also this app use ram which you maybe need for something.
Nice tips buddy!
Good job!
Sent from my IdeaTab A2107A-H using Tapatalk
skyinfo said:
Nice tips buddy!
Good job!
Sent from my IdeaTab A2107A-H using Tapatalk
Click to expand...
Click to collapse
Thanks dude
Realy good,i add some of the sets into my rom,thanx!!!
NERDIFIED TILL DEATH!!!
thnx a lot, i hope it all works for me too
since gpu freq is not changing to 245 (for some reason) I decided to stick with 380 because I run ePSXe on my phone
turkiktxhc said:
thnx a lot, i hope it all works for me too
since gpu freq is not changing to 245 (for some reason) I decided to stick with 380 because I run ePSXe on my phone
Click to expand...
Click to collapse
Is device faster???
Everyone who have L7 know speed
-CALIBAN666- said:
Realy good,i add some of the sets into my rom,thanx!!!
I
NERDIFIED TILL DEATH!!!
Click to expand...
Click to collapse
I will post video tonight to see speed of my device
But say me how to post video on xda
Paget96 said:
Is device faster???
Click to expand...
Click to collapse
It's extremely fast at this point, i'm only afraid of it gradually slowing down after days of use
right now, it's really fine
-CALIBAN666- said:
Realy good,i add some of the sets into my rom,thanx!!!
NERDIFIED TILL DEATH!!!
Click to expand...
Click to collapse
Quality is too bad, but.
https://www.youtube.com/watch?v=tm5ay4alFPQ&feature=youtube_gdata_player
Vrh brate
Thank you for these settings
Paget96 said:
This is how I setup my rom after flash, and device is working very well with 52 installed apps
1. Configure settings
-Go to wifi and disable scanning always on
-Open mobile network and chose 2G (use 3G only when you need it)
-Go to more and then to mobile broadcasts and disable all (when it enabled, consume RAM)
-configure sound,display, and interface... As you want
-go to accounts and disable sync which you don't need.
-go to About and taping on blablabla, you know to enable Developer options and rom performance.
-Go to developer options set all animations(you have three) to 0.5
-Performance??
-you don't need it, I will show you in next step.
2. Install&Configure TricksterMod
-For cpu freq the best is to set device default, like on stock rom, don't forget to press Lock freq.
-Minfree setup
-8mb
-12mb
-17mb
-25mb
-29mb
-33mb
-Syscontrol setup
-Set swappiness to 60
-Set vm.vfs_cache_pressure to 40
-vm.dirty_ratio = 90
-vm.dirty_background_ratio = 70
-Gpu freq
-That is your choice min freq will increase battery life, but some laggs is possible, max freq will drain battery faster, but there is less possibility to have lag.
After all don't forget to set run on boot.
3.Install&Configure Greenify
-You already know Hibernate what you want expect Alarm clock, messahing apps, trickster mod, etc.
4. Apps
-what about apps??
There is too much apps which user don't use, that apps use ram like other.
Now you need to delete everything what you don't use or change apps with some lightweigh, like gallery and keyboard. Download QuickPIC and google keyboard (lollipop themed) {{i will add link later }}
5.build.prop
-leave build.prop to default as much as possible.
-change DPI to device standard, in some reasons my device lag on 200, then I move back to 240 as default.
-Change ro.max.fling from 4000 to 8000 (don't add ro.min)
-Change vm.heapsize to 64m (I don't go under that, but difference is big from 128 to96
-Change lowRAM from false to true (you will get little more free RAM).
6.init.d
-keep device without any special tweaks, devs which make this rom, they choose the best.
Only if you want add zipalign.
Click to expand...
Click to collapse
pretty good and usefull tips :good: :good: but if i edit the build.prob i get black screen on boot
Jobloxx said:
pretty good and usefull tips :good: :good: but if i edit the build.prob i get black screen on boot
Click to expand...
Click to collapse
You think bootloop?? Or just black screen??
Anf which device you use?
Dj_Luxor said:
Thank you for these settings
Click to expand...
Click to collapse
no problem
Thanks for using my setup.
Paget96 said:
You think bootloop?? Or just black screen??
Anf which device you use?
Click to expand...
Click to collapse
When i manually edited the build.prop I ended up black screen too, then i tried out the build.prop Editor app, which worked for me.
vangama said:
When i manually edited the build.prop I ended up black screen too, then i tried out the build.prop Editor app, which worked for me.
Click to expand...
Click to collapse
Then ok
@Paget96 really cool! This is actually what I'm trying to do bro and thanks muchly for this configuration tips. I got more infos:thumbup:
Paget96 said:
You think bootloop?? Or just black screen??
Anf which device you use?
Click to expand...
Click to collapse
No blackscreen and i have l7
junephel said:
@Paget96 really cool! This is actually what I'm trying to do bro and thanks muchly for this configuration tips. I got more infos:thumbup:
Click to expand...
Click to collapse
Ok
Thanks for helping.
Added little stuff
Maybe someone use it
Jobloxx said:
No blackscreen and i have l7
Click to expand...
Click to collapse
now working used an editor working great