57dd737443a174379eb638450e4888500d8e4a23 |
|
28-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #21516866: Implement voice interaction in ResolverActivity The main change here is to not allow the dialog to go in to its "focus on the last app the user selected" when running in voice interaction mode, instead just always giving a simple list. This also fixes some problems with cleaning up active commands when an activity finishes and not forcing the current session to go away when the screen is turned off. Also added some debug help, having activity print the state of the voice interactor. Change-Id: Ifebee9c74d78398a730a280bb4970f47789dadf5
/frameworks/base/core/java/android/service/voice/VoiceInteractionSessionService.java
|
593334ab70a8341c7d24d71a377ab5617e3f4ab7 |
|
30-Jun-2015 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #22124996: VI: Command Request not Active Just forgot to add the request to the active set. Also eradicate a bunch of old cruft that has been replaced by the final APIs, and improve voice interaction test to sit fully on top of the final APIs and have a test for command request. Change-Id: Ieff7a6165ebf2a4c5fb80c1ebd020511a2ae63ee
/frameworks/base/core/java/android/service/voice/VoiceInteractionSessionService.java
|
1e38382b542f5cef9957a89692b02c55a3dd351c |
|
10-Apr-2015 |
Dianne Hackborn <hackbod@google.com> |
Fixes to idle alarm scheduling, package importance. - Add new API to ask the activity manager what the current importance of a particular package name is (along with a few new useful importance levels). - Fix my last alarm manager change to actually execute the alarms we have now decided should run even while we are idle. Change-Id: I1f14712b4e390770d53b185c96a1b36f6aadd687
/frameworks/base/core/java/android/service/voice/VoiceInteractionSessionService.java
|
ae6688b09649447e57468b3e7935691bc09ec9b9 |
|
12-Feb-2015 |
Dianne Hackborn <hackbod@google.com> |
Update voice interaction layer for new UI design. Can switch from a pure overlay at the top of the screen, to interactive mode with the voice UI drawing at the bottom and pushing its target activity up like an IME. Add mechanism to get assist data to the voice interaction UI. Add some basic visualization of the assist data, outlining where on the screen we have text. Add a test ACTION_ASSIST handler, which can propagate the assist data it gets to the voice interaction session so you can see what kind of data we are getting from different apps. Change-Id: I18312fe1601d7926d1fb96a817638d60f6263771
/frameworks/base/core/java/android/service/voice/VoiceInteractionSessionService.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/core/java/android/service/voice/VoiceInteractionSessionService.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/core/java/android/service/voice/VoiceInteractionSessionService.java
|