Whenever I turn on my system and log in from a shutdown/restart, every time I click on Activities it freezes (or rather does nothing) for about 3-6 seconds and then loads up the Overview screen. After this "freeze" every other time I click on Activities, it will load instantly and snap to the Overview screen like it should and that's how I want it to react every time.
After reading this I hope that you will get a better understanding of what activities are and start to think about how you can benefit from them. I will also try to answer the frequently asked question “Why should I use activities instead of virtual desktops?” and explain when I think you should use what.
Hi I'm wondering how Android is managing memory and I can't find precise answer anywhere.
Let's assume I have an application with 5 activities on current activity stack (4 are stopped and 1 is resumed), there is no service connected. I press HOME button so that all of my activities are stopped.
I start some other memory consuming application and overall device memory is starting to be low.
Recently, I wrote a post about the KDE 4.5 SC release candidate. In that post, I was a little bit critical about the discoverability of desktop activities. I wasnt too sure of what the purpose of these were, and there was nothing in the interface for creating these activities that gave the user any hint of what they were.
I am creating an app that will ask questions once a button is pressed; it will determine what activity and layout to take the user to next. I’ve been creating activities for each question that is asked, but am curious about whether too many activities can hurt an app. Does it really matter?