If somebody has correctly answered your question, please remember to accept an answer and vote them up if you can! Read more at the FAQ
Featured question: what's your favorite game?
vote up 2 vote down
star

Is it me or has anyone noticed this hiccup that happens often on my MyTouch when I run some app and then hit the Home button? I would first see completely black screen then the wallpaper will appear but no shortcuts and then, finally the complete Home. Sometimes it can take what feels as 20-30 sec? I also noticed that using TasKiller seem to make this worst rather than help. Any tricks or suggestions? I don't want to root my phone - I use it for development and I don't want any sort of deviation from the regular user experience

flag

6 Answers

vote up 3 vote down
check

As you may know, Android handsets currently available tend to have limited amount of RAM. With multitasking built into Android, the RAM can get filled up very quickly. When the OS detects that the memory is close to full, it starts automatically killing off background applications to free up more RAM for the currently active app.

That is why often when switching from the Browser and coming back you will see the page refresh. It's actually reloading the Browser application because it's been terminated. Sometimes the home app (Launcher.apk) gets killed off in this process, and that is why you see it start up all over again when you exit a particularly intensive application.

There is very little you can do to help with this situation on a non-rooted phone:

  1. The main advice is to not install too many applications. Since non-rooted phones are limited to using internal memory for applications, the more apps you install - the less memory will be available to the OS for multitasking. This in turn causes background applications to get terminated more frequently. By having fewer apps installed you minimize the need to terminate background apps often.
  2. Clear the caches of Browser, Google Maps, YouTube, and other frequently used apps often. Since caches are stored on the internal memory, the same idea from the above point applies.

Rooted phones have a lot more options:

  1. You can enable Apps-to-SD so that your applications get installed to the SD card's partition and therefore don't use up as much space on the phone's internal memory.
  2. You can enable Swap File or Swap partition to extend the available memory by having the phone keep faster access to the background apps by temporarily moving their memory footprint to the SD card.
  3. You can enable the Compcache module, which basically compresses part of the phone's memory, thus giving you more "virtual" memory in return for slightly heavier CPU usage.
  4. Overclock the CPU. There are apps/widgets available to make the CPU run faster than the stock speed (actually at fully rated speed of the G1/MT3g's CPU, 528 Mhz). It will not help with memory management, but it will at least make apps (re-)load faster.
  5. Finally, there is a hack available here that adds extra 10% to the phone's memory (~10 MB) by reassigning the memory that's normally dedicated to the 3D subsystem. Unless you plan to run some heavy 3D games on your G1/MT3G, this hack has no drawbacks.
link|flag
vote up 2 vote down

I used to experience this a lot with my G1, and it did happen less often after I rooted, but still happened occasionally. It's weird that you said it seems worse with TaskKiller, because I don't think I've seen it happen once since I started using Advanced Task Manager Free. I do kill all tasks at an almost obsessive rate though.

Do you have a lot of widgets on your home screen? I read somewhere that having a lot of apps installed can cause it to hang sometimes. Maybe try uninstalling some you might not need?

link|flag
2 
I'm trying to keep my phone as close to "real user" experience as possible. Do you think an average user will religiously kill tasks and don't pile up applications and widgets? It actually makes me sad to see how everybody advise on limiting your experience as a way of managing the phone. This is what everyone will be accusing Android of (it's slow and unmanageable) if Android engineers will not get better grip on app/services management. I think I need to trade my MT for Droid :) – DroidIn.net Oct 19 at 17:54
1 
Agreed. Google needs to build Apps-to-SD support into Android natively. This alone will resolve 90% of the issues people experience with slowness and reloads. – Chahk Oct 20 at 18:01
vote up 2 vote down

My experience is that it's a lot better when I have fewer widgets, but it's still slow occasionally. I think the G1 is a bit underpowered for Android, and it definitely doesn't have enough RAM. I'm hoping future phones with faster processors will be more responsive.

link|flag
vote up 1 vote down

Is the ram hack recommended with cyan 4.1.9999? Should I use it, I have a mt3g.

link|flag
vote up 1 vote down

So far I experience this on my HTC Magic only when visiting the Google Wave mobile site, but the home screen appearance delay is just a few seconds and not 20-30 like in your case. Given that Wave is a resource intensive site, this seems consistent with Chahk's explanation.

link|flag
vote up 0 vote down

Use spare parts app. Scroll to where it said keep hope app in memory and check the box to enable it

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.