Related
So the cdma hero is a slug. Don't try and tell me otherwise unless you've used something as fast as an iphone 3gs, blackberry, etc. And if you're saying it's great but comparing it to something other than 1.5 htc sense ui then that can't help either.
How much improvement does a clean rom on a rooted phone give? (basically just nixing sense ui alltogether)
Vanilla android should help speed things up significangtly, however I'd try some other things before doing that. I just recently installed a compressed Rosie, removed all the applications and widgets that I don't use and disabled a bunch of start up items, now the whole thing is quicker it seems.
Just wanted to ask why it is that the 2.1 roms out there don't have the new launcher or gallery apps?
For me the most exciting thing about 2.1 is the new launcher but every 2.1 rom I have tried still has the old pull-up tray. I was under the impression that the main things that made 2.1 visually different to 2.0 were the new launcher and gallery?
You have to remember that the developers are trying to "port" this stuff over from the Nexus One... a new phone with a 1ghz processor and more RAM than that of our G1s and MT3Gs...
That new Nexus ONE also has 3D hardware acceleration. This is the primary reason why the gallery and app menus from 2.1 "Eclair" work well on it and not our phones.
Have patience; we'll get them soon, but it will take time to get it working.
Thanks for the response rbrainard.
I get that it probably won't run very well on our older tech. But I just found it weird that it wasn't included in at least some of the roms just as a proof of concept type thing?
Or, is it just that those two particular apps won't run on our phones yet? Constant FC's or something?
It's more or less a "backporting" issue...
Like taking a sweet looking Windows Vista Aero theme and getting it to work on Windows 2000... ??? If that's a good analogy?
The way those softwares are currently developed is specifically for they hardware intended... As we have different hardware... a software revamp is required.
This rom has them, as well as live wallpapers, in the beta version. I've only used the basic rom though, so I can't comment on how it works.
Yeah i saw that one, really impressive that they've managed to get it to work so far! I guess now we just need to wait until someone manages to resize and optimize the App to work on our smaller screens / processors.
I have been rooted for almost as long as I've owned my phone. I have tried each flavor and version of CM, htcclay, super (insert letter), kang, dwang,... the list goes on. Most of the time, each ROM runs super smooth when first installed. I load up my most used apps, from either the market, mybackup, or titanium, but usually the market. I do not have an extensive list of apps I use. Mostly stuff for work. No games or junk. The system continues to work relatively well for a day or so. Over time, it slows down drasticly. I have tried each recommended launcher: stock, adw, launcherpro, launcher42, etc. The forcecloses become more common and the lag between app to homescreen continues to get worse.
My question, I guess is, is this just a G1 thing? Do you all experience this? Is there a cache that keeps building up with junk? Is there a hidden process that is eating up resources?
I have used cache cleaner, shutting down apps, etc. I haven't been able to find a single culprit to the lag, etc. It seems just to be a G1 thing. I know the device is low-powered, etc. But does everyone run into this?
Sent from my CM6 BBQ powered G1 using XDA App
I am with ya. Yes it does this. Killing Cache and running processes helps. I've noticed running swap and jit. Definitly overclocking cpu helps. But yeah without all these wed be up ****s creek without a paddle I think. Especially with these big new roms these days. There trying to squeeze on are outdated original gangsters of android
sent from my superfroyo dream
Im on got 2.2 but this happened to me with 2.1 too, is really annoying, multitasking is not executed well, my programs keep closing :/ 70-80% of the times i press the home button while im playing music+using the browser+using trillian or behive launcher pro loads the whole homescreen and widgets :/ , if switch to the browser, it reloads the websites or loads the homepage , am i doing something wrong?
i tought 256 mb wasnt that horrible for a smartphone
i blame android.
i was ok with my phone til the last week. i got an ipod touch 4g. 256mb only on that one and people complained it was a neutered iphone but damn it smokes my milestone in day to day tasks. granted it can't make a call, but im pretty pissed that android still lacks the optimization we need.
Chad_Petree said:
Im on got 2.2 but this happened to me with 2.1 too, is really annoying, multitasking is not executed well, my programs keep closing :/ 70-80% of the times i press the home button while im playing music+using the browser+using trillian or behive launcher pro loads the whole homescreen and widgets :/ , if switch to the browser, it reloads the websites or loads the homepage , am i doing something wrong?
i tought 256 mb wasnt that horrible for a smartphone
Click to expand...
Click to collapse
Same thing happened to me on 2.2 but on 2.1 it runs very smooth... Try "Keep in memory" setting from Launcher Pro --> Preferences
is there any method to optimize the ram usage of android. i thought that a milestone is better then iphone, i still think it is,but if the android system dont get better, iphone will smoke all of us in the pipe.
the first thing i noticed when i holded my milestone in my hands was, damn is it fast and brilliant, better then the iphone, the same day i started modding and overclocking and things like that. i gave him a little too much vsel, .... and since then i think it has gotten slower :/ , maybe some of you had the same expirience
Guys, please consider the fact, that google has to optimize their OS for different smartphone setups from different manufacturers ... the iOS featured in the iPhone and iPod Touch has been completely optimized on their hardware, since iOS isnt featured outside the apple family of handhelds. Because of this, the optimisation and integration is WAY more comfortable, Google has a ****load of work to do to consider the many different phones besides their nexus one.
give it time guys. MIUI handles the memory management already pretty good, runs way more responsive that stock android.
It's problem of the apps and widget you are using, download a app call system pannel, you will find out many apps and widget take up so many ram.
and 2.2 got leak have a problem which make the launcher redraw so often.
for launcher pro, there is an options to keep it in memory.
vladstercr said:
Same thing happened to me on 2.2 but on 2.1 it runs very smooth... Try "Keep in memory" setting from Launcher Pro --> Preferences
Click to expand...
Click to collapse
i just checked that option, it says its experimental tough , theres a couple of exta ptins:
memory usage preset: high,mediu,moderate,low...
homescreen cache type: normal compressed,light
Should i mess with this setings too?
Try4Ce said:
Guys, please consider the fact, that google has to optimize their OS for different smartphone setups from different manufacturers ... the iOS featured in the iPhone and iPod Touch has been completely optimized on their hardware, since iOS isnt featured outside the apple family of handhelds. Because of this, the optimisation and integration is WAY more comfortable, Google has a ****load of work to do to consider the many different phones besides their nexus one.
give it time guys. MIUI handles the memory management already pretty good, runs way more responsive that stock android.
Click to expand...
Click to collapse
piss poor excuse. there's not much rocket science going into optimizing a homescreen smoothness.
The A4 chip the iPhone 4 uses is more similar to a Samsung Hummingbird.
The OMAP chip the 3GS uses is similar to the one we have in the Droid/Milestone.
The old ARM11 chips in the 2G/3G/iPod Touch 1g/2G/3g 8gb is different too.
The fact is Apple has accounted for 3 types of CPUs and while they are all ARM architecture, it's similar to the fact we have Qualcomm, TI, and Samsung CPUs floating around. Even Google's own Nexus One is piss poor smooth on the homescreen.
Granted here at XDA we've already ROMed the hell out of our phones, but the fact that I'm still ashamed when I whip out my Milestone just to show my friends Facebook, and they ALWAYS comment on how choppy it is despite my 1100mhz overclock or whatever. I'll even reboot just before hanging out with them just in case I need to do some stuff. Android is just too freaking slow.
i am using cronos froyo 1.5 and i must say i am suprised, it is a good rom, fast and stabil,and trust me i testes many roms, maybe all?
so is there a way of modifing a rom (maybe cronos) to get rid of all the services that are not needed for a normal user? maybe it would be more ram available this way... aint it?
I think that 256 mb ram are enough. Try eclair mod v0.3b. It is very fast and i get about 110mb free ram. I use Advanced task killer and Estrong task manager. I have them both on my homescreen and when i tap them both I get 110mb ram free.
ram
the task killer is an option i dont want to use, because android should manage that him self, but maybe tere are some services that are not needed, so we can delete them, and make a slim rom. do someone know what services are not needed, and how we can wipe them?
Granted here at XDA we've already ROMed the hell out of our phones, but the fact that I'm still ashamed when I whip out my Milestone just to show my friends Facebook, and they ALWAYS comment on how choppy it is despite my 1100mhz overclock or whatever. I'll even reboot just before hanging out with them just in case I need to do some stuff. Android is just too freaking slow.
Click to expand...
Click to collapse
Ha ha I have to do that exact same thing, so embarrassing as it always happens just after I've sung praises for Android!
Yriel40k said:
I think that 256 mb ram are enough. Try eclair mod v0.3b. It is very fast and i get about 110mb free ram. I use Advanced task killer and Estrong task manager. I have them both on my homescreen and when i tap them both I get 110mb ram free.
Click to expand...
Click to collapse
On milestone? Don't believe it. Pleas post some screenshots so I can be amazed
As Milestone has really terrible hardware spec (cpu, ram, flash) I am still hoping someone would start to build ultra-lite version of the android without any non-essential services running, applications on flash, launchers, wallpapers, etc.
Regarding the multitasking - yes when I try to open second app I am holding my breath whether the first one will get killed or will survive
IMO it was depend on which rom u were used.
Try live home for launcher its pretty fast and handles multitasking
Sent from my Milestone using XDA App
Do you use any weather and clock widgets-if yes there is a option called refresh when home is pressed you disable it and your screen would come alive much faster.
Sent from my Milestone using XDA App
I have never be success on milestone, always restarting
I would say it probably more have to do with Motorola for not taking the effort to optimize Android's software for the Milestone, my friend X8 is smoother than mine despite having only 168MB(!) of RAM and he used live wallpapers too. 2.2 also for some reason seems to be very sluggish as compared to 2.1/2.3
Anyway I also believe that because of our higher resolution screen (854 x 480), more RAM is needed as more resource is needed for greater resolution and phones usually reserved more RAM (slightly) for connectivity purposes (cell tower) which lead to a "shortage" of free RAM on our milestone.
Though no doubt, I would say iOS have a slightly better memory management than Android but Android is not that bad given that the Nexus One prior to 2.2/2.3, the amount of RAM available for them is 40mb less than Milestone due to a bug but it still flies. Shows alot that effort to optimize by the OEMs matter more rather than Android itself.
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.