Maybe im expecting too much:
When I press gallery, almost 1/3 of the time only 1 or 2 categories come up and no thumbnails. Then i exit and press again and a few more things show up. Then i exit again and usually the 3rd time or so the app opens properly.
Also, about once every 2 weeks i press an app and it opens a different app. And this happens with multiple apps. The only way to fix it is to reboot.
I dont use a task manager
I reboot the phone every couple of days
I wipe the phone about once every 1 or 2 months
Is one of the above practices ruining my device?
I bought the phone and i havent done anything custom to it. Why does my polished 2.1 firmware work like a 5th grade science experiment?
Have occasionally noticed that the gallery app does not pick up all images and categories... something with the media scanner... try using the media scanner in the dev tools app or unmount and remount ur sd card...
Never had any problems with apps opening wrong apps... this is very strange... I have no idea why this is happening and quite frankly, I can;t think of anything which would serve as a possible solution!
Occasionally I've had the latest picture taken not show up in the gallery, but that's it. Stock O/S is great.
Never had it open the wrong app.
I don't run a task killer, don't reboot & have never wiped.
About the app opening the wrong app thing I guess its good news if I'm the only one. Is it possible that I've downloaded an app that is causing it? Or is it more likely an OS issue? it seems a little cheesy that the phone does this, if I could fix it without rebooting that would be a step in the right direction...
Likely an app you downloaded, or just something a little off about the flashing of your update, or a bad RAM memory block at the wrong place.
As for the gallery, I thought I had that issue a bit too, but I noticed that more than anything it just takes a really long time to open fully if it has been kicked out of the cache.
As for the original question posed in the thread title, Android is still Beta in a lot of ways. 2.0/1 is a huge change in many ways from 1.6. It sounds like 2.2 is going to be a bit of a change as well, but instead of changing nearly everything, it is going to build of 2.0/1 plus add in some changes. I am willing to bet that until the release after Gingerbread (the OS after 2.2, aka FroYo), not sure what the "H" release will be codenamed will we see an OS that isn't "Beta" in enough ways for me to call it non-Beta personally... then again, so far Android is less buggy than windows mobile, better than Blackberry even, and on par with iPhone OS, if not better in these regards.
Just like an OS for a computer, same holds true for a smartphone, there are going to be bugs, there are going to be bad programs/apps, and so forth.
I think you should wait for FroYo, if Android still doesn't meet your standards, root and flash some of the custom ROMs. Enom is very stock like, but fixes many of the little bugs, as does Cyan, although with Cyan you do get a few more bugs in some of the development apps and what not.
Just a thought, but maybe you're suffering from the occasional wacky touchscreen issue?
So it's not that it's just opening the wrong app, but the screen is registering a touch in a different place, it's usually most noticable when typing. If it is that, then a simple lock/unlock will solve it, no need for a reboot.
Why do several apps randomly start up?
It feels like I constantly have to open task killer and kill over a dozen apps even when my phone hasn't been touched since the last time I killed almost the exact same list of apps.
Att Navigator, stocks, countdown, etc. seem to be the regular culprits. Any help with this situation would be awesome.
I've noticed the same thing on my Aria. AT&T Navigator always restarts by itself and I've never even used it. So I just set ATK to auto kill.
Look at the sync settings and you can disable things you dont need (News, stocks etc)
A "Running" app behaves differently on android. The app may be "Running" but it is also "Sleeping" which means that it may not be using any resources (battery, cpu, etc).
Using a task killer may actually be hurting your performance and battery life.
http://androidspin.com/2010/05/25/why-you-dont-need-a-task-killer-app-with-android/
I just check the running apps on my Aria and I understand why every single one is running. AT&T Nav is NOT running. You should check all the widgets you are using, having the widget on the home screen start app automatically.
If you're rooted....
I can't tell you why it does it, but I can tell you how to stop it. If you're rooted, spend the $.89 (approx.) for Autostarts. One of the best programs I've installed.
I was having the same issue, I use AT&T Nav, but it always seemed to show up on the task list even when I hadn't started it. For whatever reason, it's set to start whenever you get a text message! With Autostarts I was able to stop it (along with many other things).
Best of luck to you!
armyengineer51 said:
I can't tell you why it does it, but I can tell you how to stop it. If you're rooted, spend the $.89 (approx.) for Autostarts. One of the best programs I've installed.
I was having the same issue, I use AT&T Nav, but it always seemed to show up on the task list even when I hadn't started it. For whatever reason, it's set to start whenever you get a text message! With Autostarts I was able to stop it (along with many other things).
Best of luck to you!
Click to expand...
Click to collapse
One caveat to this, BE CAREFUL. This is a powerful program and it will let you stop just about any service/program on your phone. You could really do some damage if you don't watch it.
This has been pissing me off for quite some time. I hear Android's RAM is managed internally and that there's nothing to worry about - task killers are redundant.
I understand the logic, I understand the reasoning.
It just won't receive any of my understanding because this is frankly wasting too much time in the course of a day.
What happens due to this "internal management" is that programs I want to keep alive and return to in the state I left them isn't happening. Let's take Aldiko (or we could say the browser, pdf reader, music player, take your pick), the ebook reader; it can take up to 30 seconds to load a book, uses a lot of RAM, and opens at the page I was at.
Now imagine that I'm getting a phonecall, or an SMS, maybe even need to check the mail, or the bus-times, perhaps needing to use the browser. The RAM dips below the line and Android kills a process. 3 guesses to which process it killed to free RAM? You got it, Aldiko. The one that it took me 30 seconds to open. The one I was using, the one I actually cared about.
Checking the list of programs running I see that Aldiko's there, just not with an open book. What I also see is 987645984549 programs that I don't use, never activate, and serves absolutely no purpose on the phone, waiting for me to start them again for the second time in the phone's lifetime (which isn't happening). They're hogging RAM for some godforsaken reason, still sitting there doing nothing, not being used. Yet it killed Aldiko. Or any of the other processes I actually need, want and use.
Why does Android behave so ridiculously? How can I fix this? Installing a task killer helped somewhat, it keeps the stupid programs off so it doesn't close the ones I need all the time, yet the more frequently I run it (increasing the uptime for Aldiko), the harder it is on the battery because the programs keep popping up. Despite never being used.
Or maybe I want to use them at some point in the future, but not all the time. Not more than once a week. It doesn't matter. They shouldn't be allowed to interfere with the programs I actually use.
Is there some way for the android management to be a little less random, and a bit more like Windows Mobile, where a program stayed on as long as I wanted it to (unless there was a crash...)?
You could use Swap memory, if you REALLY want to fiddle (like what Windows/Linux/OSX does), and maybe tweak configs. It might be just possible to "swapon"
But the reason it's done is to provide quicker performance. Aldiko SHOULD be coded to remember the last book anyway, and does it REALLY take 30secs to open? That sounds like bull to me (I just tried it, and it took maybe 5 secs). Granted Aldiko could open the last book being read by default, but you could contact the aldiko developers for a setting to do that.
Either way, swap memory would be a prereq to doing this, because if you don't have enough RAM, apps will crash. So try that first
Hehe, yeah, it does take 30 secs. Maybe a big book or something. It was just an example. There's also the browser losing the pages it was on, music player losing place where played, pdf reader, and so on.
I'll check out out, but I'm not keen on rooting though.
Thanks for replying
Sent from my GT-I9000 using XDA App
Well i searched around XDA a bit and found many threads related to this bt all for WM and not android.
Multi-tasking is getting a bit tough. Apps get auto-closed after sometime.
Samsung Galaxy SL i9003
Stock firmware and everything stock, nothing chngd much. Only apps installed from the Market.
Say m surfing the opera, and even if a small app like messaging is open and aftr some roaming around when i return of opera, it has closed.
PS - Above is jus an example so dnt claim Opera is a power-hogger so it wil b to open up ram for other apps and all......
So any way of disabling the auto-closure of apps?
Love XDA
@ mod who moved it...
Its related to i9003 nt i9000.
Anyways tnx for moving. Wil get more views here....
Any dev der? Help!
Sent from my GT-I9003 using XDA App
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Exactly.
There's an app on the market, Spare Parts, in it ders a option on hw android handles suc apps.
There r two options. Normal and aggressive. Keep it normal and try and c if it helps.
paleozord said:
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Exactly.
I hv migrated frm Symbian, and m a hard multi-tasker, and disappointd with Android jus cos of tis...
paleozord said:
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Is this the reason why I have to constantly log back into Evernote, and Tweetdeck every time i wanna have a look at them?
The whole concept of syncing periodically doesn't work anymore because they are constantly logging out on me.
Unfortunately neither Spare Parts nor any such custom tweaking app seems have any effect on this berhaviour under Froyo or Gingerbread. And yes, the system auto-close is the reason that re-logging into connectivity apps every time you open them is necessary. Since they have been shut down and are no longer running, you are essentially re-launcing them anew each and every time. Hardly ideal.
Previous "old school" smartphone platforms like Symbian and Windows Mobile 5/6 had multi-tasking incorporated into their basic functionality. It's really a shame that shiny new operating systems like Android/iPhone make it such a struggle. Up until and including Eclair (2.1) leaving apps open in the background was completely possible, but as of the present moment WebOS is the only "new age" smartphone OS that still allows it, and unfortunately it hasn't moved along in other development areas very quickly at all.
I wonder y others @xda & @google dnt feel tis....
paleozord said:
Unfortunately neither Spare Parts nor any such custom tweaking app seems have any effect on this berhaviour under Froyo or Gingerbread. And yes, the system auto-close is the reason that re-logging into connectivity apps every time you open them is necessary. Since they have been shut down and are no longer running, you are essentially re-launcing them anew each and every time. Hardly ideal.
Previous "old school" smartphone platforms like Symbian and Windows Mobile 5/6 had multi-tasking incorporated into their basic functionality. It's really a shame that shiny new operating systems like Android/iPhone make it such a struggle. Up until and including Eclair (2.1) leaving apps open in the background was completely possible, but as of the present moment WebOS is the only "new age" smartphone OS that still allows it, and unfortunately it hasn't moved along in other development areas very quickly at all.
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Erm....why do you think people flash custom roms?!
GTi9000 insanitycm010/insaneglitch
slaphead20 said:
Erm....why do you think people flash custom roms?!GTi9000 insanitycm010/insaneglitch
Click to expand...
Click to collapse
Custom ROMs do not change or affect this system auto-close functionality in any way. At least I've never seen any that did so successfully. It seems to be coded too deeply into the OS to be changed, from what I can tell. That is, I'm sure theoretically it *could* be changed, but most custom roms I've seen tackle far more surface-level interface issues and not the way the kernel manages processes in the background.
I didn't realise this happened after 2.1... I already was thinking why all apps were getting closed so fast after I updated my i9000 to froyo and then to 2.3. I just bought i9100 mainly because of the 1gb ram and still, with 400mb free ram, apps getting closed after couple of hours. (Not minutes, or even seconds like i9000, thankgod).
Autokiller lets you manually change some value of a running app, so it won't get killed... unfortunately this isn't automated so it's no use.
The time before auto-closure can sometimes vary from device to device.. I've tested on two Froyo devices other than the Galaxy S, each from different manufacturers as well, and apps rarely make it past ten minutes before being shut down on any of them. I've never seen anything make it a couple of hours so that's a new one.
I've actually gone back to my Motorola Defy running 2.1 for now, specifically to be able to multi-task again. Sadly there is a 2.2 update available over-the-air for it, but I keep declining because I just don't want to lose the ability to multi-task. Unless some future version like Ice Cream Sandwich restores control to the user, Eclair may very well be the last edition of Android I ever use.
Or should I say AndroIPhone, since that is what it has become.
Eclair actually allows u to multi-task normally?
No issues lik froyo?
Working lik "old-school" OSes's multi tasking?
paleozord said:
The time before auto-closure can sometimes vary from device to device.. I've tested on two Froyo devices other than the Galaxy S, each from different manufacturers as well, and apps rarely make it past ten minutes before being shut down on any of them. I've never seen anything make it a couple of hours so that's a new one.
I've actually gone back to my Motorola Defy running 2.1 for now, specifically to be able to multi-task again. Sadly there is a 2.2 update available over-the-air for it, but I keep declining because I just don't want to lose the ability to multi-task. Unless some future version like Ice Cream Sandwich restores control to the user, Eclair may very well be the last edition of Android I ever use.
Or should I say AndroIPhone, since that is what it has become.
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
ggclanlord said:
Eclair actually allows u to multi-task normally?
No issues lik froyo?
Working lik "old-school" OSes's multi tasking?
Click to expand...
Click to collapse
Correct, applications are left open and running in the background indefinitely until the user chooses to close them. Using a good multitasking app like TaskSwitcher or Smart Taskbar you can switch back and forth between open apps as much and as often as you like, or go away for hours without anything ever closing on you. I'm doing it presently on my Defy with no issues at all, just like older operating systems allow(ed).
Tats really Awesome!
paleozord said:
Correct, applications are left open and running in the background indefinitely until the user chooses to close them. Using a good multitasking app like TaskSwitcher or Smart Taskbar you can switch back and forth between open apps as much and as often as you like, or go away for hours without anything ever closing on you. I'm doing it presently on my Defy with no issues at all, just like older operating systems allow(ed).
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
ggclanlord said:
Tats really Awesome!
Click to expand...
Click to collapse
It's certainly a saving grace for Android that Eclair devices still provide multi-tasking functionality for those who insist upon it, though at the same time it sucks to see all these super powerful, souped up Froyo and Gingerbread devices being released monthly and having to snub them because of the deficiency in the newer OS.
Please, please fix this in Ice Cream Sandwich or Chocolate Souffle or Lemon Tart or whatever desserty moniker the 2.4 flavour of Android takes on. Or at the very least give the user the option to select an operational mode (auto-close or manual manage) just like many devices offer for battery management, with performance mode versus smart-saver mode etc..
It's hardly a smart phone without multi-tasking!!
I guess so it'd b more effective if tis is wrttn to Google...
paleozord said:
It's certainly a saving grace for Android that Eclair devices still provide multi-tasking functionality for those who insist upon it, though at the same time it sucks to see all these super powerful, souped up Froyo and Gingerbread devices being released monthly and having to snub them because of the deficiency in the newer OS.
Please, please fix this in Ice Cream Sandwich or Chocolate Souffle or Lemon Tart or whatever desserty moniker the 2.4 flavour of Android takes on. Or at the very least give the user the option to select an operational mode (auto-close or manual manage) just like many devices offer for battery management, with performance mode versus smart-saver mode etc..
It's hardly a smart phone without multi-tasking!!
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Cn any1 tel me whthr tis issue is der @GB o nt?
M on Froyo cos GB nt yet released for my device (only a Dev update yet)
I can't say with 100% certainty but I'm reasonably confident it's the same under Gingerbread (2.3). Google considers this "feature" of the Android operating system to be a significant improvement and benefit, so they're not likely to remove it on their own anytime soon unless they get a massive influx of complaints about it.
The best we can hope for is probably a user-controllable setting of some sort that determines the degree of system aggressiveness in auto-closing background applications. There are already plenty of third party root-based utilities available in the market with similar settings, but they only affect their OWN auto-closing tendencies and do not override the system itself's default auto-close behaviour. I know this because I have tried them all at the lowest possible setting levels, and everything still gets closed in the background just the same.
I have hunted for details of the new XXLT9 update and can find virtually nothing. We have 2 notes running LSO/LSZ very well indeed with good battery life and little lag and wonder what the total benefits/losses are of the new update. If it helps any one. I put our good battery life down to this, (phones have never been rooted by the way.) disable all unused/undesired apps.. yahoo etc, but clear each unwanted programs cache and data first then take the green tick out and only then disable. Even all the other programs you use take the green ticks out except chaton / messages /email and any other necessary priority app, I mean literally go through every app and take out the green tick unless its needed then set email to manual sync unless your a business, set the screen mode to the lowest brightness setting acceptable to you, then put power saving on in the task bar set screen time out to 15 secs unless your doing something special and turn brightness down as low as you find you can.I have just 27 good apps on mine (green ticks are out.). I have mentioned disabling for another reason as well, I noticed with the last maps and the play services updates that you cannot disable them or take the ticks out and I'll be surprised if I'm the only one out of millions who disables these, I mean why if you you use maps once or nonce a day should you leave it spying on you and using your data all day reporting back to google and taking up ram but I'm thinking the new update XXLT9 will have all the latest google versions baked in so people can't uninstall the updates back to the version they can disable, if this turns out to be the only reason ,thinly veiled by some little unworthy treat I'll stay put, but if theres any good new features/benefits it would be good if some one could share.
Thank you.