Home/ Questions/Q 7413353
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T06:40:55+00:00

I read http://android-developers.blogspot.com/2012/01/say-goodbye-to-menu-button.html but have some issues. For pre-honeycomb I want a custom title,

  • 0

I read http://android-developers.blogspot.com/2012/01/say-goodbye-to-menu-button.html but have some issues. For pre-honeycomb I want a custom title, for post-honeycomb I want the default. When I try to run my app on ICS

android.util.AndroidRuntimeException: You cannot combine custom titles with other title features

If I remove the custom title it works fine on all releases, just without the custom title.

in values-v11 I have themes.xml file with this content:

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <style name="customTheme" parent="android:Theme.Holo.Light">
    </style>
</resources>

So my theme document says to use no custom theme basically.

If I remove

requestWindowFeature(Window.FEATURE_CUSTOM_TITLE);
getWindow().setFeatureInt(Window.FEATURE_CUSTOM_TITLE, R.layout.title);

then the theme shows up correctly on ICS.

I cannot imagine that I have to check on coding level what API level I run and either request the window feature or not, that should be handled by the system.

Thanks, A.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Pretty similar to this question. I guess the action bar is considered a title feature, so turning it off gets rid of the exception.

    I’m still a bit confused by the question though. You say you want the default title for post-honeycomb, but you can’t use a custom title and also use the default actionbar. If you really want to do what you’re asking (custom title for < 3.0, default actionbar for >= 3.0), then you’ll need to check Build.VERSION.SDK_INT before calling window.requestFeature etc. That’s how it’s done in the actionBarCompat example that does just this sort of thing.

    • 0