Related
Same page same wifi,
Notebook HTC desire
2.2GHz dual core 1GHz
4GB DDR3 576MB ram
added better video with more sites, and still, HTC Desire wins
Show a video erasing the cache on each browser before doing the test which would be fairer.
Sent from my HTC Desire using XDA Appwo
i did this before video, i cleaned all task, cache and history, also htc desire was fresh boot.
You can try yourself...
well ... although i agree that the desire browser is really fast ... i have to say, your pc's chrome is terribly slow.
when i compare loading engadget in my chrome it doesn't even take half the time to load and it's way faster than my phone can do it
core2duo 3ghz
4 gb ddr2 ram
Mondaro said:
well ... although i agree that the desire browser is really fast ... i have to say, your pc's chrome is terribly slow.
when i compare loading engadget in my chrome it doesn't even take half the time to load and it's way faster than my phone can do it
core2duo 3ghz
4 gb ddr2 ram
Click to expand...
Click to collapse
maybe you are using desktop computer (and your cpu is 1,6GHz faster ) and faster internet, and also, you in Germany, so closer to server than me.
There's no doubt a PC or laptop is faster than the Desire. Comparing them makes no sense.
Tips to OP: try Opera Much faster than Chrome (on PC)
Oooh yeah here it comes... yes of course, opera is faster then Chrome.... of course....
Sent from my HTC Desire using XDA App
Zhypr said:
There's no doubt a PC or laptop is faster than the Desire. Comparing them makes no sense.
Click to expand...
Click to collapse
Well, computer can do tones of jobs.
But phones are optimized to do certain jobs better, and browser is one of optimized programs. (This would be my guess)
Opera is faster than chrome and webkit
You don't have the same computer then he has, and chrome is faster. Next you probably didn't use same connection, and even if you did, your pc had privileges over the phone.
It would be completely fair if you'd compare 2 same speed wi-fi connections, and use slower PC. You simply can't put 2,86TFLOPS PC versus 40MFLOPS phone, right?
EDIT:
And by the way, your desire is loading pages slower then his and mine.
Just to add to the conversation I have done some testing with browsers recently (Mainly Chrome/IE and Firefox)
And I must say Chrome is has some serious issues. For instance Firefox will load a page in less than a second and on the same machine Chrome will take about 20 seconds.
Also another bug I have noticed with Chrome it will intensivley hog the Ram useage and even CPU useage on certain machines. I first noticed this because one of our computers at home is rigged up to our 32" TV for watching stuff using WMP on the TV. Now the computer isn't high spec but reasonable and plays all these videos fine (from local hdd) but as soon as 1 Chrome page is open (1 tab) you will notice the video keeps pausing/jumping/skipping and in places become un-watchable and simply closing Chrome (without restarting the video) fixes the problem and you can see the ram and cpu drop dramatically even while still playing the video.
I don't know what is about Chrome but I have tested it on a few machines and got similar results (apart from one seemed to be ok) and Firefox has been the quickest out of my tests. Although IE sometimes (rarley) opened quicker the FF most of the time IE just crashes when you open it for the first time. Chrome opens very fast and normally the fastest to open but web browsing not always that quick and hogging system resources I stick to FF with no issues what so ever (apart from one crash in the last 2 months and when it re-opened all of my (10) tabs where open within 30 seconds and ready to go.
kilohercas said:
Well, computer can do tones of jobs.
But phones are optimized to do certain jobs better, and browser is one of optimized programs. (This would be my guess)
Opera is faster than chrome and webkit
Click to expand...
Click to collapse
Opera on PC FTW
Opera mobile FTL
max_carpenter said:
Just to add to the conversation I have done some testing with browsers recently (Mainly Chrome/IE and Firefox).
Click to expand...
Click to collapse
First of all I'm very happy with my stock browser in Desire.
As to the desktop browsers; I am totally agree with your comment on Chrome, it has issues and besides a ram and cpu monster. Firefox is working well but is slow especially at first launch. Have you ever tested Safari? It is my default browser since the day I hv installed and begun to use it.
Sent from my HTC Desire using XDA App
I have never had any of these issues you are talking about. my chrome is ridiculously fast, and does not eat more then 50MB RAM. By the time writing this(4tabs) it uses 8-11% of the CPU, and that's because of that annoying flash ad here -.-' (Now it's 0-4% when I scrolled down a bit)
There are only four problems I have experienced are these:
1.) Since first beta chrome starts up MUCH slower, but still MUCH MUCH faster then other browsers. But he can do now much MUCH more things of course
2.) The omnibox sometimes takes time to detect the site I want. Rarely.
3.) Sometimes(rarely) it "forgets" to auto-fill my login details, rarely but unfortunately on my most visited forums, that's these too =/
4.) It is too good for some people
Well, i am using only firefox, and it use just 20% of cpu (opening page)
So it would be like 0.9GHz 100% loaded cpu
HTC desire load pages by using 80~99% of cpu, so it same as desktop computer.
That's why HTC desire some times will load it quicker.
But if website is flash based, or have lot of java, it becomes quite slow.
Dany0 said:
It would be completely fair if you'd compare 2 same speed wi-fi connections, and use slower PC. You simply can't put 2,86TFLOPS PC versus 40MFLOPS phone, right?
Click to expand...
Click to collapse
Sorry mate, but Intel i7 extreme (6 cores) has only 0.1TFlops peak performance, not 2.86TFlops (with HT )
We are talking about overall PC performance. Besides, Core i7 may, maybe, have 0,1TFLOPS in linpack, but it's real performance is about 2,86TFLOPS. That perfectly fits with the 5TFLOPS HD5970
I have started to notice the performance of my htc Desire degrading.
Apps take longer to load. Where before it was almost instant, now I have to look at plain black or white screens while the apps load.
Not sure what could be causing the problem. Anyway i can find out whats the causel?
Its a stock unrooted 2.1 desire.
Only things i have loaded recently is HTC IME keyboard mod and "what the doodle". all other apps were running for a long time.
Stock Unrooted 2.1? Just install 2.2, it's much faster.
I have found that the amount of available memory/RAM decreases the more you use the device. Not sure if its due to a memory leak somewhere, apps getting greedy with RAM, or what. I find that when it gets to a point thats too low for my taste, or performance starts to degrade, a simple restart works to clear up the issue. This happens even with a task manager, so I am not sure what the cause of the memory degradation is.
Mine did the same whilst on 2.1
Does a re-boot not speed things back up? If not it could be a dodgy app hogging memory.
When this happened to me, I fixed it by backing up using mybackup pro (worth every penny) and doing a factory reset. Takes only half an hour, and gets your desire back to box fresh speedy. Just be mindful of which apps you put back on.
I also take it your stock desire is branded? When your carrier releases 2.2 to you, you'll see a vast improvement too.
Sent from my HTC Desire using XDA App
I noticed this on my Desire (2.2 custom ROM) just now, and it seems to be a memory thing as according to "Android System Information" the CPU usage is low (under 10%) while the RAM usage is high (only 7% free). Is there any way to prevent the RAM going so low and performance degrading as a result? Will a task killer help for this? (I've read not to use them as Android's meant to take care of tasks but if it's not doing a good enough job of clearing up old tasks then surely it would be better to use one?)
Es task manager works well for me when my ram is getting low. Nice not having to reboot. Im on froyo 2.2
Sent from my HTC Desire using XDA App
Stock Desire on 2.1 used to slow down once it got to about 40mb free. Now running 2.2 and its always above 100mb. Runs fast all the time now but I keep my task manager from the 1.5 days as its handy to know what is running and using up the RAM
Sent from my HTC Desire using XDA App
ergoulf said:
Es task manager works well for me when my ram is getting low. Nice not having to reboot. Im on froyo 2.2
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
What do you do in ES Task Manager to free up your RAM? I tried "Kill All" but it didn't seem to have much effect (still stays at around 40 MB free). Had to restart in the end to get the performance back up to scratch (now has over 140 MB free).
Whiterin said:
I have found that the amount of available memory/RAM decreases the more you use the device. Not sure if its due to a memory leak somewhere, apps getting greedy with RAM, or what. I find that when it gets to a point thats too low for my taste, or performance starts to degrade, a simple restart works to clear up the issue. This happens even with a task manager, so I am not sure what the cause of the memory degradation is.
Click to expand...
Click to collapse
Same issue here and i suspect that default browser is the cause.
When free RAM goes very low, generally after one or two days from the startup in my case, i use free app OSManager to see all running processes. This app shows several instances of default browser process (called Internet), each one eating 40-50 Mb of RAM and in sleep state (not zombie). System never removes them and manual killing doesn't work, so there stay in memory over time. I tried different task managers, but only OSManager shows this detail.
To confirm this hypothesis, now i start to use Dolphin instead of default browser: in a couple of days, i will know if the issue is still present.
onmichele said:
Same issue here and i suspect that default browser is the cause.
When free RAM goes very low, generally after one or two days from the startup in my case, i use free app OSManager to see all running processes. This app shows several instances of default browser process (called Internet), each one eating 40-50 Mb of RAM and in sleep state (not zombie). System never removes them and manual killing doesn't work, so there stay in memory over time. I tried different task managers, but only OSManager shows this detail.
To confirm this hypothesis, now i start to use Dolphin instead of default browser: in a couple of days, i will know if the issue is still present.
Click to expand...
Click to collapse
Well, this isn't the cause for me as I have always run Dolphin Browser HD on the Desire. I don't use the default browser. I think it's mainly system processes that just stack up in the background. I found that going through and trimming the list of system processes did free up the memory, but it's just as fast to restart the device.
Hey guys. Anyone found a fix to the lag issue when scrolling up and down in the apps drawer? To know more that I mean, pls click on the below 2 links:
http ://forum.xda-developers.com/showthread.php?t=679037&highlight=scroll+speed
and
http ://forum.xda-developers.com/showthread.php?t=657569&highlight=lag+program+menu+htc+desire
That's strange, I don't experience any lag at all... It's supersmooth and fast.
Ditto, smooth as anything here
Are you using a live wallpaper? one thing i've noticed is cpu intensive live wallpapers make scrolling the apps menu lag quite badly. At a guess i'd say live wallpapers remain running when the apps menu is displayed.
Switch to a static wallpaper or the relatively undemanding htc sense live wallpaper, see if it makes a difference.
Weird..no lag here.
Super smooth.
Yeah, I have a solution for you: buy an iPhone!
Okay, enough trolling. I experienced that as well, but it suddenly stopped and now it's very smooth. I don't know what I did, but I am certain that it stopped after the second 2.2 OTA.
I have a few different ideas you can try. I do all of these on my own phone and it's snappy as anything, even though I've limited the clock speed to 650 maximum.
1) Copy everything back to your phone if you currently have most/all things on your SD card, leaving the things on your SD only if they're actually big. Say, everything below 2mb keep on your phone.
2) Install a different launcher, like ADW. Aside from possibly being a little faster, it allows you to customize your app drawer and remove things you don't need. For example I've removed everything I already have an icon on my home screen for, and now I only use the app drawer for odds and ends or things I'm still deciding if I need them or not - like, 15 things at most usually. I don't even NEED to scroll!
3) Install a better OS, like Cyanogenmod. It's faster in general.
4) Install an OS (or patch/script) which allows you to use an EXT partition on your SD card for apps. EXT2/3/4 are much faster and lower-latency than FAT32.
5) Use SetCPU or a similar app to increase your CPU's MINIMUM speed while the screen is on, from 245 to 384. This will eliminate the initial stutter your phone may have before it decides to clock up the CPU. Even though it's a 50% increase or whatever, in practice it will have virtually no effect on your battery life since it will only take effect while the screen's on - at which time your screen will be using lots more power than the CPU does at any speed.
If #5 solves it for you, just remember the stuttering you're experiencing is only for the sake of battery savings, it's got nothing to do with your phone's performance. In that sense, it highlights one of Android's features rather than a deficiency, even if it's doing this in an unattractive way!
nawoa said:
I have a few different ideas you can try. I do all of these on my own phone and it's snappy as anything, even though I've limited the clock speed to 650 maximum.
1) Copy everything back to your phone if you currently have most/all things on your SD card, leaving the things on your SD only if they're actually big. Say, everything below 2mb keep on your phone.
2) Install a different launcher, like ADW. Aside from possibly being a little faster, it allows you to customize your app drawer and remove things you don't need. For example I've removed everything I already have an icon on my home screen for, and now I only use the app drawer for odds and ends or things I'm still deciding if I need them or not - like, 15 things at most usually. I don't even NEED to scroll!
3) Install a better OS, like Cyanogenmod. It's faster in general.
4) Install an OS (or patch/script) which allows you to use an EXT partition on your SD card for apps. EXT2/3/4 are much faster and lower-latency than FAT32.
5) Use SetCPU or a similar app to increase your CPU's MINIMUM speed while the screen is on, from 245 to 384. This will eliminate the initial stutter your phone may have before it decides to clock up the CPU. Even though it's a 50% increase or whatever, in practice it will have virtually no effect on your battery life since it will only take effect while the screen's on - at which time your screen will be using lots more power than the CPU does at any speed.
If #5 solves it for you, just remember the stuttering you're experiencing is only for the sake of battery savings, it's got nothing to do with your phone's performance. In that sense, it highlights one of Android's features rather than a deficiency, even if it's doing this in an unattractive way!
Click to expand...
Click to collapse
I have my Desire set at 768 max and there really isn't a noticeable difference from the normal 998. Hell. I clocked it way down and it was still WAY faster then my HTC Magic ever was. It's funny that the Desire's processor is faster at 3xx mhz then the Magic's is at 710mhz. I found the Desire to be unstable for sustained periods of anything under 700mhz though. Is yours running stable at 650? Maybe it was just the 691mhz speed I was using.
Hi folks,
I've been using HOX since launch, I always face the problem on multitasking.
I have usenet reader, dolphin browser opening 2-3 tabs and a game called diamond blaze running together, but the game always restert not resume, browser always reload, which is quite anoying.
I follow the guide here to modify the minfree value (use the smallest amount one), it is a bit better but I still face the same issue. I also flashed ARHD, CM10, but I can't see any better.
Furthermore, I notice that said I have usenet reader, dolphin, quickpic running. I've switched between them and make sure they can resume, and I put the phone to sleep for a while, these app can't resume again!! It seems that something is running at the back to reclaim memory and kill my tasks.
May I know if this is the default behaviour of android, problem on modifying minfree value, or my problem?
I'm on the xda app so before I probably get flamed for asking a question I'm not even sure others have asked because there is no search function for topics your reading on or etc.... I have issues where my browser just closes out not force closes just closes and goes back to the home screen almost like android was clearing it for memory like I wasnt using it...it does the same when I'm in the browser and listening to music it constantly closes whatever I'm using to listen to music , is this just me ?or is there a way to fix it
Sent from my Amazon Kindle Fire using xda app-developers app
I'd bet flash is the problem. Try disabling it/using a browser without it. Ensuring you're not set to Desktop in preferences may help also. I mostly use Opera mobile with no flash and get very few crashes but also use Boat browser with flash set at desktop for some sites and it crashes all the time.
Another possibility is that it is hogging too much RAM, and just closes. I have had that happen when I have too many tabs open..
Sent from my Amazon Kindle Fire using Tapatalk HD
I think its a memory problem aswell.
It happened alot to me when i was using maxthon, so i switched to the dolphin browser seems to do a better job at memory management then maxthon.
Also if you have a custom rom you can turn off the ram purging option in the performance settings menu.
There weren't the same problems with browser crashing in ICS, so it's not all memory. I generally believe RAM tweaking to be placebo; in my experience the only thing that improves low RAM problems in the real world is more RAM, however making sure you don't have a load of processes running in the background is key to good performance on this device. I freeze Google Maps when I'm not using it, switched from the Gmail app to Aqua Mail, freeze almost everything freezable in the system, auto kill startup at boot of many apps.
Fast Reboot is a handy little widget to free up RAM and let you know what's running. I usually have 100 to 140mb free RAM on TWA_Priv's latest and greatest.
Thanks for the Maxthon tip John, looks like a nice lightweight browser.
Are you using silk? If so that may be the problem. It's extremely sluggish and buggy.