Database Info

[REQUEST] Dialer app or Contacts app in memory

Hi,
Mods, feel free to move this to the Q&A if you think this is inappropriate. Thanks.
I would like to request whether a similar function like the "Home app in memory" for "Spare Parts" can be extended to critical functions like the Dialer and Contacts app? I find it irritating having the phone to constantly restart the application when coming off the browser or some other applications. It takes a good 2 seconds to load it completely. I have tried clearing the logs etc. but I think having it in memory would really speed up its use.
Can such a thing be done? Or has it been done? Please comment, thank you

solution
This is more of a request than a question...probably would go to the apps forum,
but anyway,
My solution is to download the AutoKiller app, and set it to whatever setting you like...go to settings, and find the running processes, long click on Dialer and select "Keep Alive"
Works for me. Always seems to stay in memory whenever I check running services. If you have any other task managers or app killers, be sure to "ignore" Dialer for those as well, so they don't close it either. Hope that helps. This is a great idea though, I've been introduced it along time ago, with no response, maybe you'll achieve otherwise. Good luck.

Klyentel said:
This is more of a request than a question...probably would go to the apps forum,
but anyway,
My solution is to download the AutoKiller app, and set it to whatever setting you like...go to settings, and find the running processes, long click on Dialer and select "Keep Alive"
Works for me. Always seems to stay in memory whenever I check running services. If you have any other task managers or app killers, be sure to "ignore" Dialer for those as well, so they don't close it either. Hope that helps. This is a great idea though, I've been introduced it along time ago, with no response, maybe you'll achieve otherwise. Good luck.
Click to expand...
Click to collapse
Thanks for the alternative solution However, I am hoping that it would automatically boot it into memory when the phone starts, instead of having to run it once before it gets shifted into the memory. Hope I am making sense... but I'll certainly try your solution.

erlern said:
Thanks for the alternative solution However, I am hoping that it would automatically boot it into memory when the phone starts, instead of having to run it once before it gets shifted into the memory. Hope I am making sense... but I'll certainly try your solution.
Click to expand...
Click to collapse
Im not sure...good point though, let me know how that works for ya

Klyentel said:
Im not sure...good point though, let me know how that works for ya
Click to expand...
Click to collapse
Yeah, I tested your method and it works perfectly, just 1 second or less to switch. But as expected, I need to run it through Autokiller again when I reboot the system. I really hope that it can be autostarted and remained in the memory from the start. But that's a lot... this will have to do while we wait for a kind developer who may take pity on us on this matter

So they're loading slowly on your phone i'm guessing?

another app...
There is another app in the market called autostarts that you can set to start the dialer on startup, a long way of accomplishing what you want, but my work for you.

OP, it seems AutoKiller app will do this for you. Check this post in the How to configure Android's *internal* taskkiller thread.

Thanks for the advices guys. I have tried all of it, and as I am looking at the documentation for 'taskkiller' I seriously am sadden that it is more technical and complicated than "Spare Parts" simple feature of ticking a box
My phone at times loads things slower than usual, especially the dialer app when I have more than 10 call log contacts, etc. I guess it is a HTC Dream problem with its now ancient 528Mhz processor. *shrug*
If a developer can help out on this, it would be great

wait for my HTC cupcake Rom...
dialer is part of the phone and stays in memory.
takes around 1 second to load...

domenukk said:
wait for my HTC cupcake Rom...
dialer is part of the phone and stays in memory.
takes around 1 second to load...
Click to expand...
Click to collapse
Thanks, will definitely wait for it I wonder whether this can be integrated into CyanogenMod?

erlern said:
I seriously am sadden that it is more technical and complicated than "Spare Parts" simple feature of ticking a box
Click to expand...
Click to collapse
It is not complicated at all.
1) Install AutoKiller
2) Start AutoKiller
3) Allow it root access permanently if it asks, relaunch AutoKiller
4) Click on Processes tab
5) Long press on Dialer
6) Choose "Keep Alive"

Super Jamie said:
It is not complicated at all.
1) Install AutoKiller
2) Start AutoKiller
3) Allow it root access permanently if it asks, relaunch AutoKiller
4) Click on Processes tab
5) Long press on Dialer
6) Choose "Keep Alive"
Click to expand...
Click to collapse
I understand the process. When I say it is complicated, I am referring to the need to redo every 5 steps whenever my phone is restarted. I restart my phone daily, and would find that having to relaunch Autokiller, and click this and that is more complicated than just clicking a box 'once' and not needing to worry about that anymore. In fact, this is the problem stated in the thread given under "durability". Thanks again.

Huhu... I've asked the same question too (less clearly than you do, but got the same answer) here and elsewhere...
I'm looking for exactly the same than you.

meuhlavache said:
Huhu... I've asked the same question too (less clearly than you do, but got the same answer) here and elsewhere...
I'm looking for exactly the same than you.
Click to expand...
Click to collapse
I still hope there will be a kind developer who will help with this request. If the solution can be incorporated into a ROM like cyanogen's ROM, even better. Thank you anyone who may be interested.

www.bit.ly/b26PcJ <<this rom has the dialer locked into memory.
Big release will be as soon as I have the time for it.
please report if you like it and if everything works
have fun with it

I agree that this feature is a good idea and should be more standard. Making calls is the primary function of our devices and as such, I should be able to do it instantaneously. On my last non-smart phone, I was able to push talk and get the dialer in like, 1 micro-second. On my G1, I've gotten more used to waiting anywhere from 2 to 5 seconds.

+1
I would love this feature to be implemented in the future.

I too have been looking for a way to set the oom of a few processes to -17 so they'll never close. I've used autokiller, but i too hate that everything has to be set after every boot. I've set the minfree values through custom_init on my hacked up version of StupidFast 1.2, and I'd love to be able to set the oom values there too.

Well I am currently looking in the android source for a way to set it...
playing around with adb shell a little. will report soon
as long as I am doing this, you can still use the rom from above... HTC dialer is just sooo much better when it comes to speed, memory consumption and usability...
best thing would be to get this ported to donut...
/edit: first steps:
/proc/<pid>/oom-score shows process' current badness score.
Click to expand...
Click to collapse
/proc/<pid>/oom-adj
Click to expand...
Click to collapse
ther you could set the oom score....
get the pid with 'pidof [app name]'
you can include the pidof in the whole thing.
so it should be something like
echo -17 > /proc/'pidof [whatever app]'/oom-adj
Click to expand...
Click to collapse
But I am not shure... still trying
but be aware that there is already waay to little memory avaliable on our phones...
possible for badness (this value) is anything from -17 to +15...
-17 will never be killed, no matter what.
/edit: there is also something like:
oomkilladj = OOM-DISABLE
Click to expand...
Click to collapse
...
stupid :/
/edit: android contacts is com.android.contacts.
/edit: sorry, I have no more time. Anybody else try it please...
seems not to work for me like i have posted it...

[HTC DESIRE HD] Android - Exiting applications

Okay so, i got my first android device htc desire hd and it's amazing.
Coming from wm6.5, i noticed there was no way to actually exit some apps...they're still running. i was going to download a task killer but did some reading and turns out it's bad.
There's a options in settings to see running processes and can kill them
But i don't know if that's safe to do...
How exactly do you exit apps in android? or is there no need to exit them? android will close them automatically to manage memory or something?
I would be grateful if someone can explain
Thank you

Gurps777 said:
Okay so, i got my first android device htc desire hd and it's amazing.
Coming from wm6.5, i noticed there was no way to actually exit some apps...they're still running. i was going to download a task killer but did some reading and turns out it's bad.
There's a options in settings to see running processes and can kill them
But i don't know if that's safe to do...
How exactly do you exit apps in android? or is there no need to exit them? android will close them automatically to manage memory or something?
I would be grateful if someone can explain
Thank you
Click to expand...
Click to collapse
new to Android here some posts to read.

Hi, Android 2.2 is build with an "internal taskiller", that will do most of the job itself, but if some apps just doesn't wan't to close themselves: Then just use a taskiller, nothing will turn out wrong. I have been using it for 2 years on my HTC, without any problems at all. But haven't used it on my samsung, cause it has got android 2.2

Gurps777 said:
How exactly do you exit apps in android? or is there no need to exit them? android will close them automatically to manage memory or something?
Click to expand...
Click to collapse
You hit the nail on the head there!
Android has no need to fully exit applications. When you close them they remain idle so switching back to them is much quicker. If Android needs to free up some space for more memory intensive apps, it will close the least important services that are running (some services will not be closed, Home app, etc.).
That's it in a nutshell. It's probably a lot more complicated than that though

Meltus said:
You hit the nail on the head there!
Android has no need to fully exit applications. When you close them they remain idle so switching back to them is much quicker. If Android needs to free up some space for more memory intensive apps, it will close the least important services that are running (some services will not be closed, Home app, etc.).
That's it in a nutshell. It's probably a lot more complicated than that though
Click to expand...
Click to collapse
Yeah i read up on it in that article explaining why not to use task killers, Thanks for that short and wonderful explanation.

[Q] how do you close apps?

so i found out how to force close apps under settings but theres gotta be a better way.
for example lets say i have browser, market, and facebook apps open. all showing under the window selection button. after time i get a ton of windows there and i don't want all of them open. how do i close them selectively without going through all the settings menu crud?
some apps let me close from within, most don't though and leave me stuck with a ton of windows (apps) open.

What you are asking isn't necessary unless an application has malfunctioned. There is no other way to close applications other than using the force close button in settings. Android handles this itself -- if this doesn't satisfy you download a task manager.

I don't think there is a way yet.
What Google needs to do is make those preview windows in the multitasking bar long-pressable for a menu to be able to close them.

modru2004 said:
so i found out how to force close apps under settings but theres gotta be a better way.
for example lets say i have browser, market, and facebook apps open. all showing under the window selection button. after time i get a ton of windows there and i don't want all of them open. how do i close them selectively without going through all the settings menu crud?
some apps let me close from within, most don't though and leave me stuck with a ton of windows (apps) open.
Click to expand...
Click to collapse
There is no need to manually close out apps. Since 2.1, Android has done an excellent job managing memory. It's been written many times (some directly from Google) that micromanaging your apps will actually hurt battery performance. You'll essentially be working against the system as opposed to helping it.

I am not sure if my task manager is working on this device. I use AutoKiller and when I killed task it doesn't appear as though anything closes. Can somebody confirm?

atoy74 said:
There is no need to manually close out apps. Since 2.1, Android has done an excellent job managing memory. It's been written many times (some directly from Google) that micromanaging your apps will actually hurt battery performance. You'll essentially be working against the system as opposed to helping it.
Click to expand...
Click to collapse
id like to point out thats NOT the issue.
the issue is the ton of windows you end up having to sort through unless you close them. its a quality of life thing, i don't like having unused unnecessary windows open that i have to sort through to get to the stuff i am using. its just bad form.

foldog22 said:
I am not sure if my task manager is working on this device. I use AutoKiller and when I killed task it doesn't appear as though anything closes. Can somebody confirm?
Click to expand...
Click to collapse
It will most likely not work until its rewritten. The way 2.2 and now 3.0 allow access is completely different then 2.1 and below. Plus as said about 200 million task there is 0 reason to run a task killer. If you wanna clear them out, even though there is 0 reason, reboot.

Okay, I get the memory management issue, but as the OP pointed out, I've got all sorts of icons in the "task bar area" (bottom right hand corner) that just sit there or keep coming back.
For example, I haven't listened to any music on my Xoom since yesterday morning, yet I've got an icon down there for Music and Rhapsody. Also, there's no way to clear some notifications.
There's got to be a way to at least clear out the notification isn't there?

you tap on the little icon music for example and you will see a little x on the right of it, click that and it closes it from the notification system

There is absolutely no reason to use a task killer or manually kill tasks. 2.2, 2.3, 3.0, etc. handle memory and tasks extremely well. In many cases, task killers will only cost you more battery and more slowdowns than letting tasks just run out and sit in memory. Unless you're seeing rogue or malfunctioning tasks in the background causing slowdowns, there is no need to kill them.
I do wish you could scroll through the recent running apps rather than only being able to access the latest 5, but spam closing background apps doesnt help at all.

arrtoodeetoo said:
I don't think there is a way yet.
What Google needs to do is make those preview windows in the multitasking bar long-pressable for a menu to be able to close them.
Click to expand...
Click to collapse
While I haven't used a task manager since I started learning how android actually works last year when starting to make apps, I can't help but want the same thing in honeycomb for malfunctioning apps. I think google left it out intentionally to discourage task-killing rampages by oblivious users.

Every time I read "you do not need to close apps" I want to scream. first hour of usage I had a second browser installed and it and the stock browser were conflicting with each other... all I wanted to do was a quick close of one of the browsers.
There are always a multitude of good reasons to want to close a background app. I completely understand the technical reasons why an app does not need to be closed, but from a user experience point of view, it should be made simple.

mjpacheco said:
Every time I read "you do not need to close apps" I want to scream. first hour of usage I had a second browser installed and it and the stock browser were conflicting with each other... all I wanted to do was a quick close of one of the browsers.
There are always a multitude of good reasons to want to close a background app. I completely understand the technical reasons why an app does not need to be closed, but from a user experience point of view, it should be made simple.
Click to expand...
Click to collapse
Which is exactly why in my first post I said "...isn't necessary unless an application has malfunctioned" otherwise such a thing is barely necessary. And in your case, the classic "Settings > ....... > Force Close" would have easily sufficed.

So what you are saying is that a method to kill tasks is necessary, just not often. I, for instance, just had the xda app stuck on the splash screen. I killed it and restarted the app and all was good. There is a potential for harm if used over zealously but at times it would be nice if there was a more convenient way to close an app when necessary.
Applications do not always behave as they should so to say there is no need to kill am app is making a naive assumption that every android app is perfect.
Sent from my Xoom using XDA App

martonikaj said:
I do wish you could scroll through the recent running apps rather than only being able to access the latest 5, but spam closing background apps doesnt help at all.
Click to expand...
Click to collapse
Oddly enough, if you turn to portrait, you get a few more. So, technically its not a hard limit on 5, but rather (literally) limited by space on the screen.
Anyone want to place a bet as to what rev we see scrollability?
Sent from my Evo using the XDA App

JanetPanic said:
So what you are saying is that a method to kill tasks is necessary, just not often. I, for instance, just had the xda app stuck on the splash screen. I killed it and restarted the app and all was good. There is a potential for harm if used over zealously but at times it would be nice if there was a more convenient way to close an app when necessary.
Applications do not always behave as they should so to say there is no need to kill am app is making a naive assumption that every android app is perfect.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
If this happens use the built in task killer, settings/applications/running tab.
Sent from my PC36100 using Tapatalk

bwcorvus said:
If this happens use the built in task killer, settings/applications/running tab.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I did and it worked. As I said it would be nice to have a more convenient way of force stopping apps that are not behaving.
Sent from my Xoom using XDA App

Closing apps isn't necessary for two reasons.
1. Android does a good job at managing apps on its own.
2. You have 1GB of RAM to work with.
Sent from my HTC Vision using Tapatalk

Watchdog does a considerable job since it only lets you know when an app is misbehaving. And since being on 2.3 its barely given me any alerts. Perhaps further proving the awesome memory management.
Sent from my Xperia X10 using XDA App

delete please

Available memory and tasks

This is my 4th Android phone, and I am still a little unclear on how memory works on this machine. I use AutoKiller, yet I am still confused. As I understand it, 100mb or 5mb free, it shouldn't affect the operation of the device until something needs more than the available and has to clear room. So, how does this work, exactly? I am continually running low on the Triumph, yet if I set the preset in AutoKiller higher, I begin to lose services ranging from alarm clocks to social networking notifications. Where do I begin to find balance? Am I missing something?

I haven't had a problem with starting to lose services like the alarm clock but I was seeing the system significantly slow down even as I kept all unnecessary tasks from running. So I figured that I would root my system, and get rid of all the pre-installed software that I didn't use. The funny thing is that after I rooted the system all the memory issues went away, and the system really flies now. I don't know what changed, when I rooted it. But I am not seeing the same slow responses, the constant starting of tasks that I don't use and so forth. I know that its not an answer so to say, but I thought that I would share so as to maybe help you, or see if it happened with someone else.

HitchHiker said:
I haven't had a problem with starting to lose services like the alarm clock but I was seeing the system significantly slow down even as I kept all unnecessary tasks from running. So I figured that I would root my system, and get rid of all the pre-installed software that I didn't use. The funny thing is that after I rooted the system all the memory issues went away, and the system really flies now. I don't know what changed, when I rooted it. But I am not seeing the same slow responses, the constant starting of tasks that I don't use and so forth. I know that its not an answer so to say, but I thought that I would share so as to maybe help you, or see if it happened with someone else.
Click to expand...
Click to collapse
Thanks for the reply. It's nice to hear other experiences. I am already rooted, and AutoKiller requires root. I'm just being patient and hoping that a custom ROM can solve problems.

Rooting shouldn't change anything except whether or not the phone is rooted. That's it. Task killers rarely help because those apps you kill just come back as soon as you look away. So I would personally recommend you only kill the miscreant apps, and ultimately remove them if you can.
Sent from my Frankenphone using Tapatalk

primetechv2 said:
Rooting shouldn't change anything except whether or not the phone is rooted. That's it. Task killers rarely help because those apps you kill just come back as soon as you look away. So I would personally recommend you only kill the miscreant apps, and ultimately remove them if you can.
Sent from my Frankenphone using Tapatalk
Click to expand...
Click to collapse
Autokiller doesn't work that way. It merely changes Android's already existing internal programming to be a touch more aggressive. It does nothing on its own, merely giving you an interface to alter Android's own values for task management and app priority.
What I really need to know is if that aggression is necessary. Android's default minimum for memory is 24mb (that is the level at which the system will kill off empty apps). I can raise that number, but is it necessary? Some one told me that free memory amount is irrelevant in Android. If that's true, what is the point in making sure my system has 100mb free as opposed to 20mb?

I wouldn't think that extra memory management app is necessary, the only problems any android 2.2 phone (or any android) has are apps that are coded porely are installed. Just use a app that shows cpu usage. If a app is porely written you will see it..... those are the ones to uninstall.....not kill, uninstall.

tsac said:
I wouldn't think that extra memory management app is necessary, the only problems any android 2.2 phone (or any android) has are apps that are coded porely are installed. Just use a app that shows cpu usage. If a app is porely written you will see it..... those are the ones to uninstall.....not kill, uninstall.
Click to expand...
Click to collapse
Like I said, the app merely gives me a UI to alter Android's already existing internal programming in regards to service priority. I am just trying to better understand how Android does it's work.

[Q] Could someone please explain the JB multitasking?

Can anyone explain to me why the JellyBean multitasking is so damn weird? Whenever im using my phone and i open the task manager, i ALWAYS see a random app open which i never opened after rebooting. For example, rebooted my phone this morning and the only apps i opened were the phone app, messaging, mail. However, the task manager lists the following apps as open: "Android core apps, Tasks, Picasa Uploader, Social Manager, Notes".
So my questions is, Why are all these random apps open and eating up battery and memory? I guess android core apps must be system required to run in background at all times but what about the other ones? Is there a way to fix this?
I have used ICS and GB on htc inpire and sensation and both software versions would not show these "random" apps open, it would only show what ive opened and let run in the background.
Thanks for all the help.

mominn8266 said:
Can anyone explain to me why the JellyBean multitasking is so damn weird? Whenever im using my phone and i open the task manager, i ALWAYS see a random app open which i never opened after rebooting. For example, rebooted my phone this morning and the only apps i opened were the phone app, messaging, mail. However, the task manager lists the following apps as open: "Android core apps, Tasks, Picasa Uploader, Social Manager, Notes".
So my questions is, Why are all these random apps open and eating up battery and memory? I guess android core apps must be system required to run in background at all times but what about the other ones? Is there a way to fix this?
I have used ICS and GB on htc inpire and sensation and both software versions would not show these "random" apps open, it would only show what ive opened and let run in the background.
Thanks for all the help.
Click to expand...
Click to collapse
Use an app called greenify in play store to keep apps from opening.
Here's the link to the apps XDA page http://forum.xda-developers.com/showthread.php?t=2155737
Sent from my Elemental Venomized S-off HTC One XL

majortaylor said:
Use an app called greenify in play store to keep apps from opening.
Here's the link to the apps XDA page http://forum.xda-developers.com/showthread.php?t=2155737
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
Thanks ill try that app. This multitasking system really makes me mad. Why would anyone come up with a system like this that wastes battery and performance...

Unfortunately greenify only helps with non system apps. So notes, tasks, weather, social manager and etc will still have a mind of their own and open whenever they want.

mominn8266 said:
Thanks ill try that app. This multitasking system really makes me mad. Why would anyone come up with a system like this that wastes battery and performance...
Click to expand...
Click to collapse
You obviously have no idea how the Android OS works.
Unless you have actual evidence that these apps are hurting your battery and performance, you should really stop worrying about it. I'm pretty sure the people who designed the OS have a pretty good idea of how to optimize its performance.

thebobmannh said:
You obviously have no idea how the Android OS works.
Unless you have actual evidence that these apps are hurting your battery and performance, you should really stop worrying about it. I'm pretty sure the people who designed the OS have a pretty good idea of how to optimize its performance.
Click to expand...
Click to collapse
Maybe you could help me understand how it works then? My only question / concern is why are apps that have never been opened running in the background?

mominn8266 said:
Maybe you could help me understand how it works then? My only question / concern is why are apps that have never been opened running in the background?
Click to expand...
Click to collapse
Sorry, didn't mean to be a douche (or, I did mean to, but shouldn't have been).
If you say you've "never opened" them, why do you even bother having them installed? You've been given a solution to this "problem," (Greenify), but honestly any benefit you see will more than likely be placebo. The OS is generally smart enough to know what to run and what not to run. Apps that are loaded into memory aren't necessarily "running" in the traditional sense, they're just in memory. It doesn't take any extra battery to have something in memory (memory is either powered on or not).

thebobmannh said:
Sorry, didn't mean to be a douche (or, I did mean to, but shouldn't have been).
If you say you've "never opened" them, why do you even bother having them installed? You've been given a solution to this "problem," (Greenify), but honestly any benefit you see will more than likely be placebo. The OS is generally smart enough to know what to run and what not to run. Apps that are loaded into memory aren't necessarily "running" in the traditional sense, they're just in memory. It doesn't take any extra battery to have something in memory (memory is either powered on or not).
Click to expand...
Click to collapse
unless causing wakelocks or syncing/updating when you don't want them too, I tend to just turn my Radios on and off as I need them.

thebobmannh said:
Sorry, didn't mean to be a douche (or, I did mean to, but shouldn't have been).
If you say you've "never opened" them, why do you even bother having them installed? You've been given a solution to this "problem," (Greenify), but honestly any benefit you see will more than likely be placebo. The OS is generally smart enough to know what to run and what not to run. Apps that are loaded into memory aren't necessarily "running" in the traditional sense, they're just in memory. It doesn't take any extra battery to have something in memory (memory is either powered on or not).
Click to expand...
Click to collapse
Dont be sorry, never took it offensively lol
I cant really uninstall system apps such as notes, tasks, social manager (even though i dont even have facebook or twitter installed). Trust me ive disabled all the apps in greenify and uninstalled all the apps i could that i didnt want.
I also have another question, When i open the "recent" app interface, does swiping to the right mean the app is closed or just taken off the list? is there a way to "kill" an app using the recent app menu?

mominn8266 said:
Dont be sorry, never took it offensively lol
I cant really uninstall system apps such as notes, tasks, social manager (even though i dont even have facebook or twitter installed). Trust me ive disabled all the apps in greenify and uninstalled all the apps i could that i didnt want.
I also have another question, When i open the "recent" app interface, does swiping to the right mean the app is closed or just taken off the list? is there a way to "kill" an app using the recent app menu?
Click to expand...
Click to collapse
not sure but there's an easy way to find out.
swipe it away then check in settings, apps, running. If it's still there then no, if it isn't then, yes.
If that doesn't work then no there isn't a way to kill in recent, if it does, then yes there is and you discovered how.