Thats right, just loaded it up after rooting this bad boy and it is working just fine!
I am not responsible if you brick your device in the process.
UPDATE!
Ok so here is what is needed to run this badboy without problems.
Use only the conservative option (least problematic and no sleep comas)
I dont use the widget, i already know the speeds i set it at.
The settings stick even after a reboot, but when you click on the setcpu icon they revert back and you lose your settings. If that happens just go back and click on detect auto speeds and set up your speeds again.
Happy clocking!
what version? 2.0.1?
Were you able to overclock it past the 1ghz?
I rooted mine today and installed setCPU which worked flawlessly but I am not able to move the slider past 1ghz.
I loaded it on mine and while it *appears* to work, it doesn't seem to effect the clocks any.
heck just underclock your phones to save battery lol
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
jroid said:
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
Click to expand...
Click to collapse
To see if it's working set it to underclock and then get into an adb shell and run the command: cat /proc/cpuinfo
It should display cpu data that includes the current clock speed.
I don't know if this helps but when I was in the Quadrant Standard app it has the system info. I hit it, scrolled down to cpu and it said
Current: 400 mhz, Max: 1000 mhz, Min: 100 mhz,
and I just checked it now and it said my current clock was 800 mhz, so i guess the cpu scales dynamically based on what the load is and what we are doing, thats a pretty great power saving feature.
Select 'Auto Detect'.
I believe you need an oc'd kernal to be able to move the slider past 1ghz.
Also, the dev has stated that it should be set to 'conservative', not 'ondemand'. 'Ondemand' was causing random shutdowns on the Galaxy S.
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Koblek said:
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Click to expand...
Click to collapse
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Has anyone noticed any significant battery conservation with this?
MINUS Stl said:
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Click to expand...
Click to collapse
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
i am still having problems with setcpu even on conservative mode. i have stopped using setcpu completely for now.
wbexpress said:
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
Click to expand...
Click to collapse
Auto detect...
Sent from my SGH-T959 using XDA App
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
mygti02 said:
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
Click to expand...
Click to collapse
What are your exact settings in profiles, advanced and overview?
any one running their phone at 1Ghz all the time?
+1, hah2110 please post your settings if they're working for you so a noob like me can learn some things!
Related
does this app work on Streak?
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
crazy cat said:
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
Click to expand...
Click to collapse
998Mhz is the limit for the kernel. you need a kernel that can be overclocked for that option....
it works fine. at this moment in time you can not overclock but it auto detects settings just fine and you can set screen off speed/battery low speed to extend your battery life.
crazy cat said:
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
Click to expand...
Click to collapse
Wait, u know there are three levels of clocking, right? one is under clock, one is clocked and one is over clock. There are two frequencies when u turn on the setcpu, one is max and one is min...but i would like to know if u r able to make the max and min both up to 998mhz so that it can run at full speed at all times
zgmf-x322a said:
Wait, u know there are three levels of clocking, right? one is under clock, one is clocked and one is over clock. There are two frequencies when u turn on the setcpu, one is max and one is min...but i would like to know if u r able to make the max and min both up to 998mhz so that it can run at full speed at all times
Click to expand...
Click to collapse
yes you can bro. both max & min are customizable from 24500Mhz upto 99800Mhz. however, ive found that having the streak running totally max when the screen on will simply drain your battery, there are no real speed improvements to be seen. a good compromise to combat lag would to be to set screen on: 76800 - 99800Mhz.
i completely downscale mine when the screen is off and although the battery life on the streak is good, doing this makes it even better. no lag when switching screen on either (frequency change)
Works great for me too! I don't see any need for overclocking a phone (unless you don't use it as a phone..)
I unplugged mine from the charger about 1.5 hours ago, still 100% battery..
thanks guys for the reply, appreciated it alot!
it does and very well
to get interactive setting you must at least have performance fix and it will let you overclock and add interacting setting i just did perf. fix and setcpu settings and now quadrant score of 1700+
Works great for me. Flash smokku and fard's djsteve kernal perfmod using clockwork or streak mod and then you can overclock using setcpu. Look at my signature line below.
Dell Streak, 2.2 froyo (318), custom kernel, OC to 1.2ghz, quadrant 2002, hspda signal mod,
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
i think you have to wait for the source code for the kernal to be released and tinkered with to get anything useful from all that...but who knows
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Odinist said:
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Click to expand...
Click to collapse
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
SuperFly03 said:
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
Click to expand...
Click to collapse
pretty much what I did, minus everything but the screen off
I always set the screen off on my evo 4g to 245 max, and will probably do the same here. Kinda waiting for kernal source code to be released so I can use the smartass governor. I always liked that one.
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
I cannot wait to tinker once HTC releases the kernel source!
mthorn79 said:
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
Click to expand...
Click to collapse
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
nosympathy said:
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
Click to expand...
Click to collapse
Ok I'm not an idiot, I know quadrant scores don't mean anything but some people use it as a gauge to get an idea on how their phone is. (If u feel it does nothing for you then don't use it if u don't want to no one asked you to)
If you know anything about phones you know certain people's will vary in speeds, I'm just posting my experience...this IS afterall a "Post Your SetCPU Settings' thread, so don't be getting all uppity.
Sent from my ADR6400L using Tapatalk
Jimmy058910 said:
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
Click to expand...
Click to collapse
Yes. I think they releases it within 45 days or something like that. It will most certainly be here soon.
Sent from my ADR6400L using Tapatalk
Any incoming call issues with Screen Off set at 245?
Steeler86 said:
Any incoming call issues with Screen Off set at 245?
Click to expand...
Click to collapse
no and their shouldn't be, unless you down the road, since you couldn't do it now, use one of the governors like Conservative which tend to really slow the phone down. On my Evo 4G it used to take a good 30 seconds to unlock the screen is I used that with screen off at 245Mhz.
1570 for me on stock rom.
I got 2000+ quadrants on stock ROM. SA for setCPU, I can't get my CPU to clock down by force with any app. I think the kernel source is going to be needed. Probably have perflock on like they did on my inc. Let me know if setCPU works please.
SetCPU works, you just have to hit the menu button and click "disable perflock"
1376 on VirusRom but it is soooo snapppy
Seems to be working for me. 39% battery after 12+ hours. Just with the "screen off: max245" setting.
Sent from my ADR6400L using XDA App
We finally got the source code!
Do I need to flash this to overclock
http://forum.xda-developers.com/showthread.php?t=1016916
or can I wait for SetCPU to update?
Is it safe to overclock the Touchpad using setcpu? I have it at 1.5 ghz and it seems to be working fine.
kscully said:
Is it safe to overclock the Touchpad using setcpu? I have it at 1.5 ghz and it seems to be working fine.
Click to expand...
Click to collapse
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Overclocking so far works well. I see no problems as of yet. Just make sure you OC with setcpu; frequencies do not show up in cmsettings when you try to OC there.
Sent from my HTC Glacier using XDA Premium App
atapia984 said:
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Click to expand...
Click to collapse
mines not overclocked and has happened 4 times today. So, obviously not an overclock only problem. I will tinker around with it, but ive yet to tell myself...man, this needs to be speedier. Its run QUICK. far quicker than WebOS and its many 10second pauses (OCed to 1.7 and patched to boot..)
atapia984 said:
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Click to expand...
Click to collapse
Haven't tested it yet, but some say it's a problem due to the "minimum cpu speed" setting when it goes to deep sleep. Something about it being too low and thus can't get out of sleep and setting the minimum higher (not sure of they value) should remedy that.
I'm using SetCpu with a OC of 1.5 and a minimum of 384 with no issues.
my question is should I click the box for set on boot?
i do. set on boot, min 384 max 1512, ondemand tcl
no sleep death, no lag, working great! (mind you im still on CM7 A1, by preference)
What is the difference between ondemand and ondemandtcl settings? Also, any problems encountered running 1.7g I've only read people running 1.5g...
There's a fix to the Sleep of Death issue and that worked for me. I thought using SetCPU caused the sleep problem but that doesn't seem to be the case. I'm going to see how far I can overclock my TouchPad now
link
I'm running Setcpu at 384/1.7 with zero problems.
I was having issues at first with failure to wake from sleep but after I changed my min to 384 It has not failed once. All my little problems went away when I made this change. Been running for 12 days without a single need to reboot.
butikofer08 said:
What is the difference between ondemand and ondemandtcl settings? Also, any problems encountered running 1.7g I've only read people running 1.5g...
Click to expand...
Click to collapse
i run 1.5 purely for performance/battery conservation but it goes to 1.7 just as easily too.
also traditionally:
Ondemand - Both CPU cores freely move up and down as needed.
Ondemandtcl - prefers the use of CPU0 unless CPU1 is absolutely necessary for use, then it will kick in. otherwise it will remain idle
does anyone try alpha 3?
I saw people said touchpad freeze when using setcpu. Does it work well?
im oc with 1728 max and 192 min ondemand. no issues or sleep of death. im thinking of bumping it up to 1.8ghz like i have in webos.
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Haven't used powersave mode at all yet, It's possible that profile has bugs on this phone.
I have my screen off profile set to 800 mhz and conservative and have had 0 issues so far.
as far as I'm aware powersave doesn't let it out of the minimum frequency (could be wrong). Use the conservative governor instead.
Don't use power save. I have done a lot of testing with this.
Here is the lowest that you can go.
Range: 200-500mhz
Mode: ondemand or conservative
If you go less than 500mhz or put it on powersaver, then it won't wake up from locking the phone.
Thanks
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
geauxlsu83 said:
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
Click to expand...
Click to collapse
I noticed that setting it to 200-500mhz increased my battery life by about 15-20%, but I did notice a significant performance drop. 200-800mhz is much less noticeable performance wise, but I didn't check to see what kind of battery life I got on that setting.
As for widgets...I'm not sure on that one either.
geauxlsu83 said:
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Click to expand...
Click to collapse
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
thanks
yeah im actually flashing your kernel as we speak i looked under a battery thread and they said your kernel is good for battery conservation thanks for your help
actually i flashed it from heimdall and it says it is kernel version is 2.6.35.7 is this yours?
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Entropy512 said:
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Click to expand...
Click to collapse
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Well said.
Entropy512 said:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
Click to expand...
Click to collapse
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
vladm7 said:
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
Click to expand...
Click to collapse
This is why I also have my screen-off limited to 500. Once in a while, the phone needs to do a little extra work, and it's better to ramp to 500, get stuff done, then go back to deepsleep. As I said min=max=200 SHOULD be OK, but personally, I wouldn't recommend it.
I would love if SetCPU allowed for different governor tuning depending on profile. e.g. make up/down threshold more battery-biased with screen-off than screen-on. (Slower polling rate, higher up/down thresholds.)
SetCPU root access problem
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
IshouldntbeHere said:
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Click to expand...
Click to collapse
Pretty sure it's your phone cause mine OC's to 1.6 with no problem.
BigBopper said:
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
Click to expand...
Click to collapse
Have you tried updating the su binary in Superuser? (Even if you have the app updated, the app itself needs to update the binary.)
Beyond that I have no ideas.
Entropy512 said:
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
Click to expand...
Click to collapse
Ahh, that was my problem. I was using powersave. Do you (or anyone else) see there being a benefit to having a screen off profile?
In theory, a screen-off profile shouldn't help - in reality, it's a line of defense for cases where something goes nuts in the background.
What settings are best for optimal performance and battery life? I don't have any experience with this, and I don't want to screw anything up. I just got tired of my games always lagging, but I don't want a battery drainer. I dont believe I have a custom ROM. Thanks for any and all help.
NLangan said:
What settings are best for optimal performance and battery life? I don't have any experience with this, and I don't want to screw anything up. I just got tired of my games always lagging, but I don't want a battery drainer. I dont believe I have a custom ROM. Thanks for any and all help.
Click to expand...
Click to collapse
SetCPU probably won't work very well unless you flash a custom KERNEL. You can mess around with it if you like and you'll probably won't mess things up. One thing I discovered before custom kernels came out is that you can enable the second core by enabling profiles in setcpu. YOu can see that in the menu option of setcpu for "cpu". That may help you in your games. If you set max at 1500 and min 192 initially, you'll see that next time you start setcpu, the max and min are both at 1500. I used another app like cpu monitor widget to see what was happening and low and behold the cpu was scaling 'properly', so I left the setting in setcpu at 1500 and 1500.
In the end...it doesn't work quite the way it was designed for and even with custom kernels we're seeing some issues with it, but mess with it, you may find that enabling the 2nd core will produce less laggy games. You'll have to judge the affect on battery.
topgun1953 said:
SetCPU probably won't work very well unless you flash a custom KERNEL. You can mess around with it if you like and you'll probably won't mess things up. One thing I discovered before custom kernels came out is that you can enable the second core by enabling profiles in setcpu. YOu can see that in the menu option of setcpu for "cpu". That may help you in your games. If you set max at 1500 and min 192 initially, you'll see that next time you start setcpu, the max and min are both at 1500. I used another app like cpu monitor widget to see what was happening and low and behold the cpu was scaling 'properly', so I left the setting in setcpu at 1500 and 1500.
In the end...it doesn't work quite the way it was designed for and even with custom kernels we're seeing some issues with it, but mess with it, you may find that enabling the 2nd core will produce less laggy games. You'll have to judge the affect on battery.
Click to expand...
Click to collapse
I appreciate the help! [Thanked]