anyone else have this where every so often, maybe 1 out of 10 times, when i hit home from an app or something, i get the MyTouch logo for like 2 seconds and then a little notification box that says Loading... for probably 3 or 4 seconds, before the home screen comes up? just thought it was weird since most of the time it doesn't have to load to get to the home screen.
thanks
I use to get that all the time, when i changed my launcher it stopped doing that, this makes me believe that its a bug
Sent from my myTouch_4G_Slide using Tapatalk
Do you use a task killer?
If so that's why.
This is caused by Android not being ready to show your homescreen, so either you were using a very resource intensive app, have a couple resource heavy apps running, an app is coded poorly, or you are using a task killer and screwed up the data for some of your apps.
What version of what are you running? That may help pinpoint your problem.
Sent from my Bulletproof_Doubleshot using xda premium
no task killers, i hate those, they do more harm than good although the phone comes with a task killer of its own in the quick settings i dont use it. i dont really put apps in the background, im always trying to save memory when i can so i completely close every app when im finish with it mostly happens when exiting from dolphin hd. Also all my apps are on the latest version and so is my os.
my old g2 couldn't survive without a taskkillers. not gonna get into the whole taskkiller vs no taskkiller debate. i've read all the articles and it simply wasn't true for me. they helped alot.
that being said though i have no taskkiller. and i'm not using any custom launcher and i'm not rooted. just using a stock mytouch4g. i have a few widgets loaded of course. like 5 i think total, most of which are stock sense widgets (the clock/weather one, the photo gallery one).
Related
With Touchwiz everything was great, but I wanted to try something new with some more flexibility.
I downloaded and installed it. It seems ok but...
Everything is so slow, it takes 10 secs for a program to open up. Never had this kind of lag before.
Is this normal? Did I do something wrong?
Mine runs super smooth. Make sure nothing is running in the background that you don't want running.
I was already rooted. I killed a lot of the junk. I also had nothing running in the background.
badbeats said:
I was already rooted. I killed a lot of the junk. I also had nothing running in the background.
Click to expand...
Click to collapse
Hopefully you're not using task killers. They're bad for android.
sent from my pimp hero running Froyo CM6 and the XDA app
No I am not using any task killers. I only you the stock task manger.
Load of rubush all system say you dont need task manager etc but lets face it its a load of crap i have been using a takman on my pulse for months and months i have never had any problems due to taskmanagers i had lots of slow downs before i used a taskmanager.
is there any honeycomb friendly task manager or stock tracking Widgets?
I like to put them on the home screen but the ones I found are quite small for use on tablets.
I have never used a stock widget. As for the task manager, you don't need one. Android manages task on its own. If you happen to get a stuck app, go to settings, apps, manage apps, then find the app and stop it.
bwcorvus said:
I have never used a stock widget. As for the task manager, you don't need one. Android manages task on its own. If you happen to get a stuck app, go to settings, apps, manage apps, then find the app and stop it.
Click to expand...
Click to collapse
I know that's the argument about android task manage in a perfect world.
However, in actual usage I get STUCKED apps all the time. For example, if I don't disconnect from team viewer before jumping to another it gets stuck... This make it very cumbersome to go to settings app all the time.
I really need something on the home screen to kill these sticker apps.
Lolento said:
I know that's the argument about android task manage in a perfect world.
However, in actual usage I get STUCKED apps all the time. For example, if I don't disconnect from team viewer before jumping to another it gets stuck... This make it very cumbersome to go to settings app all the time.
I really need something on the home screen to kill these sticker apps.
Click to expand...
Click to collapse
Use Active Apps. It doesn't manage or autokill, just a widget that gives you a list of running apps and lets you close one or all with a single button. Very easy.
As for a stock ticker widget....I would love to find one too. Can't imagine there isn't one out there somewhere.
Sent from my GT-I9000 using XDA Premium App
so i'm using an advance task killer (blue icon) and whenever i end all open apps
it tells me "advanced task killer ended "x" apps" but all the apps remain open in the recent app window in their current state..
is there an alternative way to remove the apps from the recent menu all at once?
i'm new to honeycomb..
Get rid of the Task killer imo
baseballfanz said:
Get rid of the Task killer imo
Click to expand...
Click to collapse
okay so what would an alternative way to quit apps to save battery life?
avpmusic said:
okay so what would an alternative way to quit apps to save battery life?
Click to expand...
Click to collapse
I use Active Apps & Watchdog to kill apps. Both in the market.
It's a Recent Apps list. Not a running in the background list.
All Android since 1.0 (T-Mobile G1, the first Android phone), there's been a recent app list. You press and hold the Home button. On Android 3.0 for tablets, there is a dedicated button.
In Android 3.1, the recent app list has been extended to more than 5 shown. It's now 14/15
You don't need to manually quit apps on Android. I get 15-20 hours battery with heavy use.
Hakizi said:
You don't need to manually quit apps on Android. I get 15-20 hours battery with heavy use.
Click to expand...
Click to collapse
How in the world do you get that much usage....is the screen on 1% brightness and radio off?...
life64x said:
How in the world do you get that much usage....is the screen on 1% brightness and radio off?...
Click to expand...
Click to collapse
I just leave the screen on auto brightness. The battery on these things is excellent.
I am new to not just Honeycomb but android all together. I think that it is completely asinine that there isn't an easy way to stop/close apps. when you bring up the recent app list if you tap & hold you should be given the option to close that app/window.
jadesse said:
I am new to not just Honeycomb but android all together. I think that it is completely asinine that there isn't an easy way to stop/close apps. when you bring up the recent app list if you tap & hold you should be given the option to close that app/window.
Click to expand...
Click to collapse
+1 for this
avpmusic said:
okay so what would an alternative way to quit apps to save battery life?
Click to expand...
Click to collapse
An "app" called Android. Honeycomb caches and/or kills apps on its own. Try it without the killer. Start angry birds, exit and then go back....
So what is a GOOD and FUNCTIONING Task Manager app for the HoneyComb platform? I am using ZDBOX for my Thunderbolt, but it is NOT compatible with HoneyComb.
I use Task Manager to monitor which apps is USING too much battery, not killing them. It's must faster to use this type of app than going to Settings -> Applications and wait for the apps to be listed.
For example, I use ZDBOX in my Thunderbolt and notice that Skype is running in the background ALL THE TIME, using 11 to 25 Mb even when I am not using it for the whole day. Battery life begun to suffer, so I uninstall it.
The way android works is that if an app is using a service that needs to be ran in the background, you'll find it in that list in the application menu. Otherwise, it gets cached, so it will restore faster when you you open it again. Plain and simple, if you need to use a task manager for an Android app, it's either a poorly designed app - possibly containing something bad, or you need to shut down all the services the app needs - which should be a rare occasion if it's a worthwhile app.
What are you trying to kill so often?
If it's something that you've told is okay to run in the background, when you kill it, it probably starts up again. Using a task manager to kill these means your phone is constantly starting up and killing a service, which isn't good for battery life.
Sent from my Transformer TF101 using Tapatalk
Hakizi said:
I just leave the screen on auto brightness. The battery on these things is excellent.
Click to expand...
Click to collapse
Must not be playing much flash. That eats it up.
watchdog not only will let you kill apps but tell you if any are overachivers
if things get out of hand press and hold the power button for a clean restart
I think if you go through settings and look for running apps, you can kill them. You app murderer.
franky1029 said:
The way android works is that if an app is using a service that needs to be ran in the background, you'll find it in that list in the application menu. Otherwise, it gets cached, so it will restore faster when you you open it again. Plain and simple, if you need to use a task manager for an Android app, it's either a poorly designed app - possibly containing something bad, or you need to shut down all the services the app needs - which should be a rare occasion if it's a worthwhile app.
What are you trying to kill so often?
If it's something that you've told is okay to run in the background, when you kill it, it probably starts up again. Using a task manager to kill these means your phone is constantly starting up and killing a service, which isn't good for battery life.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
That's why I need a Task Killer: to kill those poor-behaving apps. I don't use the Task Killer very often, though.
For example: I use an app called Flight Track. I don't fly very often, but I do fly more than average (once to twice a month, sometimes none in a month). This app is running in the background ALL the time. But on months I don't fly, I do not need this app to run in the background. So I kill the app and it does NOT start again in the background until I manually start the app.
Is there anything you can do to reduce the lag in getting back to the home screen after closing an application? I've recently upgraded to the CBW 2.2. I've also just loaded adw launcher. It takes 8-10 seconds for the home screen to be functional.
Sent from my XT720 using XDA App
punchback said:
Is there anything you can do to reduce the lag in getting back to the home screen after closing an application? I've recently upgraded to the CBW 2.2. I've also just loaded adw launcher. It takes 8-10 seconds for the home screen to be functional.
Sent from my XT720 using XDA App
Click to expand...
Click to collapse
Wow! 8 seconds is steep. All dexter based froyo's have a few problems. Although I dont use it anymore I remember what id do to tweak the whole ROM.
1) Use launcher pro, its lighter and faster than ADW. I also like its effects. Theres a setting in it called keep in memory which stops the launcher from being killed by android so there are less redraws of your app drawer.
2) CB froyo and dexters have memory management problems and slowly with use the memory goes down significantly. Download an app called Autokiller memory optimizer from the market and set it at the strict preset. It basically modifies androids native memory management and allow more memory to be free.
3) Use milestone overclock and set it to 850 mhz 56 Vsel.
Step 2 and 3 are assuming you are rooted at the moment. These worked for me really well when I used the ROM and I had no problems at all.
I uninstalled adw and things seemed snapper. I also installed the suggested memory manager. I had already been playing around with the milestone overclocker and its set to 850/56. When I run setcpu should it say 850? I have it set to 850max 250min.
Even set this way the lag remains when returning to the home screen.
Sent from my XT720 using XDA App
punchback said:
I uninstalled adw and things seemed snapper. I also installed the suggested memory manager. I had already been playing around with the milestone overclocker and its set to 850/56. When I run setcpu should it say 850? I have it set to 850max 250min.
Even set this way the lag remains when returning to the home screen.
Sent from my XT720 using XDA App
Click to expand...
Click to collapse
Well thats odd, with similar settings id have a very decent experience. One thing though, do you use many widgets on your homescreen? And does this lag occur when you press the home button from within an app or when you close the app. One thing you could try is setting up a swap partion on your sd card. That always speeds everything up. If you dont know how I can direct you to where you can learn how to do that. Also how did you upgrade to 2.2 CB?
hi try the go luncher i think its the best launcher.
Sent from my XT720 using XDA Premium App
It's slow whether I'm switching to home using the home button or escaping there.
If I've set milestone overclock to 850 mhz and vsel to 56 should setcpu show 850? It shows 720.
Sent from my XT720 using XDA App
I'm not going to load any launchers until it's running like it should.
Sent from my XT720 using XDA App
Try installing Autokiller Memory Optimizer from the market and selecting the Optimum memory profile. That used to work for me when I was running that ROM.
I've found lots of launchers to have lots of lag returning to homescreen on both androids I have had and it's a common issue with android launchers. The only launcher I have that doesn't redraw homescreen every time is SPB shell (but it still has to re-load every now and then). You can try using a launcher like Zeam, launcherpro, or golauncher, nemus launcher as those ones didn't redraw as often as others for me. And if the option is available in a launcher (it is in ADW, launcherpro and Go) select "Keep in Memory" and it might help somewhat.
My XT720 has always lagged when returning to the home screen. I only recently loaded a launcher after hearing reverendkjr talk about liking adw. I only kept adw loaded for a day. Its not installed anymore.
I thought upgrading to 2.2 would end the lag but it wasn't to be.
I've loaded autokiller and set it to strict. I still have times when it takes 8 seconds or so for the home screen to be functional. I do have a 4x2 clock / weather widget on the home screen. I've tried with and without that widget and still have bouts of lag. Maybe I'm expecting much.
Sent from my XT720 using XDA App
punchback said:
My XT720 has always lagged when returning to the home screen. I only recently loaded a launcher after hearing reverendkjr talk about liking adw. I only kept adw loaded for a day. Its not installed anymore.
I thought upgrading to 2.2 would end the lag but it wasn't to be.
I've loaded autokiller and set it to strict. I still have times when it takes 8 seconds or so for the home screen to be functional. I do have a 4x2 clock / weather widget on the home screen. I've tried with and without that widget and still have bouts of lag. Maybe I'm expecting much.
Sent from my XT720 using XDA App
Click to expand...
Click to collapse
Yeah, seems a problem with pretty much all launchers. Stock MIUI launcher and SPB Shell have been the only exceptions for me really. Even Zeam has done its reloading often.
punchback said:
My XT720 has always lagged when returning to the home screen. I only recently loaded a launcher after hearing reverendkjr talk about liking adw. I only kept adw loaded for a day. Its not installed anymore.
I thought upgrading to 2.2 would end the lag but it wasn't to be.
I've loaded autokiller and set it to strict. I still have times when it takes 8 seconds or so for the home screen to be functional. I do have a 4x2 clock / weather widget on the home screen. I've tried with and without that widget and still have bouts of lag. Maybe I'm expecting much.
Sent from my XT720 using XDA App
Click to expand...
Click to collapse
Dude, this almost sounds like a hardware issue or something. How's the rest of the phone? Like when you open apps or browse web pages. Honestly i've used every froyo build and ive never had it that bad. Sluggish for me would be a second or two nothing more than that. Like in my previous comment if you're upto it you could try setting up a swap partition as a final test. After that maybe you need to reflash an sbf and go through the upgrade process from scratch. That always fixes things.
sohrab.naushad said:
Sluggish for me would be a second or two nothing more than that.
Click to expand...
Click to collapse
Yeah, when I had reloads it was generally not that long. If I had a lot of widgets out it might take longer to load up but I don't recall it really being 8 seconds or so...
Hey hows spb on miui? I can't seem to find it on market. How do I get it? Is it smooth like go or launcherpro
syrenz said:
Yeah, seems a problem with pretty much all launchers. Stock MIUI launcher and SPB Shell have been the only exceptions for me really. Even Zeam has done its reloading often.
Click to expand...
Click to collapse
Sent from my Milestone XT720 using XDA App
sohrab.naushad said:
Dude, this almost sounds like a hardware issue or something. How's the rest of the phone?
Click to expand...
Click to collapse
I do have some weirdness when the battery goes dead. The phone has problems seeing the sdcard after I charge. That happens occasionally but other than that no major problems.
Sent from my XT720 using XDA App
spectacle said:
Hey hows spb on miui? I can't seem to find it on market. How do I get it? Is it smooth like go or launcherpro
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
SPB is buttery smooth. Amazing launcher - check out reviews for it online (there are a bunch). However, currently it only runs well for me on either MIUI or 2.1 (on Dexter or WanHu ROMs it has issues). And while it doesn't reload every time like other launchers, it does have to load itself up once in a while when things run out of memory (it's pretty memory intensive I think). They really need to provide it with an update already though (more widgets + features + performance improvements should come sometime, but I don't know when...).
For some reason SPB won't show up in the market on MIUI (there were a bunch of missing apps for me). I emailed SPB support about it and they gave me a copy of one from their website to install as an apk and it worked perfectly. I did already own SPB from android market. You can go to their site and buy the apk directly if you want. It is more expensive than most apps, so you may want to wait until they do that long expected update before diving in. Still, it's a fantastic launcher.
Hi guys,
Since the AOSP ICS builds I noticed that when the Phone app is not in memory it opens very slow. The next time you open it is almost instant. I thought that it would be fixed in the OTA, and even if it is a little faster it is still quite frustrating sometimes. Tried many roms/kernels and even if in some configurations it open faster, it is still slow.
Since I dont use the Phone that much, almost every time that I use it it is not in the memory and it is slow. Anyone has an idea to fix it, like a hack to make it persistent in the memory?
Thanks.
Bump. Is there a way to keep it in memory ? Maybe giving it a special permission like the launcher will help. I will take a look...
Sent from my Nexus S using xda premium
This is my only problem with ICS - I've tried a few memory management programs to see if I could keep the dialer, or contacts, persistent in memory, but nothing works. When I launch the dialer, the application 'Contacts' ('com.android.contacts', which seems to be the new ICS 'People' app) is shown as an 'active application' in my 'SystemPanel' app off the Market, and as long as that stays as an active app then the dialer usually re-launches straight away when pressed the next time, sometimes with only a small bit of lag if the screen has been of for a minute or two. When the 'contacts' app is shut down by the system, I guess when you open other apps up that need memory, the dialer lags again.
All the time, the process 'Phone' ('com.android.phone') seem to be sitting there as an 'Internal System Process' and seems to be persistent, but that alone doesn't make the dialer launch quickly, the 'contacts' app needs to be active as well.
My observations, but I am not a techie.
actually i recently read a thread here on XDA that addressed this issue. it involved a command on the terminal that allowed you to prioritize certain apps. too bad i can't seem to find that thread anymore!
found it! it involves using the Renice command. you can run it as an init.d script
or demo it out using the prioritzer apk (http://forum.xda-developers.com/showthread.php?t=1224125) kind thanks to this developer for creating the app. it works great!
all i did, was set the phone and contact app to -20 priority. it loads MUCH faster... try it and report back.
here are more links related to renice
http://forum.xda-developers.com/showthread.php?t=1271637#17746874
http://forum.xda-developers.com/showthread.php?t=1401858
Great, thanks for coming back on this, this sounds interesting - I'm not rooted at the moment, I will look into doing this as I think it would be worth it just to sort out this problem, as well as the other benefits. I will report back with my results!
I decided not to root in order to fix this, I've gone a different way with the dialer - exDialer has a polished looking ICS theme and I installed that to see how it would work, and it works great. It opens up consistently quicker, maybe due to the 'Keep in Memory' option that it has. I haven't had one laggy episode with it yet. Most other third party dialers don't look so good but this has a great ICS look, has smart dial, and a great call history function, and it's free (or you can donate as I did). Worth a look for anyone having similar problems.
I would still go back to the stock dialer if it worked properly, maybe a future update will solve this without having to root.
Hi guys,
an old thread, but i would like to now if there is something new about the "bug" that the Phone app opens slow if it is not in memory.
I'm new to the nexus s and running the newest skank Version.
On my Desire S the phone app opens much faster .
Cheers
EbiEre said:
Hi guys,
an old thread, but i would like to now if there is something new about the "bug" that the Phone app opens slow if it is not in memory.
I'm new to the nexus s and running the newest skank Version.
On my Desire S the phone app opens much faster .
Cheers
Click to expand...
Click to collapse
One thing to keep in mind is that the Desire S has more RAM.
Mine opens up instantly however. Have you rebooted after installing the rom?
I remember on GB it was instant! On ICS it is indeed very slow. Hopefully JB fixes it...
rasengan82 said:
I remember on GB it was instant! On ICS it is indeed very slow. Hopefully JB fixes it...
Click to expand...
Click to collapse
That's funny because mine doesn't even take a second. :silly:
Same here if not in memory, i can easily notice certain lag on ics roms on my phone, when opening certain apps.
Yeah i did.
Hm Sounds like i have to live with it, or does someone have an alternative way to Set the priority for apps. The one mentioned earlier does Not work for me.
Gesendet von meinem Nexus S mit Tapatalk 2
Thanks for the suggestion to try exDialer. The phone lag was really irritating me and this did the trick. With ics dark theme, it's a perfect complement to bugles beast. Hopefully this will be fixed in 4.1, but till then ...
Sent from my Nexus S 4G using xda app-developers app