Dissmissing the Overflow menu on 4.1.x produces warnings (and visual artifacts)

[Wavesonics]

On 4.1.x devices dismissing the overflow menu throws the following warnings every time:

11-09 12:58:01.099: W/InputEventReceiver(23881): Attempted to finish an input event but the input event receiver has already been disposed. 11-09 12:58:01.099: W/InputMethodManagerService(351): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@41abe0f8 attribute=null

Additionally, on the Nexus 7 (4.1.2), really hammering on the Overflow menu icon (opening and closing it very rapidly) produces what appears to be temporary video memory corruption. It only lasts for a split second, but you can reliably reproduce it by tapping the menu icon rapidly. And I've confirmed other apps not using ABS do not exhibit either of these symptoms when rapidly tapping the menu icon.

[rmack]

I have the same issue. When testing on Jellybean I receive the following error "12-12 22:24:19.820: W/InputEventReceiver(20995): Attempted to finish an input event but the input event receiver has already been disposed."

In addition, I also notice the artifact and it looks like a Flicker. I have received reports that the flicker prevents the use of the SubMenu options on some devices such as the Razor. I have just started diagnosing the issue and I wanted to report it here. I didn't have this issue with Android versions prior to Jellybean.

Currently if I add more than 4 SubMenu options the flicker appears. If I have 4 or less the flicker does not occur, but I still get the error in the logcat.

I do not have to hammer the menu for the artifact to appear, and it isn't consistent.

Another note is that I had to change to the new Android support library to get my application to compile. I have not tested to see if I get the same issue when compiling with the support library provided by ActionBarSherlock.

If I figure anything out I will post it here.

Thank you.

Update: 12/17/12 -------------------------------------------------------------------

Thanks iNoles... I was aware of this, but I couldn't find any code I could change within ActionBarSherlock to account for an action cancel for SubMenus...

I rooted around in ActionBarSherlock code for a while and I couldn't find any specific way to prevent the "Flicker" artifact from taking place. I have received 6 e-mails with people not being able to use the ActionBar SubMenues at all; which makes my app useless... so...

My current work around:

Check the build and create two different sets of SubMenus based on Jellybean. If the device is at JellyBean I would make sure each submenu only had four items. If there were more then four I would group the extras into more SubMenus with no more than 4 items. If the device is not at Jellybean I create my submenus how I would normally. I might try making lists instead of SubMenus. I haven't tried this yet.

I need to get a new version out with these fixes and then I will potentially research the problem more within ActionBarSherlock.

Cheers...

[iNoles]

Looks like http://developer.android.com/reference/android/view/MotionEvent.html#ACTION_CANCEL got called while ABS is not aware of it.