Related
If you run lots of memory heavy software, is it better to run a LOWER pp, or higher? It was my thinking that a lower number, like 4, would allow more things to run well at the same time. I just read a comment that says the opposite; someone suggested a pagepool of 8 if you run lots of memory heavy stuff...I use GPS software that tends to take up a lot of ram, and I am just never sure which pagepool number to use for myself
The higher the page pool the faster your phone will be running apps, but then there is the balance between speed, and running out of ram.
The best idea is to try a 6meg PP, run as MUCH as you think you will at the time, MAX out your ram usage, and see if you have 2megs to spare, if so, then an 8meg page pool will speed things up.
Dillsnik said:
If you run lots of memory heavy software, is it better to run a LOWER pp, or higher? It was my thinking that a lower number, like 4, would allow more things to run well at the same time. I just read a comment that says the opposite; someone suggested a pagepool of 8 if you run lots of memory heavy stuff...I use GPS software that tends to take up a lot of ram, and I am just never sure which pagepool number to use for myself
Click to expand...
Click to collapse
I personally liked using 4MB PP when i was running GPS as GPS for sure needs a lot of RAM to keep it running. It also kelped me keep up with txt and stuff, as there was a bit more RAM available.
yeah, i found that on lots of roms, while running gps if i open a text message, it would shut down the gps and i'd have to launch it again, or IE, etc...that is most annoying
Dillsnik said:
yeah, i found that on lots of roms, while running gps if i open a text message, it would shut down the gps and i'd have to launch it again, or IE, etc...that is most annoying
Click to expand...
Click to collapse
for sure IE will shut it down, as IE needs more RAM. But txt should not cause you any trouble. I gave up on GPS due to those RAM issues, so i went and bought a Magellan 1200
I have been using K's rom with a 6mb pp. And during work I leave excel and outlook open all the time, and will run gps and IE here and there, along with some other random programs, including adobe with some large pdf's, with no problems.
I have also been using sk tools, it comes with a "free ram" program that seems to help when memory starts getting low. But, if you have too many things open, it will sometimes shut one of them down (normally IE). But, I really don't have many issues. I also reboot the phone about once a day (In the morning).
iGO8 - Page Pool 4mb
- file system cache AUTO
- glyph 16kb
should be ok
TOMTOM 7 doesnt need so much memory but should be same as iGO
Guys,
Browsing the web I stumbled up on to this article:
It describes how you are able to get a good performance out of your Hero, Hence that it's just a experiment so not sure if it will work!
http://www.majicware.com/HTC-Hero-Speed-Issues-Experimenting?vzWMwp
I'm going to post updates as I will test it.
The article actually sounds quite interesting...I've also noticed that killing tasks doesnt necessarily get rid of some of the lag (although I dont have that much lag to begin with).
I think I'll give this a try for a couple of days too.
Well lets keep us posted on this case. I will give a update tomorrow.
I'll see if that works for me =)
sounds promising =D
thanks for sharing
ill give it a try!
If the phone is syncing then it is definitely very laggy. This is also the case when the memory us low. Obviously if u have apps like task panel or the,music player running at the same time things will slow down too.
For me task panel has worked well. If I keep the free memory at around 50megs then there is almost no lag. I'll keep an eye out for other things as well
If the phone is syncing then it is definitely very laggy. This is also the case when the memory us low. Obviously if u have apps like task panel or the,music player running at the same time things will slow down too.
For me task panel has worked well. If I keep the free memory at around 50megs then there is almost no lag. I'll keep an eye out for other things as well
I have been using the Hero for a few days. On day one I hated it, it was so slow. Then I started using Taskiller to kill tasks like weather, clock, mail, peep etc that are running in the background. Not much help. In fact, it seemed the more frequent that I killed these tasks, the slower my Hero ran.
After a few days of use, I realized the trick to speed up the Hero (or android in general) is DO NOT kill tasks unless you are running our of memory. By running out of memory, I mean really out of memory. My Hero is using 160MB memory right now, which may seems a lot, but it is running very smoothly. Killing some tasks reducing memory usage to, say 90MB, wont' really speed it up. Unlike Windows Mobile, as long as your memory usage is not 99% and have memory left for additional apps to open, just leave it. Remember the Hero has 288MB memory, 100 MB is already reserved for the OS to run, and android memory management will kill unnecessary tasks for you when you run out of memory anyway.
Now, the important part. Do not kill tasks manually too frequently. You have to understand when does the Hero slow down: when it is fetching data. If you use an HTC widget, do NOT kill the relevant app that the widget requires it run in the background. For example, if you used the HTC music widget, don't kill the music app running in the background. If you killed it, you would notice a very significant lag when you go from another page to the page with the music widget. This is because the music widget is trying to open the music app and access the music on your micro SD. Once it is done, the music app will just become idle until you start playing music and there is no more lag. But if you killed it, the widget had to open the app every time you reach that page after killing the app. This causes lag.
The same go for the twitter widget. If you killed Peep running in the background, you will notice a lag when you go the page with the twitter widget. This is because the twitter widget is starting up Peep again and has to connect to your twitter account to check for new stuff. But if you leave Peep running, it will do so only at the regular time interval that you set.
I am now running the HTC clock widget, music widget, bookmark widget, twitter widget and full of stuff on all of my 7 pages home screen. I have clock, weather, music, peep, mail and many other apps running in the background. My Hero run very smoothly.
I hope this helps.
Hmmm... Well, I think it is pretty obvious and common sense that the apps used for active widgets should surely not be killed. For the others, I find that I am better off killing them. Even if this should not be the case, and the effect only "psychological", I still fail to see what would be a benefit of not killing the applications.
Android market should define some criteria that applications must meet before they're made available. Applications should also be benchmarked and rated wrt connectivity requirements, CPU-load etc. This would be a deterrent against applications that load automatically even when there's no config (like peep when there's no twitter account), or puts such load on device that it runs out of juice in a few hours (power manager). If this is done on android market one could also hope that vendors also would put a bit more effort into optimising their own stuff.
've stopped obsessively killing Apps...running smoothly. Android Dev video posted on similar thread reassured me that the OS is meant to take care of all that anyhow
phel21 said:
Android market should define some criteria that applications must meet before they're made available. Applications should also be benchmarked and rated wrt connectivity requirements, CPU-load etc. This would be a deterrent against applications that load automatically even when there's no config (like peep when there's no twitter account), or puts such load on device that it runs out of juice in a few hours (power manager). If this is done on android market one could also hope that vendors also would put a bit more effort into optimising their own stuff.
Click to expand...
Click to collapse
Well, I dunno; that way madness lies, or at least iTunes Appstore madness, where new apps, and upgrades, take weeks to get approved, and are still equally buggy. And new apps often get refused, for no good reason.
I like the timeliness of the Android store; and I'm suffering with dodgy apps too - my Hero currently won't last overnight on standby - but it's still miles better than the iPhone nonsense
Well I stopped using the task manager to kill apps for a couple of days....but there is no real speedup and its just the same.
BUT it also means that its pointless to kill the tasks to begin with since it didn't make a difference either (like other people are now saying). If anything, the browser and apps like people/contacts load up faster beacause they are still somewhere in the background (I used to always constantly kill these apps).
The part about not suspending the phone straight away has made a slight difference. Before, when I turned the screen on I constantly had a lag especially sliding the screen left and right and going to the messages page. But if I let it go into standby by itself, when I wake up the phone, it barely stutters (and if it does, its only for like a split second on the first slide).
...if only there was a shortcut to just lock the screen....
I found uninstalling 'Power Manager' sped my phone up massively. I shall try this and see if he's onto anything.
...if only there was a shortcut to just lock the screen....
Click to expand...
Click to collapse
Aren't there apps for locking in the market?
don't know will this speed up things and to whom it may apply, but until today i never ran my Stocks app, seeing as i don't care about stocks so i opened it, opened settings and found out it was set to update every 1h with 4 preset stock somethings....so those not using it might also wanna check that the thing is switched to Manually, one less task that shows up for no reason :/
Tone-Fu said:
I found uninstalling 'Power Manager' sped my phone up massively. I shall try this and see if he's onto anything.
Aren't there apps for locking in the market?
Click to expand...
Click to collapse
I've only come across the likes of lock 2.0 but I thought that was an alternative lockscreen...
cdmackay said:
Well, I dunno; that way madness lies, or at least iTunes Appstore madness, where new apps, and upgrades, take weeks to get approved, and are still equally buggy. And new apps often get refused, for no good reason.
Click to expand...
Click to collapse
Apple's problem is politics. I wasn't hinting towards any such subjective valuation for Android. What I'd like is a clear set of technical requirements (example: an application that auto-starts during boot even without necessary configuration data should not be accepted), and a site back-end with numerous emulators that runs applications through their paces to obtain performance/power/network rating before they are made available for download. Extensive testing would require manual configuration, test and monitoring, but even some simple automated tests could sort out the worst offenders. Ratings should be displayed with application descriptions on the site, and would also work as a simple form of tech feedback to developers about things they may need to improve.
good points.
I've since discovered that any app that registers to receive async alarms will be started at boot, even though it doesn't necessarily need to be. not really a problem, but the cause of a lot of processes running at boot for no obvious reason.
Hi Guys,
I'm Adam Saunders, author of the original article.
Just a thanks to everyone that is also trying the experiment. So far I've had a lot more positive results from people than negative, so the hunch is somewhere on the right track.
I was going to try and find an exact reason as to why killing tasks repeatingly will slow the device down. It's been said its the way that Android kills apps but saves the state, so the process isn't actually running, and by killing that off, the orphaned state is possibly the problem. Sounds feasibly, but not read anything official to back up that claim.
Confirmed, it's been three days since I stopped killing the processes and any lagging (which was very slight for me in the first place) is gone. Thanks for the tip, Adam!
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.
I've had immense lag when I am typing into quick-reply boxes..even normal reply boxes while surfing. It's REALLY bad on default browser, worse on Dolphin Mini.
Any idea what's causing this?
On Amethyst 1.1 atm....Been having this problem from LeeDroid, CM7, Oxygen, AuraxT..
Oh and surfing web is not so smooth most of the time 100% CPU Load..
I know what you mean because I previously struggled with it. I don't know a sure fix, but in my case it was always either due to;
- The SD card being accessed heavily
- The system memory going down to below 70MB
- LauncherPro associated weirdness. Uninstalled it at such periods and the huge lag was gone.
------------------------------
- Sent via HTC Desire -