Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is most definitely a bug in several members of the Samsung Galaxy series of devices. I managed to replicate it on a Galaxy Pocket but was unable to replicate it on the emulator for an AVD that was small-ldpi Gingerbread.</p> <p>It took a while to reproduce. Occurs when there are more than 6 menu items, so that pressing on the hardware menu button shows 5 items plus the "More" overflow option. Clicking on "More" causes the crash.</p> <p>Trimming the theme down to the following still caused the error.</p> <pre><code>&lt;style name="CustomActionBar"&gt; &lt;!-- No styles --&gt; &lt;/style&gt; &lt;style name="JumbleeTheme" parent="Holo.Theme"&gt; &lt;item name="android:actionBarStyle"&gt;@style/CustomActionBar&lt;/item&gt; &lt;item name="actionBarStyle"&gt;@style/CustomActionBar&lt;/item&gt; &lt;/style&gt; </code></pre> <p>But trimming the Theme down to the following makes the error disappear.</p> <pre><code>&lt;style name="CustomActionBar"&gt; &lt;!-- No styles --&gt; &lt;/style&gt; &lt;style name="JumbleeTheme" parent="Holo.Theme"&gt; &lt;item name="actionBarStyle"&gt;@style/CustomActionBar&lt;/item&gt; &lt;/style&gt; </code></pre> <p>So for some reason the Galaxy devices were looking at "android:actionBarStyle" even though they shouldn't be and it puts them into a very strange state.</p> <p>The solution that I adopted was to create a values-v11 resource folder where my theme.xml has references to "android:actionBarStyle" and all the other Honeycomb+ ActionBar attributes and in my values\theme.xml to only use the ABS attributes (eg actionBarStyle/actionBarSize).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload