Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: android-2.2_r1

May 17, 2010

  1. Kenny Root

    Import revised translations

    Change-Id: Ieb8194d6e3bf89d7df4f94589f55417a5e9f8f5f
    authored May 17, 2010

Apr 27, 2010

  1. Kenny Root

    Import revised translations

    Change-Id: Ie7067ecfb935f67b0483f005613eb92d0e64dfc9
    authored April 27, 2010

Apr 20, 2010

  1. Fix Bug: 2606879

    The problem is that if the user leaves the VoiceDialerActivity
    using the home button, when it is started again it never starts
    listening.  This is because all of the initialization is done
    in onCreate, but the teardown is done in onStop.  When the
    activity is left using the home button, the activity is stopped,
    but not destroyed, so onCreate is never called when the activity
    is started up again.
    This change moves the initialization to onStart, and leaves teardown
    in onStop. It really doesn't make any sense for this particular activity
    to be stopped or paused, if it's stopped at all it should be finished.
    So now the onStop function also calls finish().
    Change-Id: I4ddc7e329dfbf88d7b732191581877d9e5a3f0a3
    authored April 19, 2010

Apr 17, 2010

  1. Improved fix for Bug: 2326485

    When starting the voiceDialer, there is a tone played
    to indicate that the microphone is listening.  It's
    important the tone not be picked up by the mic and
    sent to the recognizer engine, or it will corrupt
    the sample.  Prior to this change, the VoiceDialerActivity
    would simply pull a fixed 380 milliseconds of audio
    from the microphone inputStream.  This works, but
    may not be reliable on all hardware platforms because
    the size of audio buffers and performance of the audio
    system may vary.
    Now, the VoiceDialerActivity removes audio samples
    and attempts to detect the tone.  When the tone ends,
    it stops pulling samples.  If no tone is detected within
    500 milliseconds, it times out and stops removing samples.
    Change-Id: Ic57ba1947fa0d315bec081bf03a32abb1a822fdf
    authored April 15, 2010

Apr 14, 2010

  1. Undo part of change I23cc8c1e

    In this change, in addition to the changes I intended to
    make, I accidentally reverted to a previous version
    of BluetoothVoiceDialerActivity.  Revert to the previous
    version, except for the changes that I intended to make
    to this file.
    Change-Id: I2d680dcfc81300dac645990c11675c7b1a048118
    authored April 14, 2010

Apr 13, 2010

  1. Put the beep back into the voiceDialer

    Bug: 2326485
    Now the VoiceDialerActivity plays a beep just as it starts listening.
    The hard part here is that we need the end of the beep to line up
    pretty accurately with the start of the microphone listening.
    If the beep happens before the microphone is listening, then the
    user will start speaking too soon. If the beep happens after the
    microphone is listening, then the sound corrupts the incoming sample.
    The other difficulty is that the time to start the microphone varies
    considerably from platform to platform, so there is no practical way
    to time the beep so matches. So instead, the VoiceDialerActivity
    will play the beep after the mic starts, and then pull the first part
    of the audio sample off of the incoming stream.
    The beep is 40 milliseconds long, but there is some lag in between
    requesting the tone to play and getting it back on the mic.
    Experimentally, pulling out the first 350 milliseconds of sample
    removes the beep without losing too much else on both Passion
    and Sholes.
    Change-Id: I23cc8c1e3969fd94a27a44e9e0e8c4f0a5cd5c00
    authored April 13, 2010

Apr 05, 2010

  1. add launch performance test for voice dialer

    this is part of an effort for collecting app launch time for the platform.
    Change-Id: I805cdee031345f0a477b3c7fec590e1c1d5acb00
    authored April 05, 2010
  2. Cherry pick e5258ff into Froyo

    authored April 01, 2010

Apr 02, 2010

  1. Cherry pick a3f9202 into Froyo

    authored March 31, 2010
  2. Cherry-pick 78c3b0c into Froyo

    Change-Id: I4c080561e3727ce0c53040690cd0d298ab393ff6
    authored March 26, 2010

Apr 01, 2010

  1. Merge "Fix issue 2546651: Speech indistinct/ jarred when using voice …

    …dialer over BT." into froyo
    authored April 01, 2010 Android (Google) Code Review committed April 01, 2010

Mar 31, 2010

  1. Fix issue 2546651: Speech indistinct/ jarred when using voice dialer …

    …over BT.
    Use stream STREAM_BLUETOOTH_SCO instead of STREAM_VOICE_CALL for TTS playback.
    It is more appropriate as it corresponds to current user setting for the bluetooth
    headset now that STREAM_BLUETOOTH_SCO and STREAM_VOICE_CALL are not synchronized
    any more.
    Also limit volume to an absolute max of -18dB instead of dividing it by 2 in order
    to avoid saturation without impacting lower volumes.
    Change-Id: I4576de363254b666bc3d4782693592b438f1d9ed
    authored March 31, 2010

Mar 30, 2010

  1. Kenny Root

    Import revised translations

    Change-Id: I97076c081e41a49b14bb09533db1b0fbdccd0eef
    authored March 30, 2010

Mar 25, 2010

  1. Make the voiceDialer work again

    Bug: 2537307
    The recognizer has a limit on the size of each semantic value
    in the grammar.  Now that we are storing both the package name
    and class name there, it's pretty easy to overflow that limit,
    causing the grammar initialization to fail.  With this change,
    only the spoken word is stored in the grammar (i.e. "calendar").
    The mapping of words to package name/class name is stored
    explicitly in a hashTable inside the commandRecognizerClient,
    which circumvents the recognizer's fixed limit.
    Bug: 2497802
    If the orientation changes while an alert dialog is up,
    the dialog would leak and causes an assertion failure.
    With this change the VoiceDialerActivity uses the more
    modern system of using dialogs, which automatically
    brings down and recreates the dialog upon orientation
    changes.  The BluetoothVoiceDialerActivity can't handle
    this right now, it's state machine is much more
    complicated.  For now, it just forces itself to be in
    protrait mode all of the time.
    Change-Id: I127c860b6db51426a93daf1df2d71c1c32673de5
    authored March 24, 2010

Mar 23, 2010

  1. Make the VoiceDialer handle "open" commands again

    Bug: 2515380
    The problem here was that the VoiceDialer app was assuming
    that the packageName of a component can be derived by
    dropping the last token of the className.  Apparently this
    is not true, the packageName as far as the packageManager
    is not the name of the package in the java sense.
    Now when adding all of the "open" entries to the grammar,
    the CommandRecognizerEngine adds both the package name
    and the class name, separated by "/".
    Change-Id: I79fe7d12f8f3b1b6873fcf1161b3d06f3e5e17c8
    authored March 22, 2010

Mar 18, 2010

  1. Merge "Import revised translations"

    authored March 18, 2010 Android (Google) Code Review committed March 18, 2010
  2. Kenny Root

    Import revised translations

    Change-Id: Ia772e9d7aa467bb3c0f80c70ddd5d0be17fb323b
    authored March 17, 2010
  3. Use new method of BluetoothHeadset API to check if voice dialer over …

    …bluetooth is supported.
    Needed for issue 2416481: Support Voice Dialer over BT SCO.
    Change-Id: I720f7f08d1bad0d61e0d7a9afeb696fefed18761
    authored March 17, 2010

Mar 17, 2010

  1. Now the BTVoiceDialer waits for TTS utterances to complete before mov…

    …ing on
    When the BluetoothVoiceDialer is about to place a call, it uses Text To Speech
    to indicate which contact is about to call. Prior to this change, it would
    just place the call after waiting a few seconds, which did not always line up
    with the end of the TTS utterance. Now it waits for the utterance to complete.
    Similarly, when it is about to exit it says "goodbye" to let the user know
    it's exiting, and it now waits for that utterance to complete before exiting.
    Fix a bug in VoiceContacts that caused it to skip the first row
    returned by that phone query. This meant that the first person/phone
    would not be entered into the RecognizerEngine, and therefore was
    impossible to call from the VoiceDialer.
    Change-Id: I4150f652d8df9bdc4ce54d573426bba64d13ad27
    authored March 12, 2010

Mar 10, 2010

  1. Add new broadcasts to handle packages installed on sdcard

    authored January 29, 2010
  2. Merge "Simplify the state machine of the VoiceDialer"

    authored March 09, 2010 Android (Google) Code Review committed March 09, 2010
  3. Simplify the state machine of the VoiceDialer

    * Eliminate the Retry state from the Bluetooth Voicedialer.  Now
    if the recognizer returns zero results, it will simply return to the
    Listening for Command state, and expect the user to state a new
    "call", or "dial" command.
    * The voicedialer is no longer allowed to open any applications when
    running from bluetooth.  There may be security problems with
    applications coming up over the lock screen.
    * Make the Bluetooth VoiceDialer handle error conditions better,
    now it will display an error message and exit if the Bluetooth
    connection drops, if the TTS system cannot be initialized, or if
    the recognizer returns a fatal error.
    * Make the VoiceDialerTester work again, so it should be easier
    to test recognition accuracy from many different speakers.
    Change-Id: Ic123648c22cf83598a641dd4cc664476261f5063
    authored March 04, 2010

Mar 09, 2010

  1. Add an empty

    Change-Id: Ibea7d8c504b59a259dd8e81d82c190a3e0e6890c
    authored March 08, 2010

Mar 05, 2010

  1. Add strings to VoiceDialer

    There are some new strings that will be used by the voicedialer.
    The strings need to be put in ASAP so that the translation people
    can get them, although the code does nt yet reference these strings.
    authored March 04, 2010

Feb 27, 2010

  1. Import new translations.

    authored February 26, 2010

Feb 24, 2010

  1. Improve bluetooth voicedialing support

    Bug: 2432200
    When using voicedialing without being able to see or interact with the
    screen, it is more important to keep the number of matches small.  There
    is now a setting on the CommandRecognizerEngine called "minimizeResults".
    If this is set, then the CommandRecognizerEngine will in most cases return
    only the highest confidence result.
    It will return multiple results only in the case where it is unsure which phone
    to call a particular person on.  When this occurs, the BluetoothVoiceDialer
    will announce the person it is about to call, and which phone types are available
    (i.e. home, work, mobile, other), then begin listening for the the user to
    indicate which phone.
    authored February 23, 2010
  2. Make Voicedialer support "open" commands again

    Bug: 2460661
    I had inadvertently removed the call to adddOpenEntriesTooGrammar,
    so the open commands were not being recognized.
    authored February 24, 2010

Feb 19, 2010

  1. Add initial support for Bluetooth voice dialing.

    Bug: 2432200
    This adds a new BluetoothVoiceDialerActivity,
    because the flow for bluetooth is so different from the regular VoiceDialerActivity.
    This involved breaking RecognizerEngine's direct dependence on VoiceDialerActivity to
    make callbacks on. RecognizerEngine now makes callbacks on an interface called RecognizerClient,
    which is implemented by several different helper classes for different reasons.
    I've made RecognizerEngine an abstract base class, it handles some general setup, logging, etc.
    but it is up to the subclasses to set up the grammar and handle the results when recognition
    succeeds.  There are currently two subclasses, the CommandRecognizerEngine recognizes
    phrases to call people, dial numbers, and open applications.  The YesNoRecognizerEngine recognizes
    "yes" and "no".
    Known issues as of this checkin:
    * 8khz audio has not been validated, it's not certain that the Recognizer is getting a good audio stream.
    * There is still a problem with audio routing, the TTS output switches randomly between the speaker and
    the headset.
    * only the simplest case is supported, there's not a clean solution when there are multiple
    possible matches.
    * there are cases where the activity really should wait for the TTS utterance to finish before
    moving on.
    * we don't have a solution for when the phone is locked and the user activates bluetooth voicedial.
    * the flow may or may not be ideal, the "no matches, try again" option may not be useful.  We will
    let some people try this and then revisit the approach.
    authored February 09, 2010

Feb 11, 2010

  1. Jeff Hamilton

    Add an original-package tag that matches the real package name.

    Change-Id: I05f5ab2f107ae21560185dbd98e8096cc6b3e668
    authored February 11, 2010

Feb 09, 2010

  1. Merge "Update mdpi resource with 2.0 style icon"

    authored February 09, 2010 Android (Google) Code Review committed February 09, 2010

Feb 08, 2010

  1. Update mdpi resource with 2.0 style icon

    authored February 08, 2010

Feb 05, 2010

  1. am 65848a8: am 574fba2: reconcile main tree with open-source eclair

    Merge commit '65848a8723fbcfe32632fd6b031fd98dde9bbde7'
    * commit '65848a8723fbcfe32632fd6b031fd98dde9bbde7':
      android-2.1_r1 snapshot
    authored February 05, 2010 Android Git Automerger committed February 05, 2010
  2. am 574fba2: reconcile main tree with open-source eclair

    Merge commit '574fba2dc93c556d3e13ce5e9e803683eae9a2ca' into eclair-plus-aosp
    * commit '574fba2dc93c556d3e13ce5e9e803683eae9a2ca':
      android-2.1_r1 snapshot
    authored February 05, 2010 Android Git Automerger committed February 05, 2010
  3. reconcile main tree with open-source eclair

    authored February 05, 2010

Jan 29, 2010

  1. reconcile android-2.1_r1 snapshot

    authored January 29, 2010
Something went wrong with that request. Please try again.