Related
Love the phone but a few times the launcher has redrawn after exiting an app because of most likely memory issues. Anybody using this option? Assuming over time this would keep more memory free and reduce this issue. Any thoughts?
Sent from my Galaxy Nexus using xda premium
mobilehavoc said:
Love the phone but a few times the launcher has redrawn after exiting an app because of most likely memory issues. Anybody using this option? Assuming over time this would keep more memory free and reduce this issue. Any thoughts?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This is one of the reasons why I don't like that Google included these developer options pre-installed on this phone. They're developer options for a reason, we can install them if we need to.
This feature is designed so that developers can test their app to be sure that data is properly saved when is no longer in the foreground. For example, if a user receives a phone call or jumps to another app, the app needs to do what is necessary to save it's data. At times, Android can kill a process in the background. If the user plans to go back (perhaps they finished the phone call), they want to see what it is they were working on last. The developer is supposed to handle this case by rebuilding everything as it was before (to provide that seamless experience for the user when switching between apps).
This debug feature helps us test that it works.
For the average user, all you're really more likely to do is slow down your apps. As they will have to rebuild themselves when you resume them, and you may even open yourself to more quirky bugs (for those apps that didn't properly test the above scenario).
So please don't enable it unless you're doing it for development purposes. My 2 cents.
*EDIT* Here's a page from the Android Dev Guide justifying my explanation:
http://developer.android.com/guide/developing/debugging/debugging-devtools.html
Immediately destroy activities
Tells the system to destroy an activity as soon as it is stopped (as if Android had to reclaim memory). This is very useful for testing the onSaveInstanceState(Bundle) / onCreate(android.os.Bundle) code path, which would otherwise be difficult to force. Choosing this option will probably reveal a number of problems in your application due to not saving state. For more information about saving an activity's state, see the Activities document.
Click to expand...
Click to collapse
(and yes, they used to call it "Immediately destroy activities")
Thanks. I turned it off. Did notice some bugs while on. I just wish with 1GB of RAM the launcher wouldnt have to reload. Hopefully things get better. Might just be my apps but it happens quite often when leaving the browser.
Sent from my Galaxy Nexus using xda premium
mobilehavoc said:
Thanks. I turned it off. Did notice some bugs while on. I just wish with 1GB of RAM the launcher wouldnt have to reload. Hopefully things get better. Might just be my apps but it happens quite often when leaving the browser.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
weird.. how many widgets do you have on your launcher? the more widgets you have, the slower the launcher is.
Have you tried another launcher? The stock launcher has never been known for being fast and efficient, although I haven't had any issues with it (whereas I'm a LauncherPro fan on my other devices).
kwazi said:
weird.. how many widgets do you have on your launcher? the more widgets you have, the slower the launcher is.
Have you tried another launcher? The stock launcher has never been known for being fast and efficient, although I haven't had any issues with it (whereas I'm a LauncherPro fan on my other devices).
Click to expand...
Click to collapse
I have quite a few Widgets but nothing too crazy I don't think. I use LauncherPro on my other devices as well but I love this new launcher so I'm going to stick it out. Like I said the most common task that causes the issue is when I'm using the web browser and then come out of it. Otherwise its been stable. I've noticed the same thing with Honeycomb on my Xoom so it might just be one of those things I have to put up with.
Sent from my Galaxy Nexus using xda premium
i'm also noticing some redraw and occasional lag when hitting the home button.
I'm hoping that CM9's custom launcher will have an option to lock it in memory- that may increase the performance by a lot.
also when replacement launchers like go launcher start optimizing more for ICS those might be good options.
Have you tried converting your launcher into a system app? You'll need to use Titanium Backup Pro or something similar to do it for you, or simple copy the APK into your system/app folder... Really sped up my launcher!
shawnshine said:
Have you tried converting your launcher into a system app? You'll need to use Titanium Backup Pro or something similar to do it for you, or simple copy the APK into your system/app folder... Really sped up my launcher!
Click to expand...
Click to collapse
Did you see the date on this thread, almost 8 months old
Sent from my Galaxy Nexus using xda premium
95Z28 said:
Did you see the date on this thread, almost 8 months old
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
... and yet people still continue to discover the thread and benefit from it.
Thanks for clarifying the meaning of "Don't keep activities"
my razr xt910 cannot be counted upon to run smoothly with all the apps simultaneously running and forcing itself to go into reboot. i then fancied an iPhone single styled system (as compared to Android multi-talks) cuz iPhone looks robust and responsive. all the killer that claimed to do the job looked more of a farce and then when i stumbled upon the destroy activity i was like OMG. srsly b4 using it I've only got just inner 100mb of ram, after using it i have a whooping 400mb ram. UI appears faster and all. regarding the relaunching of apps and battery life being used up. i think I'll start to worry about it on a later date. what say any body. ooh yes to add on, even after i deleted 40 apps on my phone it still hanged like fcuked. i guess i can reinstall them back again and not have to worry about it. btw i can't seem to root my xt910 for nuts so i can't custom ROM it along with all other fanciful mods that i hear about what others did to their phones.
I love my Galaxy Nexus, but what's driving me crazy is how it shuts down any app whenever I switch out of it, even if I use the -completely useless so far- multitasking soft key. So for instance I'm waiting for a YouTube video to load, so I temporarily switch out of it to do something else (this is a smartphone isn't it) and come back, and find it reopening the video as if I just did it. Same thing with the browsers. I have 2-3 tabs open, and decided to check out something on the homescreen. Big mistake. When I get back will have to wait for all the tabs to reload.
Anyway to keep apps running in the background?
Sent from my Galaxy Nexus using XDA App
I think YouTube just does that. It has been mentioned before. No problem with the browser.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
If your using a Verizon nexus, it partly has to do with Verizon's cdma network, not just android. Plus it would slow your phones operation down and you would see more force closes due to limited resources.
Edit— sorry everybody, did a little drunk forum trolling last night. Everything I posted was false. The other poster was correct and I deserve all the shame.
Transmitted from my Galaxy Tab 10.1 via Tapatalk
Most likely you have an app running thats killing processes. If you have any task manager/killer remove it immediately.
As far as youtube goes, youtube will NEVER keep a video paused or continue playing if you leave. It saves what you were on, but thats it. few reasons for that.
Now, my experience today and no issues.
Facebook, Browser (4 tabs), NFL'11, and twitter all running and they all saved what i was doing and none of them ever closed.
in fact, 3 hours after, the 4 tabs were still open. I've actually had tabs open for 3 days straight that i forgot to close and the browser just made new ones.
and these are not just text sites. I had the Battlefield 3 battlelog, nfl.com, battlefield wiki, and the verge mobile all on.
My browser will keep pages open for days if I wanted to...strange! You're using stock browser?
Sent from my NookColor using XDA Premium App
stock browser is awesome. especially the inverted mode.
Pretty amateur thread. Come on
Sent from my Galaxy Nexus using xda premium
Stardate Tab 10.1 said:
If your using a Verizon nexus, it partly has to do with Verizon's cdma network, not just android. Plus it would slow your phones operation down and you would see more force closes due to limited resources.
Transmitted from my Galaxy Tab 10.1 via Tapatalk
Click to expand...
Click to collapse
I can't find one fact in your entire statement. What could CDMA possibly have to do with it? Also, you wouldn't see more 'force closes'. When Android runs low on RAM it selects the oldest cached app and ends it, unless it's active.
once again, amateur thread. **** needs to be closed down
TareX said:
I love my Galaxy Nexus, but what's driving me crazy is how it shuts down any app whenever I switch out of it, even if I use the -completely useless so far- multitasking soft key. So for instance I'm waiting for a YouTube video to load, so I temporarily switch out of it to do something else (this is a smartphone isn't it) and come back, and find it reopening the video as if I just did it. Same thing with the browsers. I have 2-3 tabs open, and decided to check out something on the homescreen. Big mistake. When I get back will have to wait for all the tabs to reload.
Anyway to keep apps running in the background?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Do you have Don't keep activities checked in the development part of settings? Go to Settings>Developer Options, scroll all the way down, and look if you've enabled the option I've mentioned above
Sent from my Galaxy Nexus using xda premium
I have this exact same problem, with the browser and even with games.
I have no task manager. I have watchdog which i believe doesnt kill any processes itself and i have juice defender; could that be whats causing this problem?
I keep hearing about this, am I seriously the only one that can swipe apps away from the recent apps and they actually close?
Sent from my Google phone
ChongoDroid said:
I keep hearing about this, am I seriously the only one that can swipe apps away from the recent apps and they actually close?
Sent from my Google phone
Click to expand...
Click to collapse
possibly you are...
because for me and more than 5 of my friends using the same phone, those swiping aways only close the shortcut regardless of the app running in background or not.
DO THE FOLLOWING
1) go to settings, apps, running apps.
2) with that open, hit the multitask button that shows all apps running.
3) swipe away
4) watch it get killed off your running apps list.
5) grow up
Im not sure what all the *****iness is about but the problen I and i believe the OP were having was quite real and serious.
Any time you switched out of an app or game, even if only for a second, when you switched back it would restart the app or game and in the case of the browser reload the webpage.
Now, ive uninstalled watchdog and the problem seems to have gone away.
Is anybody else using watchdog having this problem?
People need to understand that devs put this code INTO THEIR APPS. Killswitches are hard coded into apps to let the system kill them if they have been in the background. A good example is Opera Mobile. It has a low priority that is coded in BY THE DEV.
schizophrenia said:
possibly you are...
because for me and more than 5 of my friends using the same phone, those swiping aways only close the shortcut regardless of the app running in background or not.
Click to expand...
Click to collapse
Not possibly, I know I am. Home key keeps it running, back key caches/closes it. Certain apps perform differently as foreground tasks and some as background tasks. I think some can't be multi tasked like big games and stuff but as previously said that's on the dev side not androids.
Sent from my Galaxy Nexus using xda premium
So do you guys find it necessary to have a ram manager to free memory or no ?
No, ics have a good system to manage ram.
No. Creates more issues than it solves.
+1 for no. Watchdog has always been a must have for me, but it hasn't yet had to call out an app on my SGN.
No. Don't use automated tools to kill tasks and free up memory... in Android, free memory is wasted memory. You make your phone work harder when you interfere with its built-in memory management.
I kill running services that shouldn't be running... That allows for more RAM to be used by active applications.
EP2008 said:
I kill running services that shouldn't be running... That allows for more RAM to be used by active applications.
Click to expand...
Click to collapse
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
adrynalyne said:
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
Click to expand...
Click to collapse
Funniest thing I read all day and its true
adrynalyne said:
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
Click to expand...
Click to collapse
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You have no idea how android works and deserve to have your nexus confiscated.
Sent from my SGH-T989 using XDA App
EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Android does not operate like windows. Apps listed as "Running" are actually only loaded in ram and are not using cpu cycles or battery power. Android loads them in ram in order for them to start/be available more quickly to the user. If Android needs more ram for a task, it will remove any thing it needs to in order to free up more ram. You are wasting battery power and cpu cycles by "killing" those apps/service. If you think of ram as a memory stick you will realize that once something is loaded there, it doesn't take any power to keep it there.
Good luck
Good luck
jordanishere said:
You have no idea how android works and deserve to have your nexus confiscated.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
System services should obviously not be messed with, but disabling autostarting services that you don't use is generally not a problem. It may take more power/time to start up apps that use those services (since they will have to be manually started), but if it's an app that you use infrequently it may be worth doing.
Intelligently tuning what services are allowed to autostart themselves is NOT the same as indiscriminately killing apps chasing after "free memory".
Personally, I wouldn't terminate services, but only modify which ones are allowed to automatically start up with the OS.
codesplice said:
if it's an app that you use infrequently it may be worth doing.
Click to expand...
Click to collapse
Is it worth doing when Android does this automatically?
Sent from my SGH-T989 using XDA App
EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
you basically proved what he said was true
I agree with using "Autostarts", it's one of my fav apps and cuts down on startup time and certain apps like to be triggered for all kinds of rediculous things. Once again though I think it is counterproductive to use automated task killers. Watchdog will alert you of apps running away with your ram and battery, but does not just auto kill all random apps. As far as the Amazon AppStore, I agree that it can be very malicious with RAM if it wants to be even when just checking the FAOTD in the mornings, on my Atrix I would get constant alerts from Watchdog for Amazon AppStore. On my SGN however I have yet to recieve ANY alerts for ANY app yet from Watchdog, this leads me to think there is better optimization going on with ICS or the Nexus than I had with Gingerbread and Atrix.
Is there any reason not to use AutoStarts or WatchDog? They are not auto killing apps at all. And I am requesting a "real" technical explanation not just you opinion or a "think of it like.." story, those are useless to me and offer no explanation.
jordanishere said:
Is it worth doing when Android does this automatically?
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Eh, usually there's not much benefit to be had - but preventing a service from auto starting when you might not use its app for the entire time Android is booted won't cause any problems. You're essentially "freezing" the service while still allowing it to be used on demand .
WiredPirate said:
I agree with using "Autostarts", it's one of my fav apps and cuts down on startup time and certain apps like to be triggered for all kinds of rediculous things. Once again though I think it is counterproductive to use automated task killers. Watchdog will alert you of apps running away with your ram and battery, but does not just auto kill all random apps. As far as the Amazon AppStore, I agree that it can be very malicious with RAM if it wants to be even when just checking the FAOTD in the mornings, on my Atrix I would get constant alerts from Watchdog for Amazon AppStore. On my SGN however I have yet to recieve ANY alerts for ANY app yet from Watchdog, this leads me to think there is better optimization going on with ICS or the Nexus than I had with Gingerbread and Atrix.
Is there any reason not to use AutoStarts or WatchDog? They are not auto killing apps at all. And I am requesting a "real" technical explanation not just you opinion or a "think of it like.." story, those are useless to me and offer no explanation.
Click to expand...
Click to collapse
I relied upon autostart tuning and Watchdog on my N1, but haven't experienced a real need for either on the SGN. Not necessarily a technical response, but just my experience.
Wow, the ignorance on XDA is staggering.
A RUNNING SERVICE is not the same as a cached app or background process.
Why the heck would anyone want 3 or 4 running services in the background when they don't need them running?
Right now, I have the logmein service using 26mb, Amazon app store using 38mb, pulse taking up 43mb and I'm NOT using these apps. They are running as services and using ram, battery and cpu.
Continue to defend Android and all its flaws. The user doesn't always have to accept how poorly some things function.
Sent from my Galaxy Nexus using Tapatalk
EP2008 said:
Right now, I have the logmein service using 26mb, Amazon app store using 38mb, pulse taking up 43mb and I'm NOT using these apps. They are running as services and using ram, battery and cpu.
Continue to defend Android and all its flaws. The user doesn't always have to accept how poorly some things function.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Less an Android flaw and more related to how developers wrote those apps. Otherwise I think we are in agreement though.
codesplice said:
I relied upon autostart tuning and Watchdog on my N1, but haven't experienced a real need for either on the SGN.
Click to expand...
Click to collapse
why?
10char
Sorry for the vague title.
When apps that require additional data (GTA III, Spectral Souls, ect) are downloading, I find that I need to keep them running in the foreground.
If I open GTA III, let it start downloading data, switch to home and do other stuff, then switch back, the app immediately closes and I have to resume the download by relaunching the app.
I am not familiar with downloading data for apps so I am not sure if this is expected behavior or if there is some issue with my tablet.
Thank you in advance.
I have experienced the same issue.
Also even when I play a game and go to the home page to look at something and try and get back after a few minutes the game restarts.
Its as if multitasking does not work or the applications are being killed.
Sent from my Nexus 7 using xda premium
One of new features in jelly-bean is closing non used apps automatically instead of keeping them in ram
like android does normally, to controll dfault system behaviour in this case go to setting/developer options/keep activities, this may be causing problems, from developer point of view every app should be killed when user quits is., and android activity life cycle was sometimes real pain in the ass, especially in case of porting apps from other platforms.
Sent from my Nexus 7 using xda app-developers app
Thank you for the response. But this is not true multi tasking then. And what is the default standard limit mean? Thank you.
Sent from my Nexus 7 using xda premium
i think in the setting u can delay this?? not sure where but im sure i saw something like that...
I came from the t-mobile galaxy s2 and it ran all my tasks in the background. For example, I'd load up a page and then check my email and I'd come back to see it fully loaded.
Whereas, on my Galaxy Nexus if I try to do that it'll have to reload the page.
I know this was a problem on the HTC one X and S, but has this always been something going on in the Nexus or was it after the update to jellybean?
Is there a way to enable apps running in the background?
Thank you in advanced.
jlim0512 said:
I came from the t-mobile galaxy s2 and it ran all my tasks in the background. For example, I'd load up a page and then check my email and I'd come back to see it fully loaded.
Whereas, on my Galaxy Nexus if I try to do that it'll have to reload the page.
I know this was a problem on the HTC one X and S, but has this always been something going on in the Nexus or was it after the update to jellybean?
Is there a way to enable apps running in the background?
Thank you in advanced.
Click to expand...
Click to collapse
Mine does it fine Idk what's going on with yours :3 i multitask all the time
Sent from my Galaxy Nexus using Tapatalk 2
you prolly got too many stuff running in the background at all time thats eating up your RAM
cant blame you seems like a gig of RAM isnt enough anymore
I'll agree with the others. Mine usually works the way you have described but sometimes it doesn't, especially with Chrome. If you wait too long the OS will also kill the app no matter if there's enough free ram or not iirc. I'd think if you just switched to email or sms or the alike, then switched back to the browser within a couple of minutes it should work just fine. 2gb of ram would definitely help though!
Do you have the setting to kill apps after exiting enabled in Developers Settings?
Turn that off if it's on.
Sent from my Galaxy Nexus using Tapatalk 2
I Am Marino said:
Do you have the setting to kill apps after exiting enabled in Developers Settings?
Turn that off if it's on.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No I don't and I have the "background process limit" to standard limit. What is the standard limit?
I have to agree with the OP. On my SGS2 i9100, apps stay alive much longer in the background buttons on the GNex they have to reload even if it's the 3rd apply on hold.
But then again the I9100 had 835mb free ram and the GNex only has 695mb free ram.
Sent from my Galaxy Nexus using Tapatalk 2
Where's all of our ram being allocated to? GPU? It was like that on my Droid X2, was so annoying that the original Droid X had more free ram than it did
Toroplus
What I find surprising is that any somewhat-experienced developer can tell you that RAM is so important on Android, much more than processing power, yet phones are released QUAD-CORE, which makes no sense. Android is a semi-multitasking operating system, it would benefit more from a really good dual-core rather than an average quad-core processor.
RAM is important, because when you switch applications on Android, your app's are 'hybernated' in memory until they are called back again. It is also possible for developer to hybernate the application better (such as store the state on internal memory), but most applications do not use it.
What this means is that if you have a lot of applications running and some applications 'ping' in your background frequently, then you will have very little RAM available on your phone. So when new application is run, the old hybernated ones are killed off.
Where does this take us?
It takes us back to 2010 when released phones had very little internal memory. Applications were growing in size and functionality back then, but most could not be moved to SD card and some parts of the application stayed on internal memory anyway. This meant that after a while, you really could not install all the apps you found useful because you kept running out of internal memory.
This is similar to 2012, where most phones have just 1GB of RAM and only very few new phones have realized this as a problem and have upgraded to 2GB. It is similar because again, apps grow in size and functionality and require more RAM. And in time this means that you can only have very few applications running at the same time without being killed off. Right now, if you happen to run a game like Shadowgun, be prepared to have most of your background apps killed off the moment you start the game.
On the 1GB version of Galaxy S3 that was released in EU there are even problems where the launcher itself is killed off because applications require RAM.
So it's similar in that in a years time, 1GB of RAM will be a real nuisance on the phone because it almost entirely kills off multitasking capability of the phone.
Developers know it, yet marketers and people who 'make the decisions' do not seem to care. They can advertise better processor much more efficiently than more RAM, since people can notice speed, but rarely notice RAM. Most people don't even know that their phone could work better if it had more RAM.
Jesus, I hope you didn't type all that from a phone!
Sent from my Galaxy Nexus using xda premium
Yeah I observe what OP is encountering..
On my SGS2, app tends to stay alive in background than nexus.... not sure why. probably because of HD display.?
IMO, I've played with my friends' iphone, iphone does it somewhat better, frozen app resume very quick..
nonione said:
you prolly got too many stuff running in the background at all time thats eating up your RAM
cant blame you seems like a gig of RAM isnt enough anymore
Click to expand...
Click to collapse
You don't have a gig of ram, you have less
Sent from my Jelly Beaned GNexus
I have found that on all my phones, the stock browser and dolphin browser will get killed and force me to reload. But the chrome browser doesn't appear to do this.
Jubomime said:
Jesus, I hope you didn't type all that from a phone!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Made me LOL
Sent from my Galaxy Nexus using xda premium
What I've found is that, on JB, clicking back on an app until you get out will bring you to the home screen instead of the application you were using before opening the last one.
Pretty annoying if you ask me! Anyone knows how to change this behavior?
The stock browser behavior is not changed much from ics, though. It often reloads, but I'm not sure it's been killed, it might just be that the page is "expired" in some way.
elban said:
What I've found is that, on JB, clicking back on an app until you get out will bring you to the home screen instead of the application you were using before opening the last one.
Pretty annoying if you ask me! Anyone knows how to change this behavior?
The stock browser behavior is not changed much from ics, though. It often reloads, but I'm not sure it's been killed, it might just be that the page is "expired" in some way.
Click to expand...
Click to collapse
That's what "recents" is for. Why would you press the back button ten times, even if that worked?
Sent from my Galaxy Nexus using xda premium
Jubomime said:
That's what "recents" is for. Why would you press the back button ten times, even if that worked?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The application state wil be different if you change app by history or by hitting back.
I often leave an app by hitting back because I want it to start from the main screen (not where it was) when I get to it (eventually) later.
It's like iconifying a window on a pc and it shows the desktop instead of the underlying window(s): doesn't make sense to me.
And anyway it's been different on all previous android versions (tested from cupcake on )