Glass - ListActivity no longer scrolls up/down with left/right swipes

[barbeau]

Reported by @paulpv in OneBusAway#116 (comment):

ListActivity no longer scrolls up/down with left/right swipes. Here are some SO links that may help to solve the problem:
http://stackoverflow.com/questions/23097555/how-to-enable-scrolling-on-a-simpleadapter-on-google-glasss-firmware-x16/23146305#23146305

Here is my app's issue, specifically related to PreferenceFragment: http://stackoverflow.com/questions/23160084/preferencefragment-cannot-scroll-up-down-on-xe16-worked-fine-on-xe12

This likely started occurring due to the XE16 update, since few things have changed since the XE12 version, and scrolling worked on XE12.

[barbeau]

Same issue still occurs on XE16.1 that is rolling out now.

[barbeau]

I filed an issue for broken ListView scrolling on Google GDK issue tracker:
https://code.google.com/p/google-glass-api/issues/detail?id=484

[barbeau]

In above issue, Google is saying they won't fix, and we should look at CardScrollView instead (I assume this means cascading items that don't fit on the screen to new Cards in the CardScrollView - I've asked for clarification here).

In the mean time, as quick fixes to the current version, I have two implementations in two different branches:

1. Gesture-based fix - https://github.com/CUTR-at-USF/onebusaway-android/tree/glassFixListScrollGesture - swipe forward/backwards as before (but selected element always stays at top now)
2. Sensor-based fix - https://github.com/CUTR-at-USF/onebusaway-android/tree/glassFixListScrollAccelerometer - tilt your head up/down to scroll. Tap to pause/resume scrolling.

@paulpv opinions? The accelerometer-based option is dangerously close to being usable, IMO :).

[barbeau]

Just tweaked the sensor-based implementation - Also, two finger hold is now used to pause/resume scrolling, and two finger tap is used to scroll to top of the list. This reserves one finger tap for menu access (to come).

[barbeau]

I'm running with the sensor-based implementation for now, as it seems like the most reasonable solution (especially as a temporary quick-fix, until I try something with CardScrollView). If its problematic for some users, we can revisit it.