On Sat, Jul 14, 2012 at 5:03 PM, Cythes <[email protected]> wrote: > So if I take it back to the regular dispatchkeyevent, it should fix it.... > or do I need to find something to call it to? IN which case would be my main > activity.
Simply have your activity handle the key event itself, and delete your service and your boot receiver. Having a service running all of the time is something users generally dislike, and the service is not helping you, since the activity is perfectly capable of handling your current business logic with respect to the key event. If you are somehow thinking that you will have something "in the background" that can respond to key events like this, that does not work. A couple of key events will get broadcast if the foreground activity does not consume the event (e.g., ACTION_CAMERA_BUTTON). Otherwise, key events are for the use of the foreground activity and the OS. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.8 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
