<p>Have a question that is not listed on this page? See the "Direct Contact" section of the <ahref="support.html">support page</a>.</p>
<tableid="faq-table">
<tr>
<th>What action bar library is used on pre-3.0 devices?</th>
<td>
<p>The widget is a custom implementation that was purpose-built to mimic the API, functionality, and look of the native action bar on 3.0+ devices.</p>
<p>The basis for the widget was <ahref="https://github.com/johannilsson/android-actionbar/pull/25">work done</a> on Johan Nilsson's <ahref="https://github.com/johannilsson/android-actionbar">Android-ActionBar</a> library. The first two versions of ActionBarSherlock used his library directly for support on pre-3.0 devices and without his work the current version of the library would not be possible.</p>
<td>Both library itself as well as your application must be built using Android 3.2 (API level 13). You may set your <code>targetSdkVersion</code> in the manifest to any API 11 or higher.</td>
<th>Why do I have to build with API level 13?</th>
<td>Building with API level 13 will allow the library to use the native action bar classes so that they will be used when your app is run on devices using Android 3.0+. Since you will be compiling against new APIs but your app will likely be run on devices with older versions of Android extra care must be taken to either avoid using or properly check and call any methods that were introduced after your minimum SDK version.</td>
<th>Why doesn't the logo defined on the activity/application entry in the manifest get displayed?</th>
<td>Despite there being support for loading the logo for activities and applications since API level 9, the underlying implementation in Android is broken and does not work at all. In order to specify a logo on these platforms you should use the <code>abLogo</code> attribute in a <ahref="theming.html">custom theme</a>.</td>
</tr>
<tr>
<th>List and tab navigation hide the title on pre-3.0 devices. Can this be changed?</th>
<td>Due to the relatively small space to display items on phones, this cannot currently be changed. The forthcoming version 4.0 of the library will behave more like the native Ice Cream Sandwich action bar.</td>
<td>This library contains a custom action bar implementation for pre-3.0 devices which relies on styles, themes, layouts, and drawables in order to display properly. Due to the current limitations of Android and <code>.jar</code> files and the Android Developer Tools, it can not be accomplished any other way. This may change with future versions of the tools.</td>
<td>See the <ahref="support.html">support page</a> and create an issue on GitHub, post to the Google Group, or contact me directly. Or do all three! The worst thing you can do is to not report it. Please try to include as much information as possible in your report.</td>
<td>You application or activity is not using a theme from the library. See the "Parent Themes" section of <ahref="theming.html">the theming page</a>.</td>
<th>Do I need to include the <code>.jar</code> file for the Android compatability library when using ActionBarSherlock?</th>
<td>No. ActionBarSherlock is built on top of the Android compatability library and comes bundled with its class files. Including the <code>.jar</code> will result in a very large number of compile-time errors.</td>