Database Users

Laggy Scrolling?

Is anyone else experiencing this? On web pages or long lists, scrolling around is not nearly as smooth as it should be. My brother has a Hero, and the Evo is not as bad as that... but it is nowhere near as smooth as an iPhone is. If I scroll around quickly, it gets pretty jumpy, where the frame rate slows down a lot. I read another thread (maybe on a different forum) where people claim that it's just the difference between the speed of scrolling and/or the "coasting" feature of the phones, but this is not what I'm referring to. I'm referring to mainly the frame rate of scrolling around and also the lag between when my finger moves and when the action takes place. It is most apparent on bigger web pages and long lists (like the Manage Application list). But it also does not happen all the time.
I have Advanced Task Killer running too, set at "Crazy" and the kill frequency set to "When screen off". Is there anything else I can do to make scrolling smoother?
I'm sick of having my friends who have iPhones playing with it, and immediately commenting on how it's not nearly as responsive.
Any ideas?

I played with an EVO in the Sprint store yesterday and noticed the same thing. While overall I found it to be really fast, in some areas (like switching between home screens) it was noticeably choppy compared to my Hero. Though I should note that my Hero is rooted and running Fresh 2.1.1.
One suggestion I might make is to not use overly aggressive settings with a task killer. This has been known to cause some odd behavior with Android including choppiness.

Working amazingly for me. As close to the smoothness of an iPhone as I've ever seen.
Have you tried a full restore? Keep checking after each app installation to figure out what (if anything) is causing the problem.
Sent from my HTC EVO using Tapatalk

Do you have Live Wallpaper running?

I do not. In fact while "conditioning" my battery, brightness down minimum, WiFi/GPS/4G/Bluetooth all off as well.
Sent from my HTC EVO using Tapatalk

How much free memory do you have?

I noticed the choppiness too but it wasn't too bad, just unfitting of a phone with such high specs.

It's because of the Live Wallpapers, some are more processor intensive than others so some it's more noticeable on than others. Put a regular Wallpaper up and everythings nice and smooth.
I don't use Live Wallpapers anymore, they were cool for awhile but after a couple months of them on my Nexus the novelty has worn off.

I notice it also even with a regular wallpaper..i mean its pretty smooth but it does lag a bit.

I notice laggy scrolling within the HTC-built applications. For example, when looking through contact information or social updates. The scrolling is really bad, and I think that just might be because of the huge amount of information the HTC apps are processing. I'm sure all the social information being pulled from every end of the Internet isn't the easiest thing for the device to do, even if it is the Evo.
Aside from that, everything else is as smooth as butter.

Still stock on mine and I haven't noticed any lag, though I use Dolphin HD and Skyfire.

I don't have Live Wallpaper running, and about 200MB of free memory.
And I don't think it's with the HTC-built applications only. I notice it in most applications. Just put an iPhone right beside it and scroll around on both... huge difference.
I just changed the settings on Advanced Task Killer to Aggressive (down from Crazy) and Every half hour (down from When screen off). Maybe this will help... we'll see. Maybe Advanced Task Killer is not the best app for this? Are there any better ones? Why didn't Google have this built in if it really helped so much with speed+battery life?
Maybe FroYo will fix this issue? Does anyone know when this will be available?

shawnee4885 said:
Maybe FroYo will fix this issue? Does anyone know when this will be available?
Click to expand...
Click to collapse
I have noticed this too at times. Froyo made my Nexus One a hell of a lot faster, it will do the same for the Evo

Still on Stock rom and no root, scrolling, pinch zoom are all smooth and fast.

theoner1 said:
Still on Stock rom and no root, scrolling, pinch zoom are all smooth and fast.
Click to expand...
Click to collapse
Have you compared it to an iPhone though?

shawnee4885 said:
Have you compared it to an iPhone though?
Click to expand...
Click to collapse
I've seen this too and mentioned it to other Android people... and was promptly called a cry baby. I am coming from a 3gs...and just thought it was silly the 1ghz chip in this phone cant compare to the 600mhz chip in the iphone.

Grims said:
I've seen this too and mentioned it to other Android people... and was promptly called a cry baby. I am coming from a 3gs...and just thought it was silly the 1ghz chip in this phone cant compare to the 600mhz chip in the iphone.
Click to expand...
Click to collapse
It's all about the quality of the programming, i'm not calling htc programers bad but it seems like some of their stuff is just slow.

Grims said:
I've seen this too and mentioned it to other Android people... and was promptly called a cry baby. I am coming from a 3gs...and just thought it was silly the 1ghz chip in this phone cant compare to the 600mhz chip in the iphone.
Click to expand...
Click to collapse
First u have to realize that the iphone was built with its gpu base OS. So all the scrolling and animation are base on gpu WITH THE HELP OF CPU. Android will be more dificult since of all its different hardware. Iphone OS is just base on iphone hardware but If iphone was running without gpu support, it would move like crap.
One example of this is zuneHD. it is base on a hardware base on tegra with gpu support and is smoother than iphone since tegra is a more capable gpu chip.
This discussion has been on and off with palmpre guys and waiting for an update to enable gpu support in the OS. Gpu support is supported in game but not in the OS for scrolling etc. Just like android.
This is the reason the iphone can run smooth at low mhz. The iphone 2g even at its low mhz still is smoother in scrolling and transiction than android because of it gpu intigrationbut ofcourse not faster. Hope this help.
Another example is compiz for linux. It create a semi gpu OS of linux and u can see how compiz on linux look light yeat better and smoother than wimdows 7 with a much lower hardware spec.

eduardmc said:
First u have to realize that the iphone was built with its gpu base OS. So all the scrolling and animation are base on gpu WITH THE HELP OF CPU. Android will be more dificult since of all its different hardware. Iphone OS is just base on iphone hardware but If iphone was running without gpu support, it would move like crap.
One example of this is zuneHD. it is base on a hardware base on tegra with gpu support and is smoother than iphone since tegra is a more capable gpu chip.
This discussion has been on and off with palmpre guys and waiting for an update to enable gpu support in the OS. Gpu support is supported in game but not in the OS for scrolling etc. Just like android.
This is the reason the iphone can run smooth at low mhz. The iphone 2g even at its low mhz still is smoother in scrolling and transiction than android because of it gpu intigrationbut ofcourse not faster. Hope this help.
Another example is compiz for linux. It create a semi gpu OS of linux and u can see how compiz on linux look light yeat better and smoother than wimdows 7 with a much lower hardware spec.
Click to expand...
Click to collapse
Thanks that explains a lot, i wasn't aware Android doesn't use GPU support in this area.

I just wanted to throw this in. I know everyone is comparing things like the scrolling framerate to the iPhone's. But there is one slight issue that a lot of developers can tell you off the bat.
JAVA
iPhone is not based on java and android UI is. This is sort of why JIT is slated to make such a big difference. Java is just laggy, especially when it comes to UI. For instance: open office, eclipse, and just about any other java based app I see on linux. GTK apps are fine in ubuntu, but when I open eclipse I just know there is a delay between when I click the "file" menu and when it actually opens.
I noticed it on my hero, and no amount of free ram or killing apps would completely get rid of it. Now I have to say going from the hero to the evo I honestly do not notice any lag. But the UI on the hero just has a solid delay EVERYWHERE you go. But I noticed it was not there as soon as I got into a game written in the dalvik way. It will come, and we will eventually be there. But I don't blame it on hardware. Core2quad in eclipse and the UI lags? Blame it on Java.
Now I know some folks will say "nu uhh. such and such java android app doesn't do that!" But almost all apps for android and sense do this if they are written in java. Some more than others.
One final thing, there are several articles about why you shouldn't use task killers. It became perfectly clear it was a bad idea on some of toast's later kernel. and yes, the memory management can be improved for root users. but for non root users, I know it is counter-intuitive but task killers have major drawbacks. Just do some searching and decide for yourself, but I noticed a huge difference on my hero when I stopped using a task killer and allowed the default memory management to take over. And honestly, on my EVO I don't EVER notice a slow down.

Kernel scheduler improvement.

Hi there a good news for responsiveness.
A patch of 200 lines have been checked and approved by Linus, improving greatly responsiveness maybe it should be interesting to test it on our phones.
News and links available here.
http://www.phoronix.com/scan.php?page=article&item=linux_2637_video&num=1
Sent from my Nexus One using XDA App

Holy hell, thats a monumental difference!

Awesome, I HATE how laggy my Nexus One gets when I'm compiling the kernel with 64 threads.

Integrated it into my latest kernel build...hasn't tested it out yet though...

intersectRaven said:
Integrated it into my latest kernel build...hasn't tested it out yet though...
Click to expand...
Click to collapse
Cool Can't wait to get my hands on this, (But have no time right now) .

Tested with new Rodriguez rom + intersectRaven kernel,
the new room is really nice to use, and the reactivity is awesome !
Really amazing, feel a huge difference in multitasking and fluidity.
Tried with the Miui browser included in the room, the web pages render time are really surprising really nice.

What is the name of the IR kernel you used?

fallingd0wn said:
What is the name of the IR kernel you used?
Click to expand...
Click to collapse
http://www.mediafire.com/intersectRaven
2.6.35.8_AVS-CM-NOBOOST_CFS_20101116_2127.zip

so... does this take care of the "Cannot find CPU Subsystem.." (something like this) errors in the logcat when the CPU is pegged ?

buttery smooth!! thanks!!

holy ****. so smooth. got 22fps in nenamark

vivanshah said:
holy ****. so smooth. got 22fps in nenamark
Click to expand...
Click to collapse
Doubt thats related as this particular fix is about scheduling.
I get 21.7 FPS @1113, old 2.6.35.7 CM kernel

I'm not seeing any improvement actually...
Sent from my Nexus One using XDA App

What benchmarks would this show up in on the n1?

There's no benchmark about responsiveness or latency of the system at the moment.
But you really can feel it with multitasking.
I've nimbuzz, Skype, tweetdeck, Gmail, Ms email etc everything always ON.
I switch a lot between applications and so I really fell the difference not freeze while switching between browser and calandar music etc.
My nexus one is clearly under heavy usage with me all the time.
So since there's no benches I cannot tell exactly how good it is. But phoronix speak about
-10% lag
+60% responsiveness
Which is awesome! Even just half of that would be excellent!
Sent from my Nexus One using XDA App

liam.lah said:
What benchmarks would this show up in on the n1?
Click to expand...
Click to collapse
What is wrong with you people??? If you can only see it in a benchmark, who cares?

teh_lorax said:
What is wrong with you people??? If you can only see it in a benchmark, who cares?
Click to expand...
Click to collapse
Nothing wrong with me, would just like to see some real stats, its way too easy to think things "feel faster" especially if you are expecting them to, just like some people feel certain UV kernels have longer life than others, unless you actually do the numbers(which was done), it is really just what people "feel", and that is extremely unreliable.

IntersectRaven - how did u integrate the patch, i am unable to integrate it cleanly

Great!
Applied to PureFroyo kernel. Let's test.
http://forum.xda-developers.com/showthread.php?t=820172

got it to compile, now testing

JIT on galaxy s

Recently, I finished finally modifying the xperia x10 that I have and one of the greatest improvements that those guys achieved was getting a lot more processing power by enabling JIT.
So naturally after seeing it work miracles on the x10, I went to look for it on my captivate and so far have come up with nothing anywhere. I saw some discussion in the past about it but nothing beyond.
Hopefully somebody can enlighten and if such a thing does seriously want to be worked on.... Here's a thread!
Sent from my GT-I9000 using Tapatalk

FroYo (2.2) and later have Just-In-Time compilation (JIT) out of the box. There are probably a dozen FroYo ROMs on the front page alone, so pick one have fun!

From what I've read, it's been a part of the ROMs since 2.1 but it needs to be enabled. Is this the case here or am I missing something?
Sent from my GT-I9000 using Tapatalk

kr3w1337 said:
From what I've read, it's been a part of the ROMs since 2.1 but it needs to be enabled. Is this the case here or am I missing something?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
That is one of the biggest parts of froyo is that it enables JIT...so if you run a rom that has froyo its enabled unless I'm mistaken...
Sent from my GT-I9000 using XDA App

JIT is enabled by default in all Froyo ROM's. You can check the build.prop for ****s and giggles though.
The Galaxy S won't show the kinds of scores that Qualcomm based devices will, even with JIT enabled. Qualcomm included 128-bit SIMD Floating Point extensions with Snapdragon, while the Hummingbird only has 64-bit extensions.

yes with jit we get a 60-70% improvement but a qualcom gets 300%+ in floating point operation. in modern computers there are many other factors though and quardrant cpu scores are still very high for our chip (if you use the pay version you can see the score breakdown). so dont let the linpack scores discorage you. ive gotten as high as 18.2 in linpack with some overclocking though, which isn't bad. it's not the 50+ in the qualcom phones with some mods but not bad.

So that's what the story is, thanks guys! Wondering if things could be improved beyond overclocking...

I know it can be but don't know how. Some guys are getting 25+ in linpack on there website. So there is something else holding us back a bit.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

Dani897 said:
I know it can be but don't know how. Some guys are getting 25+ in linpack on there website. So there is something else holding us back a bit.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
You talking about xperia x10? really 25 on linpack? I dunno if that is even possible to OC to astronomical speeds. They run on older hardware and I think most are still on 2.1.....

All Android ROMs have a JIT compiler, it literally is what compiles all the Java on the fly. Newer versions are optimized for better performance.
So the better question is do the 2.2 Froyo ROMs have the latest JIT compiler version available or does the Nexus S have a newer more performant version we can steal. More than likely it will not work with 2.2 since the Nexus S is using 2.3.
From everything I have heard the newer JIT comp versions are optimized for the Snapdragon chipset more than anything. Which doesn't do us much good.

2.2+ have the JIT. Prior to 2.2, all programs ran entirely as interpreted bytecode on an isolated virtual machine. In 2.2+, the JIT translates the most cpu "heavy" bytecode down to native instructions during execution, stores it in cache, then runs it natively on the processor in a protected mode. Dig the video below, it's an hour long but the functionality of the JIT is explained in the first 15 minutes.
^Edited the above to accurately describe the function of the JIT
http://www.youtube.com/watch?v=Ls0tM-c4Vfo There you go, dudes. JIT Demystified.

modest_mandroid said:
2.2+ have the JIT. Prior to 2.2, all programs ran as bytecode on an isolated virtual machine. In 2.2+, the JIT translates the bytecode down to native instructions just before execution, then runs it natively on the processor in a protected mode. Could be wrong, but to my understanding, that is the major difference between 2.1- and 2.2+.
http://www.youtube.com/watch?v=Ls0tM-c4Vfo There you go, dudes. JIT Demystified.
Click to expand...
Click to collapse
This is what I saw and know too. However, I believe that the compiler that we are using is rather old and has some room for improvement. The nexus S compiler working on the captivate is a possibility that could become true after the 2.3 port is finished, provided that the developers look into it.
Sent from my GT-I9000 using Tapatalk

Making my Evo any faster?

So I've been messing around with different roms and kernels for the past few weeks and finally settled on CM6 6.1.1, and the snap 7.6 bfs kernel, for stability and speed. I turned on the turbo mode with snap, OC'd to 1152mhz (freezes at 1192), killed all apps, and ran quadrant.
[Picture of a 2330 benchmark screencap was supposed to go here, but I don't have eight post haha]
I know thats pretty good, my scores average from 2100-2350, but I'm looking to make it even quicker. What can I do?
Thanks!

Move to gingerbread.
Sent from my PC36100 using Tapatalk

sultan.of.swing said:
Move to gingerbread.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Which ROM and which kernel?
weehooherod said:
Don't use Snap 7.6 on CM6.1.1, just use the stock kernel. The new kernel built in with CM6.1.1 is much better, Snap 7.6 is pretty old.
Click to expand...
Click to collapse
I had 6.1.2 flashed, but snap wouldn't work on it and I was only benching around 1400 with the stock kernel.. Even with an OC

xsaqzw said:
Which ROM and which kernel?
I had 6.1.2 flashed, but snap wouldn't work on it and I was only benching around 1400 with the stock kernel.. Even with an OC
Click to expand...
Click to collapse
Benchmark scores don't matter. I don't even check them anymore. Wether I get a 1400 or 2200 its still gonna dial a number at the same speed. Im not playing call of duty on my phone or anything. I want efficiency.

A benchmark does not actually show how fast your phone is....
Cyanogen himself stated this.

quadrant scores =/= to your phone being 'fast'.
But if you care about synthetic benchmarks then you could trick your file system into giving you quadrant scores in the 3000+ range.
by the way thanks for posting this in the relevant subsection of the evo forum dedicated to development this will absolutely further the development of android.

Yeah man, don't worry about benches. If you want to brag about how high it is just PhotoShop it. It's all about smoothness and real world performance/battery life for me. Just find what setup works best on your phone
Edit: and this goes in the q and a section

Lol okay then guys, so which gingerbread ROM and which kernel for the best efficiency and speed?

david279 said:
Benchmark scores don't matter. I don't even check them anymore. Wether I get a 1400 or 2200 its still gonna dial a number at the same speed. Im not playing call of duty on my phone or anything. I want efficiency.
Click to expand...
Click to collapse
I couldn't agree more, how instant can a phone get? Theres a point where speed wont be relevant anymore and its pretty damn close to it already. In my eyes efficiency is the future, doing more with less is something im looking forward to.
Sent from my Warm TwoPointTwo RLS5 Beta'd out Evo

lexusmike said:
Yeah man, don't worry about benches. If you want to brag about how high it is just PhotoShop it. It's all about smoothness and real world performance/battery life for me. Just find what setup works best on your phone
Edit: and this goes in the q and a section
Click to expand...
Click to collapse
**** man I'm sorry I'm new to this forum.
Mods: Please move to the correct section.

Thread moved to General.

Also keep in mind that the EVO's Snapdragon CPU was never a problem, it's still competitive even with the newer CPUs (with the exception of the upcoming A9's both single and especially dual core). Most of the "hacks" that raise the Quandrant score over 2000 are just that, hacks. They manipulate the other tests (non-CPU specific ones) to raise the score and make you think that you've just achieved some kind of new level of performance when in fact you'll see pretty much no difference.
Over clocking will help a little but like I said the problem isn't the CPU; a lot of the lag you may see on the EVO is because of the GPU. Nobody has figured out out how to overclock the GPU so over clocking the CPU will make no difference with the GPU. There have been some improvements in the drivers and if you're running CM or MIUI, you already have them. Gingerbread slightly improves some of the core graphics in Android so you'll see a boost over pre-Gingerbread Android but I think what we should all be waiting on is for the new Adreno 200 GPU drivers that Google will release when the OTA 2.3 update for the N1 drops. It wont magically make our EVO's into Nexus S' or anything but I wouldn't be surprised to see a noticeable boost in performance.

Oddly enough, I'd rather have the transition animations that come with some of the custom ROMs, even if they take longer. They provide a much more "fluid" experience. I don't like the jarring, speed-driven, animation-free transitions that come with stock ROMs, because they lack polish. As soon as I saw videos of those animations, I was in love. LOL. Seriously though, lag and lack of animations (which consequently actually help hide lag and load times) are the two things I see holding back the polish of Android. Just as an example (not trying start a flame war here, people), look at the animation when going from portrait to landscape in iOS. Then look at Android's lack thereof. THAT is what Android needs-to actually FEEL faster, not necessarily BE faster. So try something like that if you want the phone to feel more fluid instead of just achieving raw benchmark speed. Again, just my opinion (kind of sad that I feel the need to put that disclaimer in every post lately).

Award Tour said:
Also keep in mind that the EVO's Snapdragon CPU was never a problem, it's still competitive even with the newer CPUs (with the exception of the upcoming A9's both single and especially dual core). Most of the "hacks" that raise the Quandrant score over 2000 are just that, hacks. They manipulate the other tests (non-CPU specific ones) to raise the score and make you think that you've just achieved some kind of new level of performance when in fact you'll see pretty much no difference.
Over clocking will help a little but like I said the problem isn't the CPU; a lot of the lag you may see on the EVO is because of the GPU. Nobody has figured out out how to overclock the GPU so over clocking the CPU will make no difference with the GPU. There have been some improvements in the drivers and if you're running CM or MIUI, you already have them. Gingerbread slightly improves some of the core graphics in Android so you'll see a boost over pre-Gingerbread Android but I think what we should all be waiting on is for the new Adreno 200 GPU drivers that Google will release when the OTA 2.3 update for the N1 drops. It wont magically make our EVO's into Nexus S' or anything but I wouldn't be surprised to see a noticeable boost in performance.
Click to expand...
Click to collapse
that is interesting.. thanks for the info.
I hope it does open some more performance and maybe a way to overclock the GPU

Im not playing call of duty on my phone or anything. I want efficiency.[/QUOTE said:
Lmao
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse

What's the point of overclocking???

Ok I aint joking but seriously what is the point of overclocking a Desire z/G2. Unless I am running on a slow phone I don't see the point. Stock speed never lags and i haven't seen any difference between 1.5 ghz vs 800mhz.
The only time when 1.5ghz clock speed is useful is when i running quadrant and rubbing its scores infront of my friends face.
There is any areas where you can actually see the performance difference?

bluntly, if you dont see the point of it then you don't need it.
For others, sometimes you run alot of stuff in the background and still want to be able to have your main app perform at its best level.
There is also the minute tweaking of speed and snappiness of the interface. The idea of instant reaction when you open your message app, or your email, or anything.

bruceko86 said:
Ok I aint joking but seriously what is the point of overclocking a Desire z/G2. Unless I am running on a slow phone I don't see the point. Stock speed never lags and i haven't seen any difference between 1.5 ghz vs 800mhz.
The only time when 1.5ghz clock speed is useful is when i running quadrant and rubbing its scores infront of my friends face.
There is any areas where you can actually see the performance difference?
Click to expand...
Click to collapse
Heavy multitasking
Sent from my HTC Vision using Tapatalk

flash video seems pretty laggy to me at 800...

http://lmgtfy.com/?q=overclocking
Sent from a Western Union telegram.

blackknightavalon said:
http://lmgtfy.com/?q=overclocking
Sent from a Western Union telegram.
Click to expand...
Click to collapse
Best link ever! I hope i can remember it long enough to use it sometime.
Sent from my HTC Vision using XDA Premium App

blackknightavalon said:
http://lmgtfy.com/?q=overclocking
Sent from a Western Union telegram.
Click to expand...
Click to collapse
Ya i know what overclocking is but I haven't found one instances where I needed it to run an app. G2 is already damn fast and it runs android with no lag but I really see no point until more demanding ver. of android come out.
I just wanted to see who overclocks their G2 everyday and for what purpose.

bruceko86 said:
Ya i know what overclocking is but I haven't found one instances where I needed it to run an app. G2 is already damn fast and it runs android with no lag but I really see no point until more demanding ver. of android come out.
I just wanted to see who overclocks their G2 everyday and for what purpose.
Click to expand...
Click to collapse
Fair question IMHO.
I don't see the difference when overclocking, or rather I don't feel it. Software does make a difference, but not the extra 200-500Mhz. I do feel however the battery drain

It always makes me laugh when somebody asks a legitimate question and you get silly responses like the above 2. It's as if these people feel threatened and have to justify that they are more knowledgeable than the op. The facts of the matter are most of the tweaks, mods and alterations are wholly unnecessary in the real world.

If you don't feel like it makes it better then you don't have to use it. I use it because I feel it makes everything just a little snappier and more instant. If you don't notice a difference that's fine. It's probably trivial for me to notice the little hang ups but I can't help it.
Sent from my HTC Vision using XDA App

For me there's several reasons. For the most part, the reason for oc is because you can. But there are practical reasons as well. For example, with the stock ROM running at 800MHz, you're stuck with that. With an oc kernel and using SetCPU or built in clock settings in CM, you can adjust it as needed. Gonna play a game? Bump it up to 1GHz or so. Done with said game? Take it back down to 800MHz. But it's not all about oc. Sometimes there's a need to underclock. Getting low on battery and don't have a charger near by and need to squeeze another hour or two out of it? Maybe take it down to 768MHz or 600MHz (if you're running Pershoot's kernel).

Dungeon Defender:
800 mHz : not fun, laggy
1.5 gHz : fun, graphic are more smooth

Reasons for using over clocking:
Because I can
Because sometimes I do notice the difference in performance of the UI and some applications (wait for Sense 3.0 etc...)
Because I also use it to underclock.
Like everything else, a lot of it is perception. My wife cannot see any difference between our normal cable channels and the HD ones. I can (or am I just trying to convince myself that I can?). Oh well.

Finally some practical and helpful responses, showing an understanding of the need for information from some people.

here's my experience when it comes to overclocking. keep in mind that, like with your computer, it does vary from user to user... so I'm making these statements from MY experience, not making blanket statements regarding all of our devices:
- if you run multiple homescreens with multiple widgets and ui "smoothness," not just aesthetically, but performance-wise as well, is of concern, mild overclocking becomes necessary.
- if you have several apps running at any given time (in background or foreground) and ui smoothness, same definition as above, is of concern, mild overclocking becomes necessary.
- if you run any iteration of a sense rom in any configuration and ui smoothness is of concern, mild overclocking becomes necessary.
- if you run PSX/N64 emulators and you don't want audio distortion or general lagginess, more aggressive (in my case, 1209 is a safe speed for maximizing performance without having a drastic effect on battery life) overclocking becomes necessary.
on AOSP builds, especially gingerbread-based, I don't think there is a necessity for more processing power than what we get from the factory if you're running a relatively slim setup and aren't using something like a PSX/N64 emulator regularly.

I run mine at 1ghz, but I did use 1.2ghz before. I do notice a slight performance difference. Overall tho I don't notice it much. I notice it more when I'm doing multiple things.
Nonsense!

OneGoodKnock said:
Finally some practical and helpful responses, showing an understanding of the need for information from some people.
Click to expand...
Click to collapse
For all that you're talking, you have yet to provide anything of value to this conversation while you're sitting up there berating those other 2 posters.
Think about it.
Sent from my Desire Z via XDA App

I run 1.1 because it is noticably faster. Everything opens faster and works smoother. My wife has a stock G2 and when I grab it to look something up on the web or to use maps when we're out, I instantly notice how mucher slower hers is.
Works for me so I use it.

I notice a definite performance boost on mine, but it also depends on which kernel/ROM you use. I was running meXroid for a few days and found that it got extremely laggy even overclocked with Flippy's kernel built in (1.9Ghz), plus my battery was dying faster than a Chuck Norris joke. PyroMod has always been reliable for me and I flashed back to 2.0 earlier and it's just as reliable and power-saving as ever.

mputtr said:
For all that you're talking, you have yet to provide anything of value to this conversation while you're sitting up there berating those other 2 posters.
Think about it.
Sent from my Desire Z via XDA App
Click to expand...
Click to collapse
Thanks for that.