The ActionBar will use the android:logo attribute of your manifest, if one is provided. That lets you use separate drawable resources for the icon (Launcher) and the logo (ActionBar, among other things).
How about a workaround.. Write a second app that implements the home screen, when the home screen button is pressed this app will come to the foreground. From this app you then need to push your main app back to the foreground. The only catch is that your Home screen app must never need an … Read more
To answer one of your questions, the Dalvik VM indeed does use a tracing garbage collector, using a Mark and Sweep approach. According to The Dalvik Virtual Machine Architecture: The current strategy in the Dalvik garbage collector is to keep mark bits, or the bits that indicate that a particular object is “reachable” and therefore … Read more
if both activities are yours, use a decent data model. Android doesn’t encourage that much to very well designed application. Or turn it differently, it allows for fast developped application and doesn’t promote much of good software application principle. The solution of @Jean-Philippe Roy (québec ?) is interesting but singleton are quite an anti-pattern when … Read more
None of standard Activity Lifecycle methods is called when “Recent Apps” button pressed. Activity will stay active after list of recent apps popups. Through semi-transparent left part of this list you can even observe application animation is still running, if you running a game with some animation that didn’t handle this situation properly. Actually many … Read more
This is the style used for any ActionMode, I pulled it from the SDK. You’ll need to create your own style to customize it. It’s really easy to do. If you’ve never done anything like this before, you should read through this post on customizing the ActionBar. It explains everything you’ll need to know. <style … Read more
If you want your activity to be fullscreen but still show an actionbar, but with an alpha you have to request overlaymode for the actionbar in onCreate() of your activity: getWindow().requestFeature(Window.FEATURE_ACTION_BAR_OVERLAY); //getWindow().requestFeature(WindowCompat.FEATURE_ACTION_BAR_OVERLAY); << Use this for API 7+ (v7 support library) Then after you call setContentView(..) (since setContentView(..) also initializes the actionbar next to setting … Read more
Selvin already posted the right answer. Here, the solution in pretty code: public class ServicesViewActivity extends Activity { @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); // etc… getActionBar().setDisplayHomeAsUpEnabled(true); } @Override public boolean onOptionsItemSelected(MenuItem item) { switch (item.getItemId()) { case android.R.id.home: NavUtils.navigateUpFromSameTask(this); return true; default: return super.onOptionsItemSelected(item); } } } The function NavUtils.navigateUpFromSameTask(this) requires you to … Read more
In the end my workaround was to execute remove() of the previous fragment and add() the new one. Although that’s what replace() method was meant to do. But I am still guessing why replace() method didn’t work properly in this case. It is really weird and I want to discard that it is because I … Read more
Drawable d=getResources().getDrawable(R.drawable.background_image_name); getActionBar().setBackgroundDrawable(d); The above code sets the background image for the action bar. Hope it helps.