For stability purposes, it is best to open an application and then leave it running, or close it?
Closing it removes it from memory, yes, but if an application is a little leaky with memory, this is a bad thing, right?
On my E71-1, it takes a lot of open applications before I notice it slowing down a little, but the real memory hog is the web browser...
All running apps use their part from the operating memory RAM , also called D: drive . When RAM is full , the device slows , stops operating , freezes , reboots or in many situations closes app(s) automatically to make room for a new operation . The latter is what the iPhone basically does : closes running app when another app is opened .
Symbian keeps several apps open : this is named Multitaking .
Running app needs battery-feed . It is really up to the user , what he needs . When the phone is left workless , of course batterytime will be best when all apps and features ( BT , Wifi !) are closed .
Grap some tips from this thread : http://www.allaboutsymbian.com/forum//forum/thread/84082/
😊 Regards jApi NL
Heya - thanks for the tips. The E71 has lots of memory and will happily have ten to thirteen application in memory at once without noticeable lag. The operating system is also far kinder to the user when running low on memory compared with say a Windows Mobile device.
The issue of applications in the background using more battery power is thorny, because if an application is sitting there not doing anything, it won't increase power consumption by a measurable amount.
Sure, if my calendar is running, it might use more processor cycles than if not running, but in the context of me downloading and listening to a podcast over HSDPA it won't make much of a difference!
Are there any applications that are known to be leaky with memory?
Web or Opera Mini ~ 20 MB .
Gallery ~ 15MB
GPS ~ ??
Etc.
😊 Regards jApi NL
The browser will soak up around 40 Mb if I let it, but when I close it, it gives this memory back...