Added a simply system to keep record of the x most recently played
OpenALSoundS (where x is the number of simulataneous sources allowed) and,
in case a new sound refuses to play, stop()'s the least recently played
sound and attempts to play it again (but only once, to prevent endless
loops in case something else prevents the sound from playing).
Added removal of disposed sounds from the buffer
Fixes issue 912

Android Audio now functions correctly on pre-Android 4.1 (pre-Jellybean)
Minor formatting
Remove comments on issue number
Add support to GWT for GlGetInteger, glGetFloat and glGetString
Correct packing for square texture (previous code would increase the
size of the image after packing. the new one packs to square image
directly, giving better result).
AndroidSounds now respond to lifecycle

Fixes #1263 on Android
Behavior is now alike with music on Android
Updated GWT backend to GWT 2.6.0

- Java 7 support (yay!)
- IE 6/7 support disabled by default.
- See GWT changelog for more
- Pulled from maven central
Merge remote-tracking branch 'origin/master' into gwt-2.6.0
Updated Changes to reflect gwt upgrades.
Fixed livewallpaper applications missing some offsetsChanged notifications on non-continuous rendering
Additional radian based angle/rotation methods.
remove unncessary degree/radian conversion value from Matrix3
Merge remote-tracking branch 'upstream/master'
Added gradle support for running texturePacker at build time.

Make sure the proper ext.texturePacker parameter is set in the toplevel
gradle.build file and have TexturePacker run with those whenever the
"texturePacker" task gets invoked, e.g. "./gradlew texturePacker
desktop:run".
Tweaked GWT reflection
Merge remote-tracking branch 'origin/master' into gwt-2.6.0
Fixed merge conflict
Update FPSLogger to use nanoTime. 

"currentTimeMillsis" pulls time from the system clock and should not be used to measure elapsed time. Other processes like NTP, or the user, can alter the system clock and the time returned can unexpectedly shift and create bizarre and intermittent behavior.

"nanoTime" is a measure of nanoseconds from some arbitrary time point and is safe for measuring elapsed time.

The results of this bug are rather benign – worst case the time is changed back and you would not get a framerate log message for that time, or until the user restarts the program. However, this flavor of bug can cause significant intermittent issues if present in other areas if the user is unfortunate enough to have his clock changed while he is playing (this happens more than you may think thanks to NTP keeping our system clocks in sync.)

See: 
http://docs.oracle.com/javase/7/docs/api/java/lang/System.html#nanoTime%28%29
http://docs.oracle.com/javase/7/docs/api/java/lang/System.html#currentTimeMillis%28%29
Migrated to TimeUtils.nanosTime()

Updated as suggested.