gamepad | Pull values from gamepads over USB | Model View Controller library

My answer here is going to be as succinct as possible. My full code is available on GitHub.

As far as I am aware, a developer cannot perform an accessibility action via ADB, they would have to create an Accessibility service in order to act on behalf of an Accessibility user and create a Broadcast Receiver so that it can take input via the ADB. This is two thirds of the answer, requiring one more component as developers cannot activate accessibility services via the ADB! This has to be done manually each time accessibility is toggled or through accessibility shortcuts - of which there can be only one. EDIT I figured this bit out as well :)

The developer documentation provides a mechanism for an Accessibility Service:

An accessibility service is an application that provides user interface enhancements to assist users with disabilities, or who may temporarily be unable to fully interact with a device. For example, users who are driving, taking care of a young child or attending a very loud party might need additional or alternative interface feedback.

I followed the Google Codelab to construct a service that could take actions on the part of a user. Here is a snippet from the service, for swiping left and right (user navigation):

It happened because not always targeted when clicking on .

When accidentally clicked on

You can manipulate it with css covered up whole

This is one of those classic problems with collision detection, where the collision occurs at some point along the object's path but the object moves far enough that the next tick doesn't fix the problem, leaving the object - your ball in this case - to fall forever outside of the viewport.

To solve this you need to not only change the vertical velocity but also have the ball reflect off the collision point. You're already bouncing the velocity vector, you just need to add position reflection. The simple way is to just take the amount of overshoot and subtract it from the limit, putting the ball back in bounds:

Forgot to set a bool variable to true

In your Draw() code, instead of

Thanks to Jack White this is the solution:

Property deviceId of Gamepad module shall be initialized, using GamepadManager.

This could be done with bitwise & operator.

Polling and waiting each have their advantages and are good for different situations. Neither is "wrong" per se, but you need to use the correct one for your specific use case.

xcb_wait_for_event(connection) is a blocking call. The call will not return until an event is available, and the return value is is that event (unless an error occurs). It is good for situations where you only want the thread to respond to events, but otherwise not do anything. In that case, there is no need to spend CPU resources when no events are coming in.

xcb_poll_for_event(connection) is a non-blocking call. The call always returns immediately, but the result will be NULL if no event is available. It is good for situations where you want the thread to be able to do useful work even if no events are coming in. As you found out, it's not good if the thread only needs to respond to events, as it can consume CPU resources unnecessarily.

You mention that your goal is to create a game or something similar. Given that there are many ways to architect a game, either function can be suitable. But there are a couple of basic things to keep in mind that will determine which function you want to use. There may be other considerations as well, but this will give you an idea of what to look out for.

First of all, is your input system running on the same thread as other systems (simulation, rendering, etc)? If so, it's probably important to keep that thread available for work other than waiting for input events. In this case, xcb_poll_for_event() is almost required, otherwise your thread will be blocked until an event comes in. However, if your input system is on its own thread that doesn't block your other threads, it may be acceptable to use xcb_wait_for_event() and let that thread sleep when no events are coming in.

The second consideration is how quickly you need to respond to input events. There's often a delay in waking up a thread, so if fast response times are important you'll want to avoid letting the thread sleep in the first place. Again, xcb_poll_for_event() will be your friend in this case. If response times are not critical, xcb_wait_for_events() is an option.

Solved and posted the answer here:

https://community.monogame.net/t/install-parse-failed-manifest-malformed-only-on-some-devices

In short the answer is:

On older api versions (<25 and therefore you should ALWAYS do this to support them?) it seems Android requires that:

the fully qualified Namespace of the Activity Name property must be lowercase.