Flinging Unicorns

Some of you are fortunate to have gotten your hands on a DU build with Fling. Congratulations! I'm going to address a few things because I've been down this road before.


Home and Back action assignments

Fling is a gesture based navigation implementation that allows you to bind actions to gesture events. Home and Back are enforced assignments. What that means is this. Where ever back or home is assigned, that gesture is locked (greyed out). To open that gesture, you must first assign back or home to another gesture. Then the locked gesture will become open. This policy is to protect you from you.

Pulse

Pulse turns your Fling navigation bar (soon traditional navbar too) into a music visualizer when music plays. Pulse will not render visualizations under certain circumstances. This is a limitation of the Android API / media stack. It is not a bug. I will explain a bit further.

Android uses a output "sink" called remote submix in which audio may pass through for operations like downsampling (a2dp compliance etc), pre and post processing (fx) and other things including passing track data through the visualizer library. Most output destinations like bluetooth, headphones, music Chromecast, Android intercepts the audio track automatically and routes it through remote submix. The visualizer library gets the track data and we have Pulse. Device speaker output does not require remote submix operations. Often in cases where the track is streamed with DRM protection, remote submix is bypassed. Pulse does not work. I'm exploring options to force remote submix on speaker output. Such a task will be rather difficult and complicated.

Viper for DU Pulse (Visualizer API compliant)

Viper
https://drive.google.com/file/d/0ByczfSw2UY4JZEl2RVhxSXNyVXM/view?usp=docslist_api

Dolby
https://drive.google.com/file/d/0ByczfSw2UY4JZ0I5VHpITXZhOGM/view?usp=docslist_api