Develop Bugs

[APP][24Nov] - 4.9 - SGS1+2] Voltage Control - control OC/UV for OC kernels

I take no responsibility for ANY damage / data loss may occur. Use this at your own risk. Beta quality software!/Alpha quality features!
The news:
4.9 - THIS IS HIGLY TEST RELEASE
+ Profiles support
+ Bus frequency switching for Siyah kernel
+ Widget with profile switcher and app launcher (passive!)
+ Recovery instructions: lets you place CWM flashable boot settings deleter
+ CPU history: now can reset and refresh graphs
+ Root detection improvement (I hope...)
Voltage Control Extreme unlock Key on Android Market!
For now features exclusive to Extreme version are:
+ More than two profiles
+ CPU History page
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Click to expand...
Click to collapse
Sources available, project on google code:
http://code.google.com/p/voltage-control/
Look for kernels with this label:
Kernel developers who added VC support please show this image in your topic
{
"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"
}
Uploaded with ImageShack.us
Features:
- minimum/maximum CPU frequency choosing
- selecting IO scheduler
- selecting CPU governor
- changing voltage per frequency
- chosing which frequencies should be used and which shouldnt
- saving settings to be automatically applied at boot (init.d script)
- saving/loading a OC profile
- well designed and highly optimised UI (I hope..)
- robust kernel detection, support of not-so-well-working kernels
- Siyah kernel interfaces (Charging current and GPU OC/UV)
- device info page
- (extreme) CPU usage history page
About donations:
This software is available free of charge.
It cooperates with OC kernel by raspdeep.
It uses some code from: MarketEnabler (Fool your market to make all apps visible!)
If you find this software useful, please consider funding a beer and pizza. There is a "Donate to me" link just over my avatar.
Donator list:
nitr8
kalpik
laststufo
glitterballs
screwyluie
Gembol
Coreym
Thanks!
How to?
Generally idea is simple: make changes to one tab and hit apply. If any changes have been made apply/discard buttons appear on bottom.
The first tab, "General" allows to change Scheduler,Governor/min and max frequencies.
Make changes and click apply
So, you want to pick a maximum/minimum frequency?
Just chose from slider and hit apply.
Governor/scheduler can be choosen by picking from the list, then hitting apply.
You can always discard changes before applying if you want start from loaded settings.
The "Advanced" tab has sliders to control undervolting settings and green/red icons, representing enabled/disabled state.
(green = enabled, red = disabled)
Pick your settings and hit apply, or discard and start over.
Profile support:
If you want to save as boot or as profile, you need to make adjustments and on "General" or "Advanced" tab and then apply them where applicable.
To save as boot -> press menu key, then select "Save as boot settings".
To save as profile -> press menu key, then select "Save profile".
Boot settings are automatically loaded on every device boot.
Profile settings can be loaded by pressing menu -> "Load profile"
Both "boot" and "profile" settings can be deleted from menu.
RECOVERY
If Your device freezes after boot because of too agressive boot settings:
Flash Voltage Scheduler Remover by user Coreym, via CWM. Don't forget to press thanks under one of his posts!
FAQ:
Q: Extreme version?
Yes, I wanted to give some extras for people that support my work.
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Q: What is it?
Its voltage control app for undervolt and overclocking kernels providing sysfs interface, designed and implemented by raspdeep (thank You!) It is being tested on his kernel releases and I can guarantee (kind of) its functionality on those kernels.
The idea of the app is to keep all simple as possible, not adding any startup services and reusing existing solutions (such as init.d support).
Q: What does it mean to undevolt, and what is overclocking?
Read more in "OC / UV 101" section That is a detailed(sort of) explanation what UV/OC means.
Check this great overclocking/undervolting guide by shaolin95 (thanks!) and discussion topic!
Prerequisites:
-root (superuser + su)
-busybox
-OC kernel supporting either UVLF and UVHF (Version 1.61) or UV_mV_table (1.97 and up)
-init.d scripts support for apply on boot
3.0.1 - OLD version;

Thank's, this app is awesome.
Now i've Super Optimized JPM-JP6 Kernel v.3.7 and this run with -50 Low -25 High scheduler anticipatory (Lagfix NO RFS overkill JFS Bind=false)
and all works great.

Thanks for this app! it's a nice tool. Once feature request for the OP would be an explanation of the different schedulers. I'm using noop after some research.
Edit: I guess it would be an OP request, not a feature request.

curious, may i ask what is the difference between noop, anticipatory, deadline, and cfq?

Just search it on wikipedia.
It seems noop is the best with flash memory.
Sent from my GT-I9000 using XDA App
E: doesnt work for me anymore. Blank screen only.
Just reflashed jpo yesterday and oc kernel 2.1 by rasp.

Doesn't seem to work with YA-OK kernel (which supposably implements rasdeeps oc 1.1). Black screen same as above poster.
Might be a kernel problem, so I'll wait for the next version, hopefully it works

oswade said:
Doesn't seem to work with YA-OK kernel (which supposably implements rasdeeps oc 1.1). Black screen same as above poster.
Might be a kernel problem, so I'll wait for the next version, hopefully it works
Click to expand...
Click to collapse
YA-OK is not using my UV code hence this app wont work. he hardcoded the UV values if im not wrong

Lio78 said:
Thank's, this app is awesome.
Now i've Super Optimized JPM-JP6 Kernel v.3.7 and this run with -50 Low -25 High scheduler anticipatory (Lagfix NO RFS overkill JFS Bind=false)
and all works great.
Click to expand...
Click to collapse
I use the same kernel and same settings but all i get when i open this app is a black screen and the su popup. Is there something else i have to setup so that app will work?
May it have something to do with setcpu?

An recommendations for stable UV on 1200MHz OC kernel? Specifically for the 1000-1200MHz range? I have the 100-800MHz range at -50mV.

ggonzalez7777 said:
An recommendations for stable UV on 1200MHz OC kernel? Specifically for the 1000-1200MHz range? I have the 100-800MHz range at -50mV.
Click to expand...
Click to collapse
I've been on 0, 25, 50, 75, 100, 100 on 1.2 Ghz - its been stable for "normal" use - but i dont stress it out with video/ 3D etc - so YMMV.

New version posted, first post updated.

nice bro!
one suggestion: add checks so it wont show blank screen if the values are not read properly or folders/file not found and display messages
sometimes peeps run a wrong kernel and expect your app to work

Which version is better for SetiroN's 1.2 kernel?

Will look into it, most of checks are there, but I might have forgotten about some
MikeyMike01 said:
Which version is better for SetiroN's 1.2 kernel?
Click to expand...
Click to collapse
As of today: 1.61. Both use old UVLF and UVHF implementation.
0 50 100 75 75 125 seems to be working here

Alright... I wont upgrade then.
Sent from my SAMSUNG-SGH-I897 using XDA App

Cant get over this "blank screen issue". I've *almost* isolated the issue, it lies in these lines:
DataInputStream osRes = new DataInputStream(process.getInputStream());
BufferedReader br = new BufferedReader(new InputStreamReader(osRes));
res.add(br.readLine() + "");
br.close();
Click to expand...
Click to collapse
Cat command returns under 64 chars when file is found, when it isnt output is >64 chars.
Thats the reason for block, somewhere in these lines.

xan said:
Cant get over this "blank screen issue". I've *almost* isolated the issue, it lies in these lines:
Cat command returns under 64 chars when file is found, when it isnt output is >64 chars.
Thats the reason for block, somewhere in these lines.
Click to expand...
Click to collapse
Glad you know of this issue, on my captivate the older version works fine but when upgrading to the new one it is stuck on the black screen forever. It says SU permission granted but just stays on the black screen. I tried uninstalling the old first, rebooting, then installing and also just overwriting the old with new. Nothing but black.
Good luck on the fix, this is a very handy app

loco- said:
Just search it on wikipedia.
It seems noop is the best with flash memory.
Click to expand...
Click to collapse
I agree, here are a couple of comments that convinced me:
You want to use noop scheduler on devices where there are no seeking penalty, such as flash drives. That's why USB stick wants noop. Unfortunately, harddisks are very mechanial beasts and their performance is highly controlled by their seeking abilities. All these schedulers above are really trying to figure out how to extract maximum performance off the harddisk without causing bad behaviour in other cases.
noop is often the best choice for memory-backed block devices (e.g. ramdisks) and other non-rotational media (flash) where trying to reschedule I/O is a waste of resources.
http://www.linuxhowtos.org/System/iosched.htm
http://stackoverflow.com/questions/1...-i-o-scheduler
Click to expand...
Click to collapse
E: doesnt work for me anymore. Blank screen only.
Just reflashed jpo yesterday and oc kernel 2.1 by rasp.
Click to expand...
Click to collapse
When I installed the new version 1.97beta, it too sat at a black screen for an unusually long time, then after almost a minute, the supperroot permission screen poped up, I granted it root rights, and then voltage control came up fine.

Hm, read first post.

xan said:
Hm, read first post.
Click to expand...
Click to collapse
Umm, what post is this comment directed to?
Unclear what topic, and what in the first post we are looking for?

Update! [Kernel] [2.6.29] [Updated: 22/12/2010] RaKern-113 for GSM Hero

Please take the time to read all the description. It is important!
What's new in RaKern-113?
I tweaked things here and there. It is now better to work with and much more stable. I've also discovered what was causing wlan not to work, and it is fixed. To be more specific:
- I've gone again a little bit into the scheduler and made some changes
- tweaked lowmemorykiller
- reduced the maximum frequency to 652MHz(from 691MHz), hopefully this will make the kernel compatible with more Heros
- patched smd_rpcrouter(see here why: http://forum.xda-developers.com/showthread.php?t=878268 )
- created update.zip for any rom available
Why should you choose RaKern?(long story, good to read)
After some debates about the perfect cpu frequency governor for a battery powered device like ours(thank erasmux for that), I've decided to tune what I already have and go for the elegant way. That means using a tuned version of the ondemand governor while the screen is on, and then use the conservative governor when the screen is off. Here's the story:
The only major difference between the conservative and ondemand governor is that the ondemand governor switches to the highest frequency available when the cpu load is higher than the threshold set. Same thing when the load is lower than the min_threshold. The conservative governor takes all the available frequencies in the table and switches between them until the load is lower than the threshold. I've been thinking about it for quite a while and on our CPU I don't think this behavior is the best we can get.
Why? Well let's say we have 650MHz in our table as the maximum frequency. Staying on the same PLL, we would get something like: 176->352->518->537->556->576->595->614->633->652. Let's consider that the phone, while the screen is off, stays at 176 because there is no process that could put load on the cpu, which usually is true, depending on the user setup. When you unlock the screen, you might need a bit of power if you have an animated widget on the main screen. Let's consider that it also uses the internet to update its data and the cpu would be loaded under 80% only @576. In this case, the conservative governor will go from 176 to 576 like: 176-352-518-537-556-576. Remember that on each frequency the kernel will wait for a few us to check the load and then decide whether it needs to raise the frequency again or not, so it would take some time until the CPU can provide the power necessary to have a responsive phone. On the other hand, the ondemand governor would go straight to 652MHz(I forgot to mention that from 518MHz, all frequencies use the same voltage). But here comes the nice part(quote taken from the Ondemand governor data sheet):
the ondemand algorithm frequency down-scaling was changed to jump directly to the lowest frequency that can keep the CPU ~80% busy. This saves more power and enables the algorithm to go to right frequency in one hop
Click to expand...
Click to collapse
So after jumping straight to 652MHz, it will go directly to 576. So instead of 5 steps, the ondemand governor only does two. Of course, in theory, the ondemand governor would be inferior in battery consumption, but in real life it is not so bad, and from my calculations it can even be better. Keep in mind that the latencies are pretty much the same on both governors. The conservative governor is just a modified ondemand.
The conservative governor would be excellent on a Snapdragon device(or any other cpu >1GHz), which can provide good performance at lower speeds, so you'd not have to jump to the highest frequency available. But on our Hero, the difference between 514 and 534 for example is unsignificant if the load is intense, so this basically causes latency.
On small loads, the power consumption with the conservative governor is much better than using the ondemand governor.
How is the governor changing done?
SetCPU. You need to create a SCREEN OFF PROFILE - 19MHz-352MHz with the CONSERVATIVE Governor. Here's how it should look like:
{
"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"
}
Here is the frequency table the kernel is using in its default setting:
{ 0, 19200 },
{ 1, 176000 },
{ 2, 352000 },
{ 3, 518400 },
{ 4, 556000 },
{ 5, 576000 },
{ 6, 614400 },
{ 7, 652800 },
{ 8, CPUFREQ_TABLE_END },
Click to expand...
Click to collapse
As you have probably figured out, in screen-off mode the cpu can only go between 19-176-352. With the screen on, it has a wider choice, 352-518-556-576-614-652. I added more entries to the table(even though I always said this is not good) because I'm not using the default ondemand governor anymore. Now, if the load is >60%, it goes up. If the load is <70%, it goes down. IF the load is >90%, it goes to MAX and if the load is <20% it goes to MIN. This is very efficient and battery-friendly. It also changes very fast between steps, as I've done some other tweaks to improve latency.
Instructions:
Download the ZIP and flash it. Then, install SetCPU(if you don't have it already) and configure a profile as you've seen in the screenshot above. After that, you're good to go .
The most important features are:
- Ondemand CPU governor improved for efficient frequency jumps and usage optimization
- dual-CPU governor based on screen state
- kernel level touch input filtering(Ninpo)
- EXT2/3/4 and FAT support
- IPv6 support, including GRE and IP multicasting(see more info below)... Mobile IPv6 should also work in a proper enviroment not anymore in 109 and 113, I will bring it back in the next version
- dalvik and swap optimizations
- battery life enhancements
- Fair scheduler tweaked for better performance
Message for users: RaKern-113 works brilliantly with ChocolateEclair 2.0.
IPv6 info(good to read, but not available in the current version):
I do not own an IPv6 capable router, so I can not say exactly how it works, but I can tell you how it should behave. From what I could see, in this configuration, the IPv6 implementation is similar to the one in Windows Vista/7. IPv4 and IPv6 work together, but IPv6 is preferred. If it can obtain a global unicast address, it will attept to communicate via IPv6. Also, support for IPSec and 6-to-4 tunneling is enabled.
Until a get a dual-stack router, I can only help you with theoretical information. Maybe fellows in Japan can give me a bit of help with this?
Filesystem info:
I've added support for EXT3/4 because I know some people might find using those FSs useful. But for the avreage user, I suggest sticking with EXT2 as its successors use more cpu juice.
Feel free to include this kernel in your ROM. All that I require is that you do not change the kernel name/version, and post a link to this thread in your ROM description. Other than that, it would also be good for the community if you'd share your changes here. Whichever leads to improvement is appreciated.
So... To the important part:
RaKern-113 for ALL ROMS
MD5 sum: 3a1d07e6a2bcbdcb39330477e877ac81
SOURCES
If you appreciate my work, please consider helping Santa buy some presents
​

Reserved for future use.

Thanks RaduG,
Will definitely try this out on ChocolateEclair 2.0; you've done some amazing work on that ROM as it is.

Thanks. Please let me know how it works.

Any chance of you sharing the tweaks you found usefull?
github is the ideal platform for this, but you need to use it properly. If you just push "first commit" then it really does not help the development community....
In any case, good luck with your kernel, and hopefully soon, your ROM.

Well, it is the first commit, what should I say other than first commit... I will mark the further updates. Also, the main changes have been mentioned in the first post.
Thanks, good luck to you too

It is now hard to view the changes you made, and now we will have to diff it manually
Just for the next time, maybe you should first upload where you got it from (or fork?) then commit the changes.
Anyway.... good to have another kernel for the hero. Variation is good for the quality
ps. care to look at the .34 port of Elemag and see what is wrong?

It does not work on my Hero with Froyo (Elelinux - http://forum.xda-developers.com/showthread.php?t=767886) - force closes... well, everything on boot and reboots itself (boot-loop).

I don't know where I got it from, because I applied changes to the sources that I already had been working on before I left. I will have a look at Elemag's port after I finnish my next ROM.
@pushaty
Try to wipe dalvik-cache/cache, as I said in the first post.

RaduG said:
Try to wipe dalvik-cache/cache, as I said in the first post.
Click to expand...
Click to collapse
That's what I did, just after flashing Your ROM (before first boot). I've even wiped it again after first fail but 'no go'.
Edit
FYI (maybe this will be helpful), Flykernel is 'doing it's job' for me. Even 12pre2 (experimental) is running just fine.

Same here. Everything force closes on boot after a full wipe and a clean install of ChocolateEclair + this kernel.

I've flashed the exact same package and it works just fine. :-?

It does not work on my Hero with : CyanogenMod-6.1 for HTC Hero V6.1.0 .
I wiped dalvik-cache/cache, but not boot.

Just reinstalled everything without the kernel and going to see what happens when I flash it past the 'android.setup' process which is what prevented the phone from functioning last time.

RaduG said:
I've flashed the exact same package and it works just fine. :-?
Click to expand...
Click to collapse
Are You running Froyo or Eclair?

RaduG said:
Well, it is the first commit, what should I say other than first commit... I will mark the further updates. Also, the main changes have been mentioned in the first post.
Thanks, good luck to you too
Click to expand...
Click to collapse
Lets pretend, that I am a kernel developer and I want to learn/check/admire/criticize/improve/port/etc. your tweaks and developments. How am suppose to do this? The normal way is to check the commits in the github and their diffs, unfortunately in this kernels case, there are no commits for the tweaks. Look at almost any other kernel on github to see what I mean (mine, ninpo's, cyanogen's, Decad3nce's, etc.).
For example, in the case of this kernel and version, I would be very interested to know what are the code changes you did for these two items:
RaduG said:
- dalvik and swap optimizations
- battery life enhancements
Click to expand...
Click to collapse
Especially in the case of these two, having only the "first commit" in your github doesn't really tell me anything. I can download all your sources and do a full diff against mine, but I hope its clear why thats just crazy....
If you prefer to share your changes in some other way it will be very welcome. Of course if you choose to keep it only in this inconvenient way (which at least satisfies GPL I believe) its your right.
This will be my last post on the subject. I am sure that if you choose to share your knowledge, by github or otherwise, it will be beneficial to the entire community.

Doesn't work here either, running Cronos ROM Froyo.
logcat: http://pastebin.com/ag96BF2W
There is really something going on when Dexopting apps.apks.

I've got it to work now, but you have to boot at least once before flashing the kernel as it causes the 'android.setup' process to crash (at least with ChocolateEclair).

beachdemon said:
I've got it to work now, but you have to boot at least once before flashing the kernel as it causes the 'android.setup' process to crash (at least with ChocolateEclair).
Click to expand...
Click to collapse
IMO, that means something is wrong and it should be fixed asap.

I'll have a look at it. Thanks for reporting.

[ACS]Battery Tweak for the NS4G RC1

{
"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"
}
Shabbypenguin and the Android Creative Syndicate
present to you
Battery Tweak RC1​
This is really a tool for power users
If you don't consider yourself 'comfortable' with messing with your phone, then don't.
This is mostly the work of collin_ph, all the ideas are mostly his and I have only contributed in part to getting some things functioning correctly and some optimizations for the NS4G.
What does it do?
This tweak creates a service that periodically checks the phone's power source.
If the power source changes, it reconfigures the device for maximum performace, battery and safety.
Tweaks memory settings for current power source
Re-clocks CPU based upon battery remaining or current power source
Reclocks for maximum performance if on AC power
Reclocks for maximum performance and charging safety if on USB
Reclocks for performance and battery if on Battery
As Battery life is diminished, Maximum CPU frequency is lowered
Tweaks scaling charactaristics depending on power sourcee
CPU Scales up less frequently on battery power
CPU Scales up more frequently on USB/AC power
The CPU is allowed to scale dynamically in all charging states based upon CPU usage
Includes a batt-cfg utility to configure the system
You may load 1 of 3 pre built profiles
Manually configure CPU Frequencies in all charging states
Determine the percentage of underclocking as the battery drains
Configure how often to poll the power state / battery statys
Disable batt.sh service from running at startup
Includes a batt-rm.sh uninstall utility
Includes a batt-diag diagnostic utility
Includes optional Disk performance tweaks (enabled by default)
Includes overheating controls to lower your cpu if the phone starts to overheat
The Tools
The entire 'application' is written in shell code and was first written just to give a performance and battery boost, but since has evolved more and more.
All the tools mentioned will be utilized either through the terminal, or in adb shell.
batt.sh
This is the core of the entire script. Don't mess with it.
The one thing you should do after installing the script:
Code:
Code:
pidof batt.sh
If theres any number showing up after it, then it's working fine.
batt-cfg
This is the 'main menu' of sorts, as it gives the user all the options and allows them to toggle tweaks/mods on the fly.
batt-diag
It's a diagnostics utility, allowing you or someone knowledgeable to figure out any issues that you may be having with your device and be able to pinpoint exactly where the problem is.
batt-diag -v gives a more thorough output as you can see here; http://pastie.org/1162034
batt-rm.sh
It's a battery tweak removal script, follow the onscreen prompts and it should remove just about any trace of the battery tweak script.
The Presets
The presets are just default configurations that I have set up that can make your phone more efficient without you, the user, having to manually set everything.
The preset of 800 literally means that 800000 is the scaling_max_freq, or the max frequency, that your phone can achieve after you enable it.
Just typing 1, and then enter, you'll be ready and set to go. Same with 2 or 3.
Customize Settings
This is only for the experienced user, and it allows you to manipulate most/ifnotall the configurables on your device.
Note, you do not need to configure anything to enable this battery mod. Default settings will be assigned at 800MHz.
All the settings explain what each option does, so read them carefully.
Disk Boost
Remounts via noatime and nodiratime. Look up what that means on your own, and why it benefits performance the way it does.
Prerequisites needed to run this
netarchy's kernel
Matr1x kernel
seems to work with every rom
If you're running any other kind of kernel, feel free to try it but i cannot guarantee that it will work.
This script will WORK even if you don't have the import call at boot, but it won't survive on the next reboot. AKA if you dont have this rom kernel, when the phone boots it may not start batt.sh if you are willing please check and let me know if the rom/kernel supports it.
You can check via:
Code:
Code:
pidof batt.sh
NOTE: This script will also prompt you to try to run itself as root if you use it in terminal.
Contributors:
Collin_ph
Decad3nce
myn
onicrom
shabbypenguin
nullghost (aka tehdarkknight)
nubecoder - so he might not cry any moar
Download
*make sure to ignore some of the finer things on the screens they came from the epic version which im working on *
*make sure you are running these as root*
*disable setcpu while running this*

reserved for something

Makes me want to get a Nexus...
EPIC PORT [email protected]!!!!!

why so you can try it on your evo3d?

Great job bro!
Sent from my Nexus S 4G using Tapatalk

I can't wait to try this.
dreamsforgotten said:
Great job bro!
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
OT: but those lyrics are from Tears for Fears, he simply did a cover
Sent from my Nexus S 4G using XDA App

derekwilkinson said:
I can't wait to try this.
OT: but those lyrics are from Tears for Fears, he simply did a cover
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well I covered my ass by citing a reference : p
Sent from my Nexus S 4G using Tapatalk

Now that's what I'm talking about, great job can't wait to get this up and running
Sent from my Nexus S 4G using XDA Premium App

Nice job. I might play around with this later tonight. Nicely done.

I install it but were i go for settings?
Sent from my Nexus S 4G using Tapatalk

renizo said:
I install it but were i go for settings?
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
batt-cfg check the op for more
Sent from my Nexus S 4G using Tapatalk

either thru terminal emulator or adb shell

Anyway to add support for init.d by putting or editing a different script? Using opensoju, i dont know much about init.d or how it is implemented into a rom.

I love this original mod by collin. Glad to see you guys working w him
Uncle Jimmy says hello

uhh no idea all i know is the init script is there

It's been forever since I've used Collin's tweak with my Hero so please forgive the stupid question: if I flash a Rom or kernel do I need to reflash the batt tweak zip?
Sent from my Nexus S 4G using Tapatalk

rom yes, kernel no

shabbypenguin said:
uhh no idea all i know is the init script is there
Click to expand...
Click to collapse
After flashing netarchy beta 1.3.5, init.d was created and is executing at boot. In the kernel. Learn something new everyday Thanks for this mod. Ima big fan of ACS.
Uncle Jimmy says hello

running deck's ROM 1.2x, netarchy kernel 1.3.0.12 CFS universal and it survives reboot,.
Thanks for this. I also ran this on my hero back in the day.

so you can just flash this zip & you're ready to go if you want to leave everything at their default state?
everything seems to be working for me with KingsROM & Netarchy Kernel!

[APP][24Nov] - 4.9 - SGS1+2] Voltage Control - control OC/UV for OC kernels

I take no responsibility for ANY damage / data loss may occur. Use this at your own risk. Beta quality software!/Alpha quality features!
The news:
4.9 - THIS IS HIGLY TEST RELEASE
+ Profiles support
+ Bus frequency switching for Siyah kernel
+ Widget with profile switcher and app launcher (passive!)
+ Recovery instructions: lets you place CWM flashable boot settings deleter
+ CPU history: now can reset and refresh graphs
+ Root detection improvement (I hope...)
Voltage Control Extreme unlock Key on Android Market!
For now features exclusive to Extreme version are:
+ More than two profiles
+ CPU History page
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Click to expand...
Click to collapse
Sources available, project on google code:
http://code.google.com/p/voltage-control/
Look for kernels with this label:
Kernel developers who added VC support please show this image in your topic
{
"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"
}
Uploaded with ImageShack.us
Features:
- minimum/maximum CPU frequency choosing
- selecting IO scheduler
- selecting CPU governor
- changing voltage per frequency
- chosing which frequencies should be used and which shouldnt
- saving settings to be automatically applied at boot (init.d script)
- saving/loading a OC profile
- well designed and highly optimised UI (I hope..)
- robust kernel detection, support of not-so-well-working kernels
- Siyah kernel interfaces (Charging current and GPU OC/UV)
- device info page
- (extreme) CPU usage history page
About donations:
This software is available free of charge.
It cooperates with OC kernel by raspdeep.
It uses some code from: MarketEnabler (Fool your market to make all apps visible!)
If you find this software useful, please consider funding a beer and pizza. There is a "Donate to me" link just over my avatar.
Donator list:
nitr8
kalpik
laststufo
glitterballs
screwyluie
Gembol
Coreym
Thanks!
How to?
Generally idea is simple: make changes to one tab and hit apply. If any changes have been made apply/discard buttons appear on bottom.
The first tab, "General" allows to change Scheduler,Governor/min and max frequencies.
Make changes and click apply
So, you want to pick a maximum/minimum frequency?
Just chose from slider and hit apply.
Governor/scheduler can be choosen by picking from the list, then hitting apply.
You can always discard changes before applying if you want start from loaded settings.
The "Advanced" tab has sliders to control undervolting settings and green/red icons, representing enabled/disabled state.
(green = enabled, red = disabled)
Pick your settings and hit apply, or discard and start over.
Profile support:
If you want to save as boot or as profile, you need to make adjustments and on "General" or "Advanced" tab and then apply them where applicable.
To save as boot -> press menu key, then select "Save as boot settings".
To save as profile -> press menu key, then select "Save profile".
Boot settings are automatically loaded on every device boot.
Profile settings can be loaded by pressing menu -> "Load profile"
Both "boot" and "profile" settings can be deleted from menu.
RECOVERY
If Your device freezes after boot because of too agressive boot settings:
Flash Voltage Scheduler Remover by user Coreym, via CWM. Don't forget to press thanks under one of his posts!
FAQ:
Q: Extreme version?
Yes, I wanted to give some extras for people that support my work.
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Q: What is it?
Its voltage control app for undervolt and overclocking kernels providing sysfs interface, designed and implemented by raspdeep (thank You!) It is being tested on his kernel releases and I can guarantee (kind of) its functionality on those kernels.
The idea of the app is to keep all simple as possible, not adding any startup services and reusing existing solutions (such as init.d support).
Q: What does it mean to undevolt, and what is overclocking?
Read more in "OC / UV 101" section That is a detailed(sort of) explanation what UV/OC means.
Check this great overclocking/undervolting guide by shaolin95 (thanks!) and discussion topic!
Prerequisites:
-root (superuser + su)
-busybox
-OC kernel supporting either UVLF and UVHF (Version 1.61) or UV_mV_table (1.97 and up)
-init.d scripts support for apply on boot
3.0.1 - OLD version;

Thanks mate will check this out looks pretty sweet.
Sent from my GT-I9100 using XDA App

4,5 version pushed to market ;p

Thanks a lot for your app xan.
Would it be possible to include GPU OC as well? I saw you were using Siyah kernel which does support that ^_^

What are the interfaces? I have something coming for Siyah in the following week

Take a look at these this post:
http://forum.xda-developers.com/showpost.php?p=18315860&postcount=3897
It has an example init.d script.

The init.d script for GPU OC or UV doesn't work for some people. Thats including myself, I change the value and save the script but nothing changes, I use Nenamark2 to see if my fps has changed, I still get around 50fps (400Mhz)
I asked someone else whose script was working somehow and he achieved 57fps on 400mhz.
I hope you try another way just like Tegrak app to OC and UV its GPU.
I'll defiantly buy it if Siyah kernel is supported

MrPhilo said:
The init.d script for GPU OC or UV doesn't work for some people. Thats including myself, I change the value and save the script but nothing changes, I use Nenamark2 to see if my fps has changed, I still get around 50fps (400Mhz)
I asked someone else whose script was working somehow and he achieved 57fps on 400mhz.
I hope you try another way just like Tegrak app to OC and UV its GPU.
I'll defiantly buy it if Siyah kernel is supported
Click to expand...
Click to collapse
The GPU script was a reference for the interface used.

xan said:
What are the interfaces? I have something coming for Siyah in the following week
Click to expand...
Click to collapse
That's great , waiting for this, could you possibly give us a hint what's coming up next? Btw using voltage control atm for uving and I love it. Especially that it doesn't run in background but makes a script which no other CPU control app does (as far as I know). Thanks for your great work
Sent from my Miuibuntu Revolution GT-I9100 using XDA App

Xan, you agree with take the source in my rom?
Maybe I can add GPU oc support, but I need first the voltage sysfs, how I can implement it.
Sent from my GT-I9100

The licencing after last rewrite (4.x) changed, its now closed.
You are free to work with the sources on google code (3.x)
The source of app wont be updated to latest version.
I'm implementing GPU oc/uv (UI!) myself, it will be available today/tomorrow.
Charging speed changes will be available too: http://forum.xda-developers.com/showpost.php?p=18471684&postcount=5059
About sysfs itself: check siyah sources.

xan said:
The licencing after last rewrite (4.x) changed, its now closed.
You are free to work with the sources on google code (3.x)
The source of app wont be updated to latest version.
I'm implementing GPU oc/uv (UI!) myself, it will be available today/tomorrow.
Charging speed changes will be available too: http://forum.xda-developers.com/showpost.php?p=18471684&postcount=5059
About sysfs itself: check siyah sources.
Click to expand...
Click to collapse
Why it is now closed source?

netchip said:
Why it is now closed source?
Click to expand...
Click to collapse
Quite a lot of work has been put into latest branch, I dont think I want any clones floating around.
Most was put into ui / look /feel of app..
It doesnt differ much in 'getting' and 'setting' the values, so 3.x code is still very valid and working.

xan said:
Quite a lot of work has been put into latest branch, I dont think I want any clones floating around.
Most was put into ui / look /feel of app..
It doesnt differ much in 'getting' and 'setting' the values, so 3.x code is still very valid and working.
Click to expand...
Click to collapse
I dont want to make a clone.
My intention is include it in a new secret AOSP rom ...
In the settings app.
Sent from my GT-I9100

With the new changes and the possibility of custom frequency steps in upcoming syiah kernel 2.1... Is this app going to be updated to support those ? Because now when I change the frequency steps I can only modify them using setcpu, voltage control cant see the new values and displays only old ones. Same applies for the cpu usage screen.
I bought the premium version because of the syiah extras, so I am hoping it will be updated in the future
Great app btw, been using the old one on my SGS1 back in the days.

xeq544 said:
With the new changes and the possibility of custom frequency steps in upcoming syiah kernel 2.1... Is this app going to be updated to support those ? Because now when I change the frequency steps I can only modify them using setcpu, voltage control cant see the new values and displays only old ones. Same applies for the cpu usage screen.
I bought the premium version because of the syiah extras, so I am hoping it will be updated in the future
Great app btw, been using the old one on my SGS1 back in the days.
Click to expand...
Click to collapse
Will do my best, I'm not sure how to handle this at this moment...

Will not run in ICS rom. Any chance of an update?

How come, it works for me.
Maybe some details?

Great work!
Sent from my GT-I9100 using xda premium

xan said:
How come, it works for me.
Maybe some details?
Click to expand...
Click to collapse
Nvm. I uninstalled it, then downloaded from market and this time it worked. I have the Extreme version installed.
Thanks.

[MOD] Architect_Edition : * Set your kernel without application * and more *[SCRIPTS]

Warning : Stritcly FORBIDDEN to share MY work on Phonandroid
{
"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"
}
Kernel Architect is some scripts to set your kernel without application and 100% compatible with all Kernels
only if you have a Snapdragon 800 as processor
You can modify :
- governors
- schedulers
- max frequences *
- table of voltages *
* if your kernel have OC/UV options
List of commands
Open an application like Android Terminal Emulator
Start always a session with su + enter ...
Code:
Architect
*that give you some informations and recommandations
Code:
governors
*that will show you all governors available
Code:
name of governor
conservative
interactive
wheatley
ondemand
performance
powersave
userspace
*that will activate the governor of your choice ( say me if you want another )
Code:
schedulers
*that will show you all schedulers availables
Code:
name of scheduler
cfq
deadline
noop
row
sio
fiops
test-iosched
vr
zen
*that will activate the scheduler of your choice
Code:
freq
*that will show you some informations about frequences of your CPU
Code:
freqmax1,3
freqmax1,4
freqmax1,5
freqmax1,6
freqmax1,7
freqmax1,8
freqmax1,9
freqmax2,3
freqmax2,5
freqmax2,7
*That will activate the max fréquence of your cpu : 1,3Ghz to 2,7Ghz
Code:
volt
*That will show your table of voltages CPU
Code:
volt0
*That will set the original table of voltages
Code:
volt-25
volt-50
volt-75
volt+25
volt+50
volt+75
*That will set - or + in mV
that will show you before and after
Warning: the base is volt0
How to have these scripts actived at boot
2 way :
- the folder init.d
- use Script manager
1) init.d
Copy your combinaison, for example :" interactive, deadline, volt-25 and past it in /system/etc/init.d/
Don't forget to be in root explorer and give right permissions *... ( read, write, execute )
You can find all my scripts in /system/bin/
or : Kernel-Architect-scripts.zip
2) Script Manager
Take the application Script Manager on play store
Choose the script, give root access and apply at boot
You can find all my scripts in /system/bin/
or : Kernel-Architect-scripts.zip
*** Kernel Architect-signed.zip ***
Uninstall Kernel Architect-signed.zip
Kernel-Architect-scripts.zip
- Reboot in your Recovery
- Install Architect_Edition-signed
- Enjoy
~~~~~~~~~~~~~~~~~~~~~~~~~
More​
Take my TWRP theme :
Our themes1080p​
- Download
- Reboot on Recovery
- Install
- Reboot on Recovery
- Enjoy
~~~~~~~~~~~~~~~~~~~~~~~~~
​

Reserved for OP

This is awesome. Great directions, works like a charm.
And first!
Sent from my SM-N900T using Tapatalk

I like alternatives. Especially the simplicity. Thanks.

I really expected a lot more activity in here. I would be here more often, but haven't had a single issue with the scripts. $hts on point. Battery lasting 3 days sometimes and I don't have to touch a thing or ever re-tweak. Just set all my (your) scripts on boot... Done.
And I still like the fact I don't have to mess around with an app.
Sent from any phone that isn't made by Apple.

Good stuff, simple and convenient - and sometimes silence is a good thing

dwitherell said:
Good stuff, simple and convenient - and sometimes silence is a good thing
Click to expand...
Click to collapse
Anybody need to begin by silence

Very good work, works great....thank you sir
reason for not much traffic, not many people like venturing into the kernel area and such....
But for peeps like us, this rocks.
:good::good:

dwitherell said:
Good stuff, simple and convenient - and sometimes silence is a good thing
Click to expand...
Click to collapse
I hear you. I was more leaning towards some thanks buttons being pressed. Maybe a question or two. But mainly on these threads you see a ton of requests. You should know, your thread(s) are full of requests. LOL.
TheAxman said:
Very good work, works great....thank you sir
reason for not much traffic, not many people like venturing into the kernel area and such....
But for peeps like us, this rocks.
:good::good:
Click to expand...
Click to collapse
True DAT...
Sent from any phone that isn't made by Apple.

noobtoob said:
I hear you. I was more leaning towards some thanks buttons being pressed. Maybe a question or two. But mainly on these threads you see a ton of requests. You should know, your thread(s) are full of requests. LOL.
True DAT...
Sent from any phone that isn't made by Apple.
Click to expand...
Click to collapse
I gave you another thanks, this baby is way nice...again thanks for giving me a toy to play with...this has some potential. And it works great...no issues here sorry to say.

What is the benefit to using this versus setcpu or trickster?
Sent from my SM-N900T using Tapatalk

useltonm said:
What is the benefit to using this versus setcpu or trickster?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
The benefit is not using an app.

NorthLight said:
The benefit is not using an app.
Click to expand...
Click to collapse
Why is that a benefit though? I'm not trying to be difficult, I'm genuinely interested. If using something like this increases my Android knowledge, I'm all for it. I would just like to know before I dig into it more.
Sent from my SM-N900T using Tapatalk

useltonm said:
Why is that a benefit though? I'm not trying to be difficult, I'm genuinely interested. If using something like this increases my Android knowledge, I'm all for it. I would just like to know before I dig into it more.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
This mod will allow for all your specified kernel settings to load at boot via androids init.d. Apps like Trickster will load up in system memory after the OS has booted and will then apply the modifications you specify. You could say that scripts like this are "cleaner" ways of applying tweaks as it is done during boot naturally through the OS and negates the need to have an additional app starting and running in the background. That being said, init.d scripts are not as user friendly as apps like Trickster and could take some time to get used to if you don't have much experience with them. The scripts may also increase boot time but will most likely be a negligible amount.

themichael said:
This mod will allow for all your specified kernel settings to load at boot via androids init.d. Apps like Trickster will load up in system memory after the OS has booted and will then apply the modifications you specify. You could say that scripts like this are "cleaner" ways of applying tweaks as it is done during boot naturally through the OS and negates the need to have an additional app starting and running in the background. That being said, init.d scripts are not as user friendly as apps like Trickster and could take some time to get used to if you don't have much experience with them. The scripts may also increase boot time but will most likely be a negligible amount.
Click to expand...
Click to collapse
Thank you. Time to start reading.
Sent from my SM-N900T using Tapatalk

themichael said:
This mod will allow for all your specified kernel settings to load at boot via androids init.d. Apps like Trickster will load up in system memory after the OS has booted and will then apply the modifications you specify. You could say that scripts like this are "cleaner" ways of applying tweaks as it is done during boot naturally through the OS and negates the need to have an additional app starting and running in the background. That being said, init.d scripts are not as user friendly as apps like Trickster and could take some time to get used to if you don't have much experience with them. The scripts may also increase boot time but will most likely be a negligible amount.
Click to expand...
Click to collapse
Exactly !
Thanks