Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Yes, it *should* fix screen tearing, but 4.3.1 only had a generic HAVS version, while 4.3.2 went back to both a more and less aggressive version. So, you could *potentially* still see some screen tearing on 4.3.2 with aggressive HAVS. It is less likely, though.
What if you spend a lot of time listening to mp3's or streaming audio? Any opinion as to whether HAVS would help or hurt in that case?Some people notice worse battery life when using a combination of setcpu profiles and HAVS. In theory, though, there is absolutely nothing wrong with doing it. Setcpu profiles deal with variable frequencies, while HAVS deals with variable voltage. They do not conflict. That being said, certain battery savings methods are actually worse for the battery when used incorrectly. Such is the case with setcpu profiles because it has to constantly check if the state has changed. As for HAVS, this is the general rule:
1) If you use your phone constantly, and it spends more time awake than with the screen off, don't use HAVS. You'll just be forcing the cpu to constantly change the voltage.
2) If you use your phone a light to moderate (or even heavy in spurts) amount, use HAVS. You see the benefit to HAVS when the screen is off for longer periods of time. This is the case for most people, which is why it works well for most, but not all. Of course, it varies from phone to phone as well. This is a generalization, only.
What if you spend a lot of time listening to mp3's or streaming audio? Any opinion as to whether HAVS would help or hurt in that case?
Some people notice worse battery life when using a combination of setcpu profiles and HAVS. In theory, though, there is absolutely nothing wrong with doing it. Setcpu profiles deal with variable frequencies, while HAVS deals with variable voltage. They do not conflict. That being said, certain battery savings methods are actually worse for the battery when used incorrectly. Such is the case with setcpu profiles because it has to constantly check if the state has changed. As for HAVS, this is the general rule:
1) If you use your phone constantly, and it spends more time awake than with the screen off, don't use HAVS. You'll just be forcing the cpu to constantly change the voltage.
2) If you use your phone a light to moderate (or even heavy in spurts) amount, use HAVS. You see the benefit to HAVS when the screen is off for longer periods of time. This is the case for most people, which is why it works well for most, but not all. Of course, it varies from phone to phone as well. This is a generalization, only.
Well, I basically what I meant by "screen off" was when the phone is asleep. If you're listening to mp3s with the screen off, the phone is obviously still awake, and the frequency is going to change. If you use it a lot, as in most of the day, that way, I would say you might benefit by not using HAVS. It's not a one size fits all rule. Try both. In theory, you might get better battery life out of noHAVS.
so if i sync email to my phone every hour at peak hours and as it comes on non peak does that mean its not really off since there is running processes in the background? and therefore it will be more benefitial to use the no-havs over the havs?
please advise.
thanks.
Well, here's the thing - if you're using HAVS, the voltage is going to change as the frequency does. If you have a screen-off profile, the frequency will not go higher than you tell it to, so HAVS is irrelevant. Things that sync, though, do need to wake up the phone. That's what wake locks are. They should only last for a few seconds - a few minutes. Anything that holds the phone awake longer than that isn't releasing its wake locks. That's when you have a problem. HAVS should matter that much unless you don't have a screen-off profile.