In Mobile Services a session starts when a a user launches your app, and ends when they leave your app for longer than your configured lifecycle timeout (analytics.lifecycleTimeout in the SDK JSON configuration), which defaults to 5 minutes. Launches is the metric that tells you the number of sessions. The session length only reports time that the app was actually open. A session, while analogous to a visit, is not aligned with the visits metric, and is not available as a container for segmentation.
The numbers in the path reports are instances or path views. It is the number of times that sequence of states or actions occurred. The green tapered in path is the entries, or number of times it was the first state or action in the visit. The red tapered out path is the exits, or number of time it was the last state or action.
I'm not sure what you mean by "click counts". Any actions that you have tracked using the Mobile Services SDK can be reported on in Mobile Services, or any of the Adobe Analytics tools.
A/B results for Target Activities are reported at the bottom of the page where you define your activity.
As previously mentioned, the data in Mobile Services is available in all of the other Adobe Analytics tools including data feeds.
For geolocation, you can pass in GPS coordinates, which will populate a Map report of the location variables. On the map, close coordinates are grouped together and summed, while the table lists all coordinates separately. That may account for what you are seeing. Adobe additionally can lookup geo information from the IP address of the client. The Countries, Regions, Cities reports use the IP lookup information.