Database Develop

google maps and factory reset question

my google maps is allways running i cant se it running in "running proceses" but if i check wats eating my battery in "batery use" google maps is top of the list whit 35%
also if i do a factory reset will it delete the preinstaled programs that the phone came whit also(google maps,youtube etc)?
and in running proceses it shows 78 mb used and 214 mb free.....wasent it suposed to have 512 mb of ram?

funstuffalex said:
my google maps is allways running i cant se it running in "running proceses" but if i check wats eating my battery in "batery use" google maps is top of the list whit 35%
also if i do a factory reset will it delete the preinstaled programs that the phone came whit also(google maps,youtube etc)?
Click to expand...
Click to collapse
No, the pre-installed programs like Maps and YouTube shouldn't be impacted, they're in the /system/app folder, not the /data/app folder (where user installed apps go). Even if the Google apps were deleted, they're all available in the Market, so no big deal to download them manually if necessary.
The DATA for the pre-installed apps will get erased, though.
Your battery usage pointing to google maps may be related to running the Latitude portion of google maps...it's constantly on and tracking your position. go into the settings for google maps (layers perhaps) and make sure Latitude is turned off.
funstuffalex said:
and in running proceses it shows 78 mb used and 214 mb free.....wasent it suposed to have 512 mb of ram?
Click to expand...
Click to collapse
The missing memory is used by the system and not available to you; this confuses many people, but you should be okay.

google latitude is not on
i cant clouse maps even in battery use if i click on maps and force stop it then refresh and its still there

funstuffalex said:
google latitude is not on
i cant clouse maps even in battery use if i click on maps and force stop it then refresh and its still there
Click to expand...
Click to collapse
Non-rooted, you might try going into Settings/Applications/Manage Applications/ All then finding Maps and uninstalling updates. Also, clear data, clear cache, etc. This might help you out.
Are you rooted?
The way Android works, killing tasks isn't advised. One of the reasons is exactly what you're seeing (I think what you're seeing)...if you kill an app that Android thinks you're going to use again any time soon, it just re-opens it in the background. It shouldn't be sucking up any significant resources in that state, though. Android doesn't like a lot of free memory..the linux mantra is "free memory is wasted memory".
Anyways, if you're rooted, you can try getting Autostarts off the market and tell it to keep Google Maps from autostarting on boot.
Also, if you're rooted, you could use Titanium or Root Explorer to delete the Google Maps apk and then re-download it from the Market.

What he's experiencing is a growing problem with Google Maps. There's currently a ton of people commenting about it in the market and I've seen it first hand.
I sat down with a bunch of friends the other day (all of whom have one Android device or another) and we all checked our battery usage has Google Maps at either the first or second position on the list. In the group was my Nexus S, a Captivate, a Nexus One, and a G2. It appears to be a problem with the newest update, probably related to the caching its doing with the map data, but that's just a guess.

[Q] Close apps?

Old question I know, but most answers only mention memory handling. When memory runs out, Android closes background apps automatically.
Fine, but what about all the CPU the app takes up while loaded in background?
I just made a little test with a few games (only apps I have that will actually use up all memory). Memory-wise it works fine, if I load to many the games in the background will get unloaded. But if I only load up Worms and press "home" to get it into the background, it will still be loaded and take ~30% CPU
If I use "back" most apps will really close, but some are really annoying to close this way since you have to go through all the pages you have viewed (like IMDb).
The browser will not even close this way so I might as well just press "home".
What's the solution? I dont want to find out the specific way to exit for every single app, I want a universal solution. And "home" doesnt seem to be that universal as I hoped.

ram waste (and google messaging service)

I know that G1 has few ram, so I think we need to don't waste it for unuseful services.
I'm using froyo by laszlo 5.1.
When rom start up, there are a lot of unuseful sercices that waste ram:
1) Google Messaging Service
What is it? I don't think that is for SMS/MMS. It waste about 5 - 6 MB of ram!!
The service start up automatically after some minutes I close it..
2) Virtual Keyboard
Yes! Standard virtual keyboard waste about 5mb of ram.. It is useful on our g1?
Why a stupid virtual keyboard waste 5mb of ram? (gingerbread keyboard from market waste 8mb.. )
3) NetworkLocationService, is from android.apps.maps. It will starts everytime you open google maps. If you close google maps, the service continue running... (olso using task killer).
Waste from 5mb to 8.1mb of ram...
4) MediaPlaybackService, is from android.music, it waste about 6mb and starts every time you open music.apk
The real problem for me is google messaging service!
Because I don't know what is it and starts automatically.
I think that mediaPlaybackService and NetworkLocationService shut down automatically if ram is needed (I really hope that) but googleMessagingService and virtual keyboard stay on all the time, wasting 11mb!
For now I have disabled virtual keyboard (but some time is usefull).
But google messaging service?

If I'm not wrong, I think "google messaging" is something like every push/receive data method through the google cloud server. So it is always needed for most of the time especially if you are using gmail and other google synchronisation apps

uhm.. wow..
it's possible that android waste handfuls of ram mb for doing anything?
I hate java.. and virtual machines

Task switching without reloading? What memory is required?

Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?

douginoz said:
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
Click to expand...
Click to collapse
Try enabling zram, I haven't tried it personally but its supposed to allow for more multitasking.
Sent from my Nexus One using xda app-developers app

Moved To Q&A​
You may of considered it dev based, but its a question so belongs in the Q&A section.​

I've tried ZRAM now for a couple of days but makes no difference. I also have the problem on another Android device. I'm convinced its some sort of design limitation of the opsys or something. When I start up Grindr, it takes a long time to load all the images, make connections, etc. Then I start of Gruff, and it does the same. As long as I don't try to go to another app, I can flip between the two of them without them restarting/reloading/reinitialising themselves. That is clearly because their pages didn't get swapped out of memory or flagged for deletion and deleted.
But if I do something else, or even try to use additional functions within either app, its too much and the next time I try to flip to the other app, it has to reload and reestablish connections etc.
Its not just those apps either. The same with a game like Candy Crush. Or many many apps.
So either my devices don't have enough memory of some form to allow many concurrent apps to run without being swapped out, or Android can't handle it and unnecessarily swaps out or deletes a process's memory pages to make room for the next process, >>> even if the device has plenty of memory<<<.
I don't know which type of memory the opsys needs if this is the case. I'd like to know so that i can make sure there's ample available so that this constant restarting doesn't keep happening. It seems stupid to me that Android does this if the device has got "heaps" of available memory (no pun intended). Newer devices will continually have more and more built in memory, so if Android is doing this arbitrarily and not because of space issues then its, well, stupid.
I have to assume its my devices that are the problem. They're both old (Nook Color, Nexus One). But with the NC, I'd assume we can partition some of that 5GB for use as main memory to run lots of processes concurrently, without this annoying swapping/page deletion/forcing re-inits all the time.
I'm also having problems figuring out where in XDA to post this question - its not NC specific, or dev specific, but I need answers from people that know the Android architecture so I can work out if its possible to stop this from happening.

I want to see what's consuming my ram.

Hello everyone.
Even after hibernating all the apps, still 2GB of my ram is used. I want to look at all the processes that are using the ram. How can I do that?
Cheers!

Until someone comes up with a better answer...
Settings/Apps. Under each app there are stats for used storage and memory used in the past few hours. Might give you a clue.

xhamadeex said:
Hello everyone.
Even after hibernating all the apps, still 2GB of my ram is used. I want to look at all the processes that are using the ram. How can I do that?
Cheers!
Click to expand...
Click to collapse
Because ANDROID KNOWS that UNUSED RAM is WASTED RAM.
It ***preloads*** all of the things, in order of what it believes is the likelihood of you using those particular things.
This way when you actually DO use one of those things, it is ***already loaded*** (and starts fast).
Stop "hibernating" things. You are breaking Android.

doitright said:
Because ANDROID KNOWS that UNUSED RAM is WASTED RAM.
It ***preloads*** all of the things, in order of what it believes is the likelihood of you using those particular things.
This way when you actually DO use one of those things, it is ***already loaded*** (and starts fast).
Stop "hibernating" things. You are breaking Android.
Click to expand...
Click to collapse
Hmm.. You have a point..
So, is using Greenify a bad Idea?

xhamadeex said:
Hmm.. You have a point..
So, is using Greenify a bad Idea?
Click to expand...
Click to collapse
Bad idea.

yea there's two built-in ways to view running processes. One is directly Settings. Scroll down to where it says Memory. Open and check it out. I know. Google might as well not even wasted their time making that activity since it's next to useless. The other one is located in Developer Options. It's labeled "Running Services" and gives you stats on what apps are running, how long, etc. Yea, not very helpful either since there isn't much you can do besides uninstall some things or do the root and ransack thing. It's intentionally made like that, just like the way android battery stats are completely useless for nailing down offensive background services. Google likes it that way. They make money by tracking your location and serving you up with as many ads as possible. While it's true what dude said about the way Android preloads and makes a lot of stuff ready in RAM, hibernating, and using task killers is basically like working against your system resources, don't listen to people who yell things at you because they've been brainwashed by companies and developers who want their services installed, front-and-center, autostarting, and running 24/7 in your device's memory. Why else you think every website has a banner talkin' bout "oooh ooh install our app" and grant as many permissions as possible while some even go as far as sabotaging their own services via their website so users feel forced to install the app. They don't care about you, your cpu, or your experience as long as it's filled with ads and periodically uploading analytics and usage stats and the best way to do that is to have background and persistent services to silently restart their location polling or pointless notification systems designed solely around getting you to interact with the app. I'm not talking about things like email, messaging, or whatever other app you depend on or feel is important enough to keep close at a tap of finger. My suggestion is to analyze those settings activities I named earlier or a 3rd party one like BBS and make some decisions about what you are willing to delete. Compromises can be made depending on what's important to you and also with root. Half (or more) of the apps in your phone that have boot receivers and other various event listeners up the wazoo have no business knowing your phone is even on until you tap it's little icon. This is opinion of course because others will tell you you're breaking android and a bunch of other nonsense they've been fed by google to address the people, like me, who are tired of seeing google and other apps (usually ones my by behemoth corporations) that run constantly in the background even though I open up and use whatever particular app maybe once a week. If you're rooted, there is a lot you can do to take control of apps that like to stay nudged up as close as possible in the queue and keep open connections. It all depends on you and how you use your device. Don't listen to know-it-alls who yell at you IN ALL CAPS. Either accept the fact that google, facebook, admob (and whoever else app you have that thinks it's the most important) own your phone, or do a little research for yourself because regardless of what homeboy said, it's easy to see that available RAM feels way smoother than ram that has to wait for android to move pokey balls out of the way...just sayin

ElwOOd_CbGp said:
yea there's two built-in ways to view running processes. One is directly Settings. Scroll down to where it says Memory. Open and check it out. I know. Google might as well not even wasted their time making that activity since it's next to useless. The other one is located in Developer Options. It's labeled "Running Services" and gives you stats on what apps are running, how long, etc. Yea, not very helpful either since there isn't much you can do besides uninstall some things or do the root and ransack thing. It's intentionally made like that, just like the way android battery stats are completely useless for nailing down offensive background services. Google likes it that way. They make money by tracking your location and serving you up with as many ads as possible. While it's true what dude said about the way Android preloads and makes a lot of stuff ready in RAM, hibernating, and using task killers is basically like working against your system resources, don't listen to people who yell things at you because they've been brainwashed by companies and developers who want their services installed, autostarting, and running 24/7 in your device. Why else you think every website has a banner talkin' bout "oooh ooh install our app" and grant as many permissions as possible while some even go as far as sabotaging their own services via their website so users feel forced to install the app. They don't care about you, your cpu, or your experience as long as it's filled with ads and periodically uploading analytics and usage stats and the best way to do that is to have background and persistent services to silently restart their location polling or pointless notification systems designed solely around getting you to interact with the app. I'm not talking about things like email, messaging, or whatever other app you depend on or feel is important enough to keep close at a tap of finger. My suggestion is to analyze those settings activities I named earlier or a 3rd party one like BBS and make some decisions about what you are willing to delete. Compromises can be made depending on what's important to you and also with root. Half (or more) of the apps in your phone that have boot receivers and other various event listeners up the wazoo have no business knowing your phone is even on until you tap it's little icon. This is opinion of course because others will tell you you're breaking android and a bunch of other nonsense they've been fed by google to address the people, like me, who are tired of seeing google and other apps (usually ones my by behemoth corporations) that run constantly in the background even though I open up and use whatever particular app maybe once a week. If you're rooted, there is a lot you can do to take control of apps that like to stay nudged up as close as possible in the queue and keep open connections. It all depends on you and how you use your device. Don't listen to know-it-alls who yell at you IN ALL CAPS. Either accept the fact that google, facebook, admob (and whoever else app you have that thinks it's the most important) own your phone, or do a little research for yourself because regardless of what homeboy said, it's easy to see that available RAM feels way smoother than ram that has to wait for android to move pokey balls out of the way...just sayin
Click to expand...
Click to collapse
Holy wall of text Batman!
You've got a couple of points hidden inside that rambling, but dude... If you want anyone to read that, try that little thing called paragraphs.

Didgeridoohan said:
Holy wall of text Batman!
You've got a couple of points hidden inside that rambling, but dude... If you want anyone to read that, try that little thing called paragraphs.
Click to expand...
Click to collapse
Ah...apologies. I may have been a little bit hopped up last night on the leftover holiday spirits but how else to explain what I see as google's all-over-the-place ridiculous approach at making it as god awful experience as possible for people interested in granular control over their devices' /system. I just got done flashing, setting up, and going thru the motions on a new phone so I may have been a little annoyed as well. lolz hope it helps someone.