Develop Bugs

OCUV, HAVS, etc... - what does it mean?

what does all these stand for, and what do they actually do?
OCUV (is this faster with less battery consumption???)
OC
UV
HAVS
r3.1 (or other numbers)
De-odexed
odexed
kernel
what I'v read is that you can have kernel, rom and radio separatly installed and they work together. correct?

ocuv = overclocked/undervolted, means the kernel can be overclocked or undervolted, overclocked means you run the cpu at alot higher clock speed than normal, meaning better performance, undervolted means you run the cpu clock speed at alot less than normal, giving you better battery performance.
oc - overclocked
uv - undervolted
havs - never heard of this
r3.1 - sounds like the rom version a dev has given his rom lol
deodexed - The Java virtual machine in Android is a Dalvik Virtual Machine, designed to operate on processor-constrained and memory-constrained devices like smart phones. The files that a Dalvik Virtual machine consumes are DEX files - which are Java files rendered by a utility called dx. After the files are rendered by DX they are loaded into a virtual machine and the classes in them are optimized by a utility called dexopt. This results in an "optimized DEX" - an ODEX. To hack such code, the files must be "DE-ODEX'ed," if you will, which is accomplished with a utility called deodexerent.
odexed - Odex stands for Optimized DEX. This is just the machine compiled version of the classes.dex file. To get from the odex version to classes.dex the term deodex is used. consider odexed roms as compressed roms that give you alot more space but cannot be themed
kernal - the kernel is the core set of files that run an os, it is responsible for handling data processing at a hardware level it also controls system resorces like battery ect

I believe when people say MCR r3.1, they refer to Modaco Custom Rom version 3.1.

havs stands for 'hybrid adaptive voltage scaling'
The purpose of HAVS is to minimize the power used by the CPU by determining and setting the optimal voltage. At the same time, the maximum voltage by which HAVS can scale to is fixed to a specified voltage depending on the CPU frequency in order to prevent scaling to a higher voltage than what is normally used at a specified voltage. The optimal voltage is actively determined for each frequency and temperature. HAVS actively adjusts the CPU voltage as the CPU frequency and temperature changes.
rr3636 said:
what I'v read is that you can have kernel, rom and radio separatly installed and they work together. correct?
Click to expand...
Click to collapse
You need all of them to operate your phone.
The radio is the basic piece of software on your phone, it comes pre installed but you can update it to a newer version. You don't have to do this all the time as it stays untouched.
With every ROM comes a kernel, but some ROMS offer you different kernel updates that you can apply AFTER you installed the Full ROM.

x01a4 said:
havs stands for 'hybrid adaptive voltage scaling'
The purpose of HAVS is to minimize the power used by the CPU by determining and setting the optimal voltage. At the same time, the maximum voltage by which HAVS can scale to is fixed to a specified voltage depending on the CPU frequency in order to prevent scaling to a higher voltage than what is normally used at a specified voltage. The optimal voltage is actively determined for each frequency and temperature. HAVS actively adjusts the CPU voltage as the CPU frequency and temperature changes.
Click to expand...
Click to collapse
you learn somthing new every day on here

AndroHero said:
undervolted means you run the cpu clock speed at alot less than normal, giving you better battery performance.
Click to expand...
Click to collapse
No, undervolting means running your CPU at a lower maximum VOLTAGE.
It DOES give you a better battery performance, but some CPUs (not every CPU is produced equally) doesn't like being overclocked/undervolted resulting in an unstable or odd behaviour. You have to test yourself what your CPU can handle

x01a4 said:
No, undervolting means running your CPU at a lower maximum VOLTAGE.
It DOES give you a better battery performance, but some CPUs (not every CPU is produced equally) doesn't like being overclocked/undervolted resulting in an unstable or odd behaviour. You have to test yourself what your CPU can handle
Click to expand...
Click to collapse
x01a4 said:
The purpose of HAVS is to minimize the power used by the CPU by determining and setting the optimal voltage. [...] The optimal voltage is actively determined for each frequency and temperature.
Click to expand...
Click to collapse
The first poster suggests that manual uv tuning is required while the second poster seems to suggest that the uv values are determined by the phone.
If manual, how to you tune it? Increase voltage after each crash/hang?
If auto, how does the phone know when it's pushing the envelope? Considering that the poster claims that it's temp and speed adaptive, that's quite an impressive feat. It's exactly what I'd want to have though.

the kernel's governor decides what CPU frequency the CPU needs to run at under its current load.
On SVS Kernels, this frequency is a SET voltage. On HAVS Kernels, the frequency is a RANGE of voltages which the kernel decides on.
Some kernels do allow you to set those voltages or voltage ranges, see manU kernels for example.
If you follow the red link in my signature, there is a kernel info thread which may help understand a bit better.

Need a little help

I am new to the setcpu app I am wondering how do I know how much frequency my min and max should be to help my phone out more. Can anyone help me on that plz?
Sent from my PC36100 using XDA App

It will depend on which ROM and kernel you're running, but generally, overclocking doesn't do much good for you. I do however run my Main Max @ 1113 and Min @ 245. I then have a profile set for Screen Off Max @ 245, Min @ 245. This has helped a lot with battery life. This is on CM6.1.1 and the SBC stock kernel.
Also, there are the Scaling options. They will vary based on the kernel you're using. Generally, their names speak for themselves, so pick appropriately. I use Interactive when available, or Ondemand as a second choice. If you choose Performance, you will stay clocked at the highest speed until over ridden by a profile, so don't bother with that one unless it's for testing only.
One thing to think about is that Setcpu doesn't play well with HAVS, so if you're running a kernel with that built in, they will be fighting each other.
Also, if you're running a stock based rom with a stock kernel, you will need to disable Perflock if you want Setcpu to be able to really do it's job. So, while in Setcpu, tap Menu > Perflock Disbaler and attempt to disable perflock. Once it is successful, pick set on boot and close that window. Now Setcpu can work properly and you can start saving battery.
If you're primary goal is to get amazing battery life, I highly reccommend you try some of the new SBC kernels that have trickle charging built in. That's what I've been using since they came out, and it is amazing what a little tweak can do for you. SBC Kernel Thread

[Q] HAVS + CPU Control & [Q] Battery Applications

I have a HAVS kernel (Net's 4.2.2 SBC CFS Aggressive HAVS) and as I understand it any sort of CPU Tweaking application will cause conflict and probably a system crash, correct?
Also, can some recommend me any applications that compliment Juice Defender well. I have Juice Plotter already. I am looking for an aggressive auto task killer that's customizable along with any other suggested applications. Thank you!

A system crash is a possibility but they will basically just counteract each other and either make your battery life worse or give a performance hit.
SetCPU helps dynamically underclock/overclock based on certain scenarios. You can set what scenarios you want. Another option is AutoKiller. It isn't Auto Task Killer. Its a different application. Not quite sure how this works but you can research it. However Froyo does a good job managing most applications.
But if you are looking for customization I would go with SetCPU and AutoKiller

Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks

Vulf said:
Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks
Click to expand...
Click to collapse
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...

I just installed setcpu and ran it. My phone crashed about 10 seconds after I allowed root access. Tried twice more with same results.

aimbdd said:
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...
Click to expand...
Click to collapse
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.

sekigah84 said:
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.
Click to expand...
Click to collapse
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.

lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)

aimbdd said:
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)
Click to expand...
Click to collapse
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?

Vulf said:
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?
Click to expand...
Click to collapse
Again, it is not setcpu it is your settings. You said you moved the slider "one or two notches up" (overclock) from the default 944? The evos default max is 998. Either way, with what you said you are overclocking and your device cannot handle the overclocked speed.
Like I said, you can do the exact same thing that setcpu does through terminal emulator. Instead of blame setcpu you should observe the speed/governor combo you are using.
I can oc my evo to 1.26 on my personal kernel without it rebooting on certain governors but on others it would reboot randomly and I don't set cpu parameters through setcpu, I use te, init scripts, and tasker.

lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Couldn't have said it better. The common misconception around these parts is that SetCPU has some negative effect on kernels with HAVS and this is just untrue.

Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.

sekigah84 said:
Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.
Click to expand...
Click to collapse
The common practice with setcpu is to use it to underclock when sleeping. Depending on the governor you use (besides powersave) you are actually causing the cpu to struggle when completing tasks if you limit the max to 245 for example. During sleep if it needs to perform a task and that task would normally complete in 1 second at 998 mhz imagine how much longer it would take if it was capped at 245.
I have had better results not underclocking while sleeping. I would suggest using setcpu to specify to use the conservative governor when sleeping, ondemand/interactive/smartass when screen on (depending on which one you want), and interactive/ondemand while charging without under/overclocking at all and using the default freqs (245 - 998). I'm certain you would be surprised at how your evo behaves after that.

I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.

aimbdd said:
I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.
Click to expand...
Click to collapse
My last post may have been a bit confusing so I will clarify. When I said underclock I was referring to the practice of capping the max freq to 245 which is what most people do. If you cap the freq at 245 you are essentially underclocked all the time and would cause your cpu to work harder.
The evo underclocks automatically when the cpu load is low enough (idle for example) to save on power, reduce temps, and to basically keep the system running. But I would assume that most of us who have used setcpu have seen how lousy the evo runs when it can't scale up (locked at 245) when using the evo. The governors will underclock the cpu on their own if the device reports it does not need the higher freqs and this occurs during sleep/screen off as well.

Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?

Vulf said:
Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?
Click to expand...
Click to collapse
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.

freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?

freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
This.
Very sound advice and yes some evos can't undervolt as well as others. Always remember too that the stock kernel for the evos use CFS. If you are using a bfs kernel that could also cause issues. Some evos run better with bfs versus cfs but it's really going to come down to the amount of time you want to put into testing and confirming what your evo likes.

Vulf said:
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?
Click to expand...
Click to collapse
Yeah, it does. How far are you trying to overclock before your phone freezes/reboots?

[Q] Kernels ain't working for me

Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock so I have no choice to but to stay on stock kernel. I have no ext3/ext4 partition on my SD card in case you ask.
Current ROM: TB Fusion 1.1.2
Radio: 12.54.60.25U_26.09.04.11_M2
Any idea what should I do to solve this issue?

golokipok said:
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock
Click to expand...
Click to collapse
uoooo this is sooo dangerous for your handset... u can "smoke" it...
Any idea what should I do to solve this issue?
Click to expand...
Click to collapse
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device

SERGI.3210 said:
uoooo this is sooo dangerous for your handset... u can "smoke" it...
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
Click to expand...
Click to collapse
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ). Is there any effect if I'm using smartass profile on those kernels I've mentioned?

golokipok said:
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ).
i hope that the processor works or not works (don´t crashes a little bit...)
but the reason of your freezes maybe (almost sure) because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
golokipok said:
there any effect if I'm using smartass profile on those kernels I've mentioned?
Click to expand...
Click to collapse
it´s possible, take this explanation, read and judge by yourself what´s the better cpu governor...
smartass (Best explanation i've found paraphrases to: based on interactive, but better.)
----
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
Click to expand...
Click to collapse

Thanks for the info
SERGI.3210 said:
because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
Click to expand...
Click to collapse
You have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Anyway, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy

golokipok said:
have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Click to expand...
Click to collapse
you only should do a good over/underclock & set the correct cpu governor for your daily use....
well, you know ho is @MDeeJaay? the developer of MDJ kernels and roms...
he explained smartass with this words:
SMARTASS GOVERNOR - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245.
golokipok said:
, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
Click to expand...
Click to collapse
no, no buddy... i only show the max speed nothing more... i set my cpu concretly like this;
CPU GOVERNOR:interactive
MAX SPEED:1113 MHZ
MIN SPEED:245 MHZ
PROFILE: screen off; 245 MHZ max.
245 MHZ min.
in adition i´m going to modify my syg LOL

haha..thanks again. I'm gonna try playing with the frequencies to see which will suit me
i hope someone can make a stable 1.8ghz kernel without the freeze

IT´S POSSIBLE but i don´t want to try it LOL
i love a lot my DHD

[Q] Daemon controller, what is all this nonsense O.O?!

ok idk ow to overclock correctly i need a way to make this sense 3.5 rom less laggy an run more smoothly, can anybody help me with this???

Yes just use Daemon Controller (basically functions the same as SetCPU) and set your maximum frequency. For most ROMs I would set it around 1.5Ghz, and set the governor to smartass or smartassv2. The governors will depend on the kernel you're using. For a good sense kernel, I would use this one.
Additionally, you can download Incredicontrol via the market and that will enable you to adjust your voltages, based on the frequency steps. A lot of people prefer to bump the voltage up or down 25% to increase performance or reduce battery drain.
I AM NOT RESPONSIBLE FOR ANY PAIN AND SUFFERING YOUR DEVICE MAY INCUR.
If I helped, slap my Thanks button around a bit.

chattguy said:
Yes just use Daemon Controller (basically functions the same as SetCPU) and set your maximum frequency. For most ROMs I would set it around 1.5Ghz, and set the governor to smartass or smartassv2. The governors will depend on the kernel you're using. For a good sense kernel, I would use this one.
Additionally, you can download Incredicontrol via the market and that will enable you to adjust your voltages, based on the frequency steps. A lot of people prefer to bump the voltage up or down 25% to increase performance or reduce battery drain.
I AM NOT RESPONSIBLE FOR ANY PAIN AND SUFFERING YOUR DEVICE MAY INCUR.
If I helped, slap my Thanks button around a bit.
Click to expand...
Click to collapse
0k the number says 245760 i cant tell which is the 1.5 ghz?

245mhz... That is your lowest frequency. You'll set that as your minimum. Your max should be set at 1497mhz. It'll have some numbers straggling on the end but disregard them. 1497mhz = 1.5Ghz.
Sent from my Incredible 2 using Tapatalk