Note: CityID annihilates Inc's memory

[MisterMixelpix]

I was playing around with Task Killer (again), and I decided to shut down the CityID app. It's a cute idea, but I never actually use it or need it.

Discovery? 77M -> 148M free!

That's right, the CityID crapware uses about SEVENTY megs of memory. So if you've still got that running, shut it down! Your phone will thank you!

 

[nightfishing]

I was playing around with Task Killer (again), and I decided to shut down the CityID app. It's a cute idea, but I never actually use it or need it.

Discovery? 77M -> 148M free!

That's right, the CityID crapware uses about SEVENTY megs of memory. So if you've still got that running, shut it down! Your phone will thank you!

Sorry, but that is not the way memory recovery works on Android. The change in memory had nothing (or very, very little) to do with CityID.

 

[mikewashere05]

Sorry, but that is not the way memory recovery works on Android. The change in memory had nothing (or very, very little) to do with CityID.

I have a basic understanding of how Android allocates memory and in process of attaining a computer engineering degree so out of curiosity could you elaborate more?

All the task killer does is kill the process (kill <pid>), so if all the OP really did was kill the CityID process and memory freed up I'm seeing a direct correlation here.

 

[jamor]

That picture is so gross

 

[bjanow]

I was playing around with Task Killer (again), and I decided to shut down the CityID app. It's a cute idea, but I never actually use it or need it.

Discovery? 77M -> 148M free!

That's right, the CityID crapware uses about SEVENTY megs of memory. So if you've still got that running, shut it down! Your phone will thank you!

Where did you see this so we can replicate?

 

[nightfishing]

I am no expert, but killing CERTAIN processes seems to trigger Android to release a chunk of memory. The longer since this has been done (the lower the current memory is) the greater the change.

The key to all of this is that the "free memory" number has little to nothing to do with the performance of the OS. It will grab what it needs when it needs it

EXAMPLE: my phone is at 57M, I close the clock widget (inactive) which was "using" 4M and my free memory jumps to 101M

 

[Rubik76]

On my Inc, City ID is running (at the moment):
Resident: 5.4MB
Shared: 2.3MB
Effefctive: 3.1MB

 

[armoredsaint]

Google Maps suck up most of my memory.