-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help I have 2.2... Now what the Hell am I supposed to do?
- Thread starter danoack
- Start date
-
- Tags
- htc droid incredible
JFeisty
Member
Install Launcher Pro....you can hide icons from the app drawer! ('course, you won't have sense running)
You can't root if you went RUU, wait for them to come up with root for 2.2..
You lazy guys should have just flashed the Official OTA rom like Virtuous... That ROM even comes with all the bloat ware your complaining about removed.
These 2 links are anyone needs to have Root and Install Official 2.2 Froyo ROM.
[ROM] Virtuous v2.4 (8/31/10): Stock Sense/Froyo v3.21.605.1 w/Fixes & Enhancements - xda-developers
[GUIDES] Root, nand unlock, radio update, Froyo 2.2 update, Restore stock radio/rom - xda-developers
You lazy guys should have just flashed the Official OTA rom like Virtuous... That ROM even comes with all the bloat ware your complaining about removed.
These 2 links are anyone needs to have Root and Install Official 2.2 Froyo ROM.
[ROM] Virtuous v2.4 (8/31/10): Stock Sense/Froyo v3.21.605.1 w/Fixes & Enhancements - xda-developers
[GUIDES] Root, nand unlock, radio update, Froyo 2.2 update, Restore stock radio/rom - xda-developers
zemerick
Android Enthusiast
None of those should actually be doing anything and can be ignored ( My Verizon should only show when it is actually running. I needed to open it a second time and back out to get it to close on it's own, but when I did it the process was gone. )
Terabethia
Android Expert
Ummm... you mean that you have 5 new icons on your homescreen? And you want to remove them...
If that is really what you are talking about, it's simple. Long press on the icon and drag it to the trash can. Problem solved
NoRegrets78
Well-Known Member
The only logical thing to do after you get the update to 2.2 is to start posting threads demanding Gingerbread.
irishjoeyo
Android Enthusiast
Um, yes they are. If they weren't, memory wouldn't be freed up after killing them.
literacolax
Member
lol. as if it isnt bad enough most people still dont have the OTA you want to start a thread about wanting gingerbread. Lets do it.
mcscissorhands
Lurker
Anyone know of any good flash sites so I can show off my new froyo abilities?
Also, don't shoot me and please forgive my ignorance, but does anyone know when the adobe flash app comes out? I didn't see it in the market, only the stupid showcase.
Thanks, from a patient, proud new froyo user.
Also, don't shoot me and please forgive my ignorance, but does anyone know when the adobe flash app comes out? I didn't see it in the market, only the stupid showcase.
Thanks, from a patient, proud new froyo user.
tylerdurdin
Android Enthusiast
No, your wrong. cached applications are only stored in memory, memory on an android is completely wasted if it is empty. My captivate has 512mb of ram if it is all empty, you would not be USING 512mb to say, run your web browser. At this point the biggest problem apps running in the background are Taskkillers and battery savers.
Your OS is designed to shut apps down if the phone requires more ram to run an app. The apps you use the most are stored there, for immediate launch next time you use it. A manual kill, app killer i guess is cool if your running 20 different apps a day. This is why people using taskillers are still complaining about phone lag, it is because the entire application has to be reloaded. You can also use a manual taskiller to kill off service provider apps that launch on start up. I can see why you believe otherwise, but you are not correct.
irishjoeyo
Android Enthusiast
You're still wrong. Just like I said, if nothing related to a particular app was running, then no memory would be freed up by killing anything associated with that app. It's simple math. So, try again.
gornul
Newbie
You kinda have to pick one. Either
A) Learn what's going with the expensive piece of hardware you've acquired, or
B) Accept that you can't use it to its full potential.
Seriously I didn't know jack about this phone before I signed up for these forums. A little occasional skimming and reading of guides, how-tos, and XDA links, and I'm pretty damn knowledgeable. This place is a great opportunity to learn.
There IS no way to discuss the finer details of rooting and power-tweaking your phone without the "nerd talk" you're taking issue with.
A) Learn what's going with the expensive piece of hardware you've acquired, or
B) Accept that you can't use it to its full potential.
Seriously I didn't know jack about this phone before I signed up for these forums. A little occasional skimming and reading of guides, how-tos, and XDA links, and I'm pretty damn knowledgeable. This place is a great opportunity to learn.
There IS no way to discuss the finer details of rooting and power-tweaking your phone without the "nerd talk" you're taking issue with.
tylerdurdin
Android Enthusiast
stored or CACHED apps are not running, but you believe whatever you THINK you know.
secretLOVER
Android Enthusiast
What do you think people are trying to do!? The guys asking a simple question and being called lazy n having his thread thrashed. It is an expensive piece of equipment. That's why some are taking time before rooting or anything.
irishjoeyo
Android Enthusiast
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.
gornul
Newbie
Which is perfectly fair, and I'm not saying it's lazy to not want to screw with your phone (I handled all the rooting/etc on my wife's, I wouldn't call her lazy). But when you want to do things that require rooting (removing bloatware, for instance, which I'm understanding to be the OP's issue) you need to be willing to learn enough to do it.
You can't have your cake (remain willfully ignorant about the technical side of the device) and eat it too (try to do all the fancy stuff that comes with knowing more about the device), is all I'm trying to say. (Unless you've got a friend who will actually DO it for you, like I took care of my wife's.)
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.
zemerick
Android Enthusiast
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.
just like you said, Memory is irrelevant to the question of a process "running". A process can actually be removed and not running, but still have a portion "cached" in memory. This cached memory does not affect your performance, because as you pointed out: If something else needs that memory, it just takes it away.
What DOES matter is cpu utilization. The "bloat" processes such as CityID, Amazon MP3, etc. are all simply cached, and idle. They have data cached into memory but are not actually doing anything. Thus, there is no reason to bother with killing these processes as they are behaving properly. Freeing up memory will only drain your battery a little more ( because you had to start a process and use a tiny bit of power to "kill" the process and clear the memory ) and also slows down your phone ( both because you had to load another process to do it, which temporarily used up some of your CPU cycles, as well as any time you might want to load that process it is no longer in memory and must fully load from scratch.)
NOTE: With the "bloat" apps, it's even worse because the app just auto-starts back up, thus you also did not even accomplish freeing up any memory. In fact, it is possible the apps needed to take memory from something else to fully start back up and get back to where they were.
Now, yes: This is all assuming the app is properly coded ( all of the "bloat" apps are behaving properly, at least on my phone. So this does not apply to them. ), so you may need to force close certain poorly coded apps. It happens.
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.