While I agree that consuming a bunch of memory has an impact -- it
means apps have to be killed and restarted more often, for example --
there's no connection to GC.
GC is something that happens entirely within your own process, and is
not affected by memory usage by other processes. Allocating a
The battery power frob is great! But I think it may already be good
enough to serve for this purpose. The apps that are consuming the most
battery power, and the apps that are consuming the most CPU, are
typically the same set.
I'm not arguing against your suggestion -- even if they were always
Example: suchandsuchappcrond_service.. CROND service? This is what
the alarm manager is for, doing a repeated task every so often. If you
are consuming memory being in the background all the time, when you
could simply invoke the alarm_manager to wake you every so often, that
is much better
Yep the problem is largely associated with services and not just random
processes running. That is why the running services UI was introduced.
Trouble with that is, it doesn't show the *running* services but the
*started* services.
Esp. services written for 1.x might just linger around to do
On 4 kvě, 01:06, Eric F ericfrie...@gmail.com wrote:
The solution here is a change in attitude. I don't use a task killer
on my phone, never have. And my phone sports good performance for
weeks on end.
Agree. I have task killer but use it really rarely.
Obviously the solution isn't to
Dianne, thanks for answers.
In fact one of the problems with the API that the task killers have been
abusing is that it was there for the force stop button in the UI. This is
not for killing processes. This is for making everything about the app
stop: not just its processes and services,
On May 3, 11:59 pm, mort m...@sto-helit.de wrote:
And what's wrong with resource consuming? I coud cache several MB of
data in a non-running service, it wouldn't matter. Android would just
kick it if the memory's required, and the service would just reload
the data when it's restarted.
It's
I think that cure can be the same approach as when battery is out of
power. There is button Why? and it shows major consumers of the power.
I think that Google could include in Android also some tool that shows
major CPU Memory eaters. Users after this info will decide whether
they want such a
Too extreme :-)
On Apr 30, 1:56 am, Tomáš Hubálek tom.huba...@gmail.com wrote:
Hello,
I'm on developer of Digital World Clock Widget
(http://www.appbrain.com/app/net.hubalek.android.worldclock).
I'm receiving a few emails per week with complain that my widget
stopped working. In all
Way too extreme, without the Task Killers battery life on most phones
would be horrible and the speed even on some phones such as the Droid
would slow down too much waiting for background tasks to die on their
own.
Although I understand your frustration there has to be a better
resolution for now
On Mon, May 3, 2010 at 1:59 PM, gcstang gcst...@gmail.com wrote:
Way too extreme, without the Task Killers battery life on most phones
would be horrible and the speed even on some phones such as the Droid
would slow down too much waiting for background tasks to die on their
own.
Not to
Task killers are the only way I can get a mostly lag-free experience
playing games. It's surprising how loaded up with services a phone
gets when you install even a moderate amount of useful tools. You can
see an obvious difference even on a nexus one when you cut out some of
the tasks you don't
As far as I know most task killer apps will kill processes only if you
tap on the process itself, so your users are probably killing the
process of your widget to then wonder why it has stopped working...
--
You received this message because you are subscribed to the Google
Groups Android
The solution here is a change in attitude. I don't use a task killer
on my phone, never have. And my phone sports good performance for
weeks on end.
I do, however, frequently visit manage applications - running
services. And I also uninstall apps that run services that probably
shouldn't be.
Yep the problem is largely associated with services and not just random
processes running. That is why the running services UI was introduced. Not
only does it let you see exactly what is doing this (and deal with it), but
it is also the first step in making developers more accountable for (and
15 matches
Mail list logo
