d3fdb8bed8e836786253f9cd5ab640c7c5ed8501 |
|
07-Jul-2014 |
Barnaby James <bjames@google.com> |
Add VoiceInteraction request type for successful actions. Add CompleteVoiceRequest to VoiceInteractor to allow apps to indicate when a voice interaction was successfully completed. Change-Id: I1481cfe96e9e2495d88a7a4fb62263bdd1e03c54
/frameworks/base/tests/VoiceInteraction/src/com/android/test/voiceinteraction/MainInteractionSession.java
|
a2c076d54048258cf88ab14551ce5fdf5a09c6e8 |
|
31-May-2014 |
Dianne Hackborn <hackbod@google.com> |
Clean up voice API. Add various java docs. Switch to CharSequence where appropriate. Add new request for canceling voice interaction. Also update test app to follow API changes and be more better. Change-Id: If27eeba53cf6444660adb7d37ea2ce0557c6c91f
/frameworks/base/tests/VoiceInteraction/src/com/android/test/voiceinteraction/MainInteractionSession.java
|
c03c9167c2d9a1e22fb2b176b00a0524177fb037 |
|
02-May-2014 |
Dianne Hackborn <hackbod@google.com> |
Further work on voice interaction services. This makes VoiceInteractionSession a more first-class concept. Now the flow is that a VoiceInteractionService calls startSession() when it wants to begin a session. This will result in a new VoiceInteractionSession via the VoiceInteractionSessionService containing it, and the session at that point an decide what to do. It can now show UI, and it is what has access to the startVoiceActivity API. Change-Id: Ie2b85b3020ef1206d3f44b335b128d064e8f9935
/frameworks/base/tests/VoiceInteraction/src/com/android/test/voiceinteraction/MainInteractionSession.java
|
18f0d357f9693fe787a3e3777d8fdf01357a6e3f |
|
26-Apr-2014 |
Dianne Hackborn <hackbod@google.com> |
Rework some of the voice interaction APIs. On the app side, requests are now composed by subclassing from various types of Request objects. On the service side, starting a voice interaction session involves starting another service that will then manage the session. This leads the service design much more to what we want, where the long-running main service is very tiny and all the heavy-weight transient session work is elsewhere in another process. Change-Id: I46c074c6fe27b6c1cf2583c6d216aed1de2f1143
/frameworks/base/tests/VoiceInteraction/src/com/android/test/voiceinteraction/MainInteractionSession.java
|
91097de49b0f683b00e26a75dbc0ac6082344137 |
|
05-Apr-2014 |
Dianne Hackborn <hackbod@google.com> |
Initial implementation of new voice interaction API. This gives a basic working implementation of a persist running service that can start a voice interaction when it wants, with the target activity(s) able to go through the protocol to interact with it. It may even work when the screen is off by putting the activity manager in the correct state to act like the screen is on. Includes a sample app that is a voice interation service and also has an activity it can launch. Now that I have this initial implementation, I think I want to rework some aspects of the API. Change-Id: I7646d0af8fb4ac768c63a18fe3de43f8091f60e9
/frameworks/base/tests/VoiceInteraction/src/com/android/test/voiceinteraction/MainInteractionSession.java
|