[Verizon Samsung Galaxy S III] cabibi:
@OP... I too am having the issue where it gets stuck on initializing using this method.

So I compared the logcat files of launching the voice search activity by itself, and through the Bluetooth button utilizing BluetoothLaunch

Here's what I found:

when launching through Bluetooth launch, you get a Duplicate Finish Warning:

04-06 21:35:23.582 505 12344 I ActivityManager: START {act=android.intent.action.VOICE_COMMAND flg=0x10000000 cmp=com.kin.bluetooth_launch/.start_voice u=0} from pid 853

04-06 21:35:23.613 505 1632 I ActivityManager: Start proc com.kin.bluetooth_launch for activity com.kin.bluetooth_launch/.start_voice: pid=19213 uid=10174 gids={1028}

04-06 21:35:29.761 505 798 I ActivityManager: START {act=android.intent.action.VOICE_COMMAND flg=0x10000000 cmp=com.kin.bluetooth_launch/.start_voice u=0} from pid 853

04-06 21:35:37.238 505 842 I ActivityManager: START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.kin.bluetooth_launch/.config_voice u=0} from pid 934

04-06 21:36:05.019 505 798 I ActivityManager: START {act=android.intent.action.VOICE_COMMAND flg=0x10000000 cmp=com.kin.bluetooth_launch/.start_voice u=0} from pid 853

04-06 21:37:38.918 505 967 I ActivityManager: START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.googlequicksearchbox/.VoiceSearchActivity u=0} from pid 934

04-06 21:37:39.011 505 12345 W ActivityManager: Duplicate finish request for ActivityRecord{41993748 com.google.android.googlequicksearchbox/.VoiceSearchActivity}

04-06 21:38:35.855 505 798 I WindowState: WIN DEATH: Window{42288b68 com.kin.bluetooth_launch/com.kin.bluetooth_launch.config_voice paused=false}

04-06 21:39:13.668 505 516 I ActivityManager: START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.googlequicksearchbox/.VoiceSearchActivity u=0} from pid 934

04-06 21:41:05.519 505 1646 I ActivityManager: START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.kin.bluetooth_launch/.config_voice u=0} from pid 934

04-06 21:41:05.558 505 12344 I ActivityManager: Start proc com.kin.bluetooth_launch for activity com.kin.bluetooth_launch/.config_voice: pid=20229 uid=10174 gids={1028}

Everything in Bold Does NOT happen when you launch it natively. Instead, it goes right into the recognition phase:

04-06 21:36:05.019 505 798 I ActivityManager: START {act=android.intent.action.VOICE_COMMAND flg=0x10000000 cmp=com.kin.bluetooth_launch/.start_voice u=0} from pid 853

04-06 21:36:48.941 505 895 I AudioService: AudioFocus requestAudioFocus() from android.media.AudioManager@41951a18com.google.android.voicesearch.speechservice.GrecoRecognizer$1@4195f890

04-06 21:37:13.980 505 1632 I AudioService: AudioFocus abandonAudioFocus() from android.media.AudioManager@41951a18com.google.android.voicesearch.speechservice.GrecoRecognizer$1@4195f890

04-06 21:37:14.082 505 798 I AudioService: AudioFocus requestAudioFocus() from android.media.AudioManager@41951a18com.google.android.voicesearch.speechservice.GrecoRecognizer$1@4195f890

04-06 21:37:14.113 14305 16713 I VS.Greco3RecognitionEngine: create_rec: m=ENDPOINTER_VOICESEARCH,l=en-US

04-06 21:37:16.004 505 842 I AudioService: AudioFocus abandonAudioFocus() from android.media.AudioManager@41951a18com.google.android.voicesearch.speechservice.GrecoRecognizer$1@4195f890

04-06 21:37:16.105 505 798 I AudioService: AudioFocus requestAudioFocus() from android.media.AudioManager@41951a18com.google.android.voicesearch.speechservice.GrecoRecognizer$1@4195f890

04-06 21:37:21.316 505 1022 I AudioService: AudioFocus abandonAudioFocus() from android.media.AudioManager@41951a18com.google.android.voicesearch.speechservice.GrecoRecognizer$1@4195f890

Basically, BluetoothLaunch needs to be updated but the developer seems to be on hiatus. Unless there's someone on here with the capability to hack the .apk itself with a finish all command, I'm afraid we're stuck :(

---------- Post added at 05:21 AM ---------- Previous post was at 05:03 AM ----------

I posted my findings in the dev's xda thread. he hasn't been around in a while though, hopefully he comes back or someone can fix it!

http://xdaforums.com/showthread.php?t=836243