Database Develop

Taskiller ignore list:

After switching from Magic to Hero (which is a great improvement!) I've noticed that there are a couple of new recurring processes on the Taskiller list, which I have never seen before on the Magic; eg: com.htc.provider.weather, HTC locatiediens (=localisation service, in Dutch), com.htc.socialnetwork.provider, HTC media uploader; beside TouchInput and Touchflow, which I've already put on my ignore list.
I assume these are specific Sense processes, partly vital for the UI; is there anybody who could give a list of the vital processes, we should put on the ignore list and/ or a list of processes which are safe to kill if system slows down?
I've already contacted the dev of Taskiller; but he says he has no Hero experience, so cannot advice on this issue..
Any advice is welcome, thanks in advance!
Balazs

I have the same question...
It would be great if we know whixh process correspond to what

I fiddled around with this and it's safe to kill everything. The vital processes will just start right up again. socialnetwork.provider and provider.weather are, I'm assuming, to do with Facebook/Google integration and weather widget/applications respectively. If you're going to be killing processes regularly, I'd suggest you put touchflo and touch input in the ignore list, as they need to be running constantly for the UI to work. You can kill them, but the phone will hang for a few seconds while they restart.

[Q] Possible to keep background apps in low mem situations?

Is there any way to keep certain background applications running if memory runs low and the android garbage collector goes around killing processes that are running in the background?
I have the problem that under low memory situations android kills all my background apps and especially services. This is ok for most use-cases, but is really annoying especially for my Jabber client and sometimes even the music app.
I looked through the API doc and found that you can set Service::setForeground(true) to prevent the service from being killed. This is nice for open source apps, but I can't prevent closed source apps from being killed that way. And I'm not even sure if it helps in all cases, as the music app should be using it and gets killed too.
Does anyone know how I could exclude certain apps from being killed in the BG? Which process is responsible for doing that? Wouldn't it be possible to patch that process or part of the kernel to exclude certain processes?
I know there are workarounds for keeping the launcher in memory by restarting it all the time. That wouldn't help in my situation where the Jabber service has a permanent network connection going.
Anyone got technical information for me on this?

You created a new thread with [Q] so why don't you create it in Q&A forum. Thread move.

[Q] All apps seem to load on startup

Hi,
It appears that any time I reboot the phone, it starts with all applications loaded.
Unless I go to Advanced Task Killer and kill all, my phone is very slow. Also free memory jumps from about 90M to 150M after the kill.
Does anyone know ho to stop that from happening? Is there some kind of startup list that can be edited?
I am using rooted UCJH7 but no other tweaks and fixes.
Thanks

You could have just searched the market for 'startup'.

There are quite a few startup editor apps in the market, I haven't tried any, but most of the reviews seem pretty hit or miss. Just search "startup" in the market.

Well android handles memory management really well. Those apps load up and take a very small amount of memory and when you open the app it will increase the memory usage and when you close it it will run in the background again and take up very little memory. The fact the apps are open in the background shouldn't slow down your phone. The fact you have 90mb free is good. This isn't windows mobile where the more free memory you have the faster your phone is. There are apps u can use to see if your apps are running in the background or foreground when your not using them. If they are running in the foreground and taking up alot of memory then there's a problem. Hope i explained the memory management well enough.
And btw for future reference, read the stickies. You posted this in development. Should be posted in Q and A

jasonyump said:
Well android handles memory management really well. Those apps load up and take a very small amount of memory
Click to expand...
Click to collapse
The fact remains, free memory almost doubles after I kill them.
>The fact the apps are open in the background shouldn't slow down your phone.
The fact is that they do slow down the phone a lot.
The problem is that it seems that all applications get fired indiscriminately. And the question is if someone with some knowledge of Android internals can shed some light on that.
I will post specific numbers on memory after I reboot it next time.

alexnoalex said:
Hi,
It appears that any time I reboot the phone, it starts with all applications loaded.
Unless I go to Advanced Task Killer and kill all, my phone is very slow. Also free memory jumps from about 90M to 150M after the kill.
Does anyone know ho to stop that from happening? Is there some kind of startup list that can be edited?
I am using rooted UCJH7 but no other tweaks and fixes.
Thanks
Click to expand...
Click to collapse
i too thought so initially. but when i started observing, i observed that the apps that load up at start up are generally the apps that i frequently used.

questions on N

I'm on N... Things...
1) is the downgrade resolution feature still here? I can't find it
2) does the "close apps when power button is pressed" do anything different than a regular task killer? Is this useful?
3) how do you control whether or not a notification peeks?
4) i seem to be having data sync only every few minutes for background apps (whatsapp, hangouts). im not in any sort of power saving mode and ive made sure those apps dont close behind the scenes. ideas?

Anyone? These notifications are driving me nuts.

Hello, sorry you didn't get any replys on here, last time i was in here i made a post and nobody replied to me, so i deleted my account and ended up coming back because i too wanna update to Android N which you already have. The firmware is still Beta stage so it's normal that you see lota of bugs and such.

Background Apps closing when navigating away

Is there a way to stop background apps from closing when navigating away from them?
If flicking between a few apps they are going back to the starting screen so are being closed when navigating away. I have searched Google and it looks like a bug Nokia are aware of but is there a workaround to stop this behaviour?
I tried switching on Background activity cleaner and setting just one app to be blacklisted as per a thread I found but this does not work and still all background apps are being closed
With 6GB of RAM you would have thought there could be plenty of apps left to run in the background without too much performance issues