TransiCast

Known Issues

The following known issues exist with TransiCast

• Switching screen orientation is not very "snappy", it takes roughly a second to complete.

• Google Street View does not align with all stops and stations. This seems to occur for coordinates of off-street stops which are not associated with a street and respective pictures in Street View. Street View error message: "Invalid panorama".

Known Android™ platform problems

• Google's map view sometimes stops loading map tiles. This is independent from TransiCast, and is only a very rate occurrance.

• Since Android™ 2.1, Google's map view sometimes "disconnects" from the app. Neither tiles or grid are displayed. Zoom in or out typically rectifies the problem.

• When resource constrained, Android™ may "kill" the dynamic app widget without warning.

• LG and Samsung devices have shown to generate accelerometer sensor readings that are inconsistent with the test devices. This makes stop labels swing from left to right by themselves. TransiCast 2.0 introduces a method that detects sensor readouts that are incompatible. Switching stop label orientation by flicking the device is not available in such cases.

TransiCast has been fully tested and validated with the Android™ reference implementations Android™ 1.6 on the Google Ion development device, and Android™ 2.2.1 on the Google Nexus One. The Google Ion uses hardware that is equivalent to the HTC Magic, and is a compatible app development device, along with the Dev 1.
Carriers typically load custom builds of Android™ on the devices they sell through their stores and online. As is the case with the Sprint Hero, this often leads to incompatiblitie devices as sold by the carrier. Other devices have also shown incompatibilites such as accelerometer sensor events which are inconsistent with the development platform.
With that said, TransiCast runs on most any Android™ device.