Help I have 2.2... Now what the Hell am I supposed to do?

irishjoeyo said:

LOL obviously you have no idea what it means for an application to have data "cached". To enlighten you, it means that data from that application is being stored in memory. That, in turn, means that it is using that memory.

I am aware that the Android OS frees up memory on its own when necessary. That is not my point, but you seem to think that it is. You also seem to think that a particular application using memory is the same thing as the application running at full/normal capacity when you're actually using it. That is your mistake.

To clear this up for you, imagine the following hypothetical situation: Your phone's total memory is 500 MB. There are 0 MB free. You start an application that uses 4 MB. It works. That's because something else was killed (de-cached, if you will) in order to accommodate the newly-started application. You seem to think that 4 MB would be pulled from the sky, but that's just plain silly.

Click to expand...

Once again you are wrong and that is NOT what i am implying at all. I fully understand how this works I have been using linux technologies for the last 6 years and have plenty of info how memory is cached, what were you even reading to come up with this response? I am saying that 300mb of free memory is a COMPLETE WASTE OF MEMORY and that cached apps are supposed to be there for the next time you launch it. The advantage of a high end phone is that you have more memory to CACHE MORE APPS. Background apps that are running are usually an app you were just using or connected to another application like google search and Gtalk. For the most part, there are some sort of apps running in the background no matter what. Its fine the phone knows what to do.

Found the answer in this post...

How to get Clockwork recovery, busybox, & root on 8/26 leaked RUU 3.21.605.1 - xda-developers

Need to do the payload and superuser along with the busybox files. Use in recovery.



It is amazing how much I missed root until I didn't have it again.

krelvinaz said:

It is amazing how much I missed root until I didn't have it again.

Click to expand...

Thats no joke....Froyo is nice, but has much more bloat that i cant wait to abolish from my phone.

AndyLL said:

errrrr.... it's up to the app.

Apps can be programed to run in the background.

Apps can be programed to keep the phone awake.

Well designed apps do neither unless there is a reason to.

Not every programmer writes well designed apps.

Run 'Antennas' and choose the setting to run in the background. Switch away from it and come back a few hours later and check your battery usage. Then tell me 'cached' programs are not running.

If an app is cached it means it was loaded at least once. If the user didn't do it that means it loaded on its own. That means it's possible it will reload if killed.

If that's true that means we've permently lost the memory because even if the OS dumps the program it will come back.

Click to expand...

Dude do yourself a favor and do not count on any dumb app that runs in the background to tell other dump apps what to do. That apps have not been needed since android 1.5

one11sgt said:

But they do use up battery. I was very open minded about this listening to both sides, but after trying it out myself both with and without a task killer....my battery lasts mmuucchh longer with a task killer.

Ideally, android may not need one....practically, it does.

Click to expand...

Ideally, the amount of battery used by the application being cached is the same as if that memory location was empty, the system will periodically refresh the contents of the memory location, whether or not there is something there. It is only when the application is actually using CPU that the energy use increases due to the app being in memory. That being said, if you are seeing an increase in battery life by using a task killer, that means one or more of the apps you are killing aren't just cached, they are actively using CPU at some point.

Just installed 2.2 this morning and didn't even know we got a flashlight. WOOT!

Ryd1ZZ said:

Just installed 2.2 this morning and didn't even know we got a flashlight. WOOT!

Click to expand...

lol. flashlight is nice, but there are plenty of other nice perks too.

AndyLL said:

errrrr.... it's up to the app.

Apps can be programed to run in the background.

Apps can be programed to keep the phone awake.

Well designed apps do neither unless there is a reason to.

Not every programmer writes well designed apps.

Run 'Antennas' and choose the setting to run in the background. Switch away from it and come back a few hours later and check your battery usage. Then tell me 'cached' programs are not running.

If an app is cached it means it was loaded at least once. If the user didn't do it that means it loaded on its own. That means it's possible it will reload if killed.

If that's true that means we've permently lost the memory because even if the OS dumps the program it will come back.

Click to expand...

Your example is poor. When you choose to have it run in the background, it is no longer just cached, it is active, just not in the foreground.

literacolax said:

lol. flashlight is nice, but there are plenty of other nice perks too.

Click to expand...

True, I also like how you can change the amount of time it takes to initiate the lock pattern. Is there a list of all the features cause I can't really see much difference.

Ryd1ZZ said:

True, I also like how you can change the amount of time it takes to initiate the lock pattern. Is there a list of all the features cause I can't really see much difference.

Click to expand...

You can find most of the important stuff in this thread:

http://androidforums.com/htc-incredible/161336-little-things-2-2-update-addons-changes.html

Theres also a several hundred page changelog for android 2.2 somewhere ( though it doesn't include anything HTC/Verizon did after they got their hands on it. ) I don't have the link off hand though, forgot where I saw it

Dream said:

Arg, there not "running" all the time. Silly n00bs.

Click to expand...

I don't give a crap if it's only once every 10 minutes, VZ Navigator, CityID, Amazon MP3, Skype Mobile, My Verizon Mobile are ALL showing my ps list, I have never launched any of them, and for them to EVER run without my explicit launching is unacceptable. Why in the name of Christ would I want VZ Navigator to consume memory and processor when I have Google Nav?

And anything that shows in a ps list is consuming system resources, to some extent, at all times.

Skorpios1027 said:

Your example is poor. When you choose to have it run in the background, it is no longer just cached, it is active, just not in the foreground.

Click to expand...

It was just an example. Any app developer can do the same thing in their apps with or without using a setting.

You seem under the impression that if an app doesn't have focus it isn't using resources other then memory.

You are incorrect.

You also seem under the impression that it is normal for an app that the user hasn't run to show up as a process taking up memory. ( regardless if it's using other resources or not)

You are incorrect. It means it was loaded at startup

And finally... you seem to be under the impression that Android always will make the right choice in what programs to dump when memory is low.

I prefer to make that choice myself.

Using a Automatic Task killer to kill off processes that just reload themselves is counter productive.

Using a Automatic Task killer to kill off processes that you use often is counter productive.

However....

Using a task killer to kill off processes that are running in the background that no longer need to be loading is fine.

Using a task killer to kill off processes that load at start up (that do not reload) is fine.

Using a task killer to kill off processes that you know you are not using again anytime soon to keep your memory down so memory usage spikes do not cause lag ( and perhaps lost data if Android has to dump a running program) is fine.

Andy

You guys are lucky to receive such an update! Without devs, I'd be stuck on 1.5

Even without the other stuff, 720p and led flashlight alone would be worth updating IMO.

zemerick said:

You do realize in the very quote you have, he specifically said having an app loaded in memory is not the same as it running?

You actually made HIS point.

Click to expand...

Yes, I do realize that. My point was that he seemed to contradict himself by disagreeing with what I originally stated. His idea of an app "running" is different than how I was using the term, which I made even more clear in my most recent post. It was not that an entire application was running, but that a part of it was. You can debate the meaning of the term "running" all you want, but if something is unnecessarily using memory, then I consider that something to be running. And again, that is not to say that the entire application itself is running.

tylerdurdin said:

Once again you are wrong...I am saying that 300mb of free memory is a COMPLETE WASTE OF MEMORY and that cached apps are supposed to be there for the next time you launch it.

Click to expand...

Everything you stated here is entirely irrelevant to my original point - the one that you originally disagreed with. I have at no point debated the potential wastefulness of memory. Your confusion lies in the fact that you are using a different definition of the term "running" than I am. For an app to be "running", you seem to believe that whatever components of that app that are in memory while the user is actually using that app are necessary to be in memory for it to be considered "running". That is not an incorrect definition, but it is different than the one that I used. I was using the term "running" in the sense that if any component of an app is in memory such that it appears in a task killer list, then it (or a part of it) is "running".

Here is the post that started all of this:

vnyislesv said:

Yeah, Skype, Amazon, City ID and My Verizon are always running. Annoying as hell since I don't use any of them.

Click to expand...

Now, to me, it seems that this particular person is not concerned about the difference between an app "running" and an app being cached. If I'm wrong about that, then they and only they can make that judgment. What they do seem to be concerned about is that apps that they never use have enough components stored in memory such that they appear in their task killer, and they find this "annoying" because it is totally unnecessary. Dream then called this person a "silly n00b", apparently because they didn't use the correct nomenclature, even though it was entirely beside their point. I disagreed with Dream, stating that they are actually "running" based on the memory difference that occurs when whatever a particular app has cached is killed. I was using the same definition that vnyislesv apparently used in their post because I was addressing their concerns. You are more interested in debating the definition of the term "running", but that's not the point of these forums, is it? The point is to effectively communicate with one another in a helpful manner, but you'd rather tell everyone else how "wrong" they are and how smart you are because of your implied superior linux knowledge and experience. This isn't a job interview, so nobody really cares about your experience or knowledge. They just want their concerns addressed.