b625e19a877dc8e128329d730bc5e9b8e8a2fce9 |
|
03-Jun-2016 |
Svetoslav Ganov <svetoslavganov@google.com> |
Properly set default voice interactor We need to figure out the default voice interactor to give it default permissions. This happens before the user has been unlocked and if the voice interactor is not direct boot aware we fail to find it, hence no permissions are granted. Now we query the package manager for both direct boot aware and unaware components. This is fine as we don't interact with the assistant until the user is unlocked. bug:28963642 Change-Id: Ide5471fa1798e868c6e3a4b5e87570a5556e2d3f
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.java
|
0af6fa7015cd9da08bf52c1efb13641d30fd6bd7 |
|
18-Jan-2016 |
Amith Yamasani <yamasani@google.com> |
Voice Interaction from within an Activity This allows an app to show a voice search button and invoke a voice interaction session for use within the activity. Once the activity exits, the session is stopped. Test application has a new activity that demonstrates it with the test voice interaction service. This initial version is functional enough for an integration test, with some more tests and improvements to come later. Bug: 22791070 Change-Id: Ib1e5bc8cae1fde40570c999b9cf4bb29efe4916d
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.java
|
cbb2382992bdab4cc6d429fd5d015d68d1912f8a |
|
23-Jan-2016 |
Jorim Jaggi <jjaggi@google.com> |
Merge "NullPointerException when starting VoiceInteractionManagerService" am: b7fbe1104f am: 5d6da4eab0 * commit '5d6da4eab024c13afbfef5cfec0f9f2b19168318': NullPointerException when starting VoiceInteractionManagerService
|
7dbcbad577a32f16d75dde3fe1412c56c5a2a399 |
|
15-Dec-2015 |
Edward Savage-Jones <edward.savage-jones@sonymobile.com> |
NullPointerException when starting VoiceInteractionManagerService If an end user disables the package that implements support for Voice Assist (Google App) and reboots, an NPE is thrown during boot, which results in the device getting stuck at the boot animation. Recovery is not possible without USB debugging enabled, leaving factory reset/user data wipe as the only other option. Change-Id: I9c161fff7f096deee13bf8e37d951e20898ae3ff
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.java
|
c83189b5d6ab2fe5f1c38cbe22254f4995379c88 |
|
17-Nov-2015 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #25673462: Shamu update from MMB29J -> 29K does not complete The direct path to the package manager returns null on failure, oops! Change-Id: Id33ea299b605a59b0703dab200bafb754dd66e78
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.java
|
e70d6535237d2e6f03adcd0bdc11e45ea714dc97 |
|
25-Apr-2015 |
Selim Cinek <cinek@google.com> |
The voice assist may now be launched above the lockscreen A possibility was introduced to launch voice assist over the lockscreen using the left keyguard affordance. Change-Id: Ic4618d24256b65441a50d77d0ef59b0ec99b6ead
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.java
|
5f560d056243638a83a4e7770035fdb66004c9d7 |
|
30-Apr-2015 |
Jorim Jaggi <jjaggi@google.com> |
Rename supportsAssistGesture to supportsAssist Bug: 20642759 Change-Id: Idddc786980244cc94570d04fd414540bbad60448
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.java
|
0b68ff45125e449dd0b4120f530240093aa6253e |
|
02-Apr-2015 |
Jorim Jaggi <jjaggi@google.com> |
Add flag to voice interactor for supporting assist gesture Add an additional flag to the voice-interaction-service declaration so it can indicate whether it is able to handle the assist gesture. Use that information in SystemUI so it only starts the voice interaction session if the service is able to support it. Change-Id: I62b035ce4f4cf06ee6e7eb0ddc4bf5edbc0e6737
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.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/VoiceInteractionServiceInfo.java
|
ecc7498b2bcf65adf20f5544a2994c68b75f8cea |
|
13-Aug-2014 |
Dianne Hackborn <hackbod@google.com> |
Turn off voice interaction service restrction for now Need to wait for the prebuilt to update. Change-Id: I5501c2ba23e6e18379aa0859b248446c82de6cdc
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.java
|
a3fb40d5f492825bb86769f541620baca5616e05 |
|
13-Aug-2014 |
Dianne Hackborn <hackbod@google.com> |
Add 560dpi, and some other stuff. Like new settings actions for some of the new settings panels. And fix voice interaction services so they require a recognizer. And tweak array map doc to be correct. Blah blah blah. Change-Id: Ib5e66b574b10e7b3fa39723b21046a74e6ead204
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.java
|
a351ab96987381ffe7ea29a7cdec1e7fbd1497d5 |
|
09-Aug-2014 |
Dianne Hackborn <hackbod@google.com> |
Fix issues 16739817 and 16709247 in voice interaction service. Issue #16739817 VIS doesn't start for non-primary user(s) Issue #16709247 GSA is not the default voice interaction agent These are both fixed by getting rid of the existing code for applying the default voice recognizer, moving it in to the voice interaction manager service, and extending it to also set up the default voice interaction service. Change-Id: If8d5936c28aebfa7eff77c8d99241c3a2ffdb0a4
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.java
|
fee756ff91ab4d8f0e09ddb050d22d88ebb66ae7 |
|
17-Jul-2014 |
Dianne Hackborn <hackbod@google.com> |
Implement issue #16330060: Inform ActivityManager about WebView... ...state changes. Add a new API to tell the activity manager about a new dependency one process has on another package. Start using it already for when apps is Context.createPackageContext() to load code from another app. Also do some work on getting the monitoring of proc/uid states in shape so it can be used by unundled code, along with an AppImportanceMonitor class for doing so. Some small fixes and additions to VoiceInteractionService. Improve handling of unaccounted/overcounted battery use so that they aren't shown to the user unless they are significant. Change-Id: I22dd79a73f4e70103d3f8964494aebc8a31f971c
/frameworks/base/core/java/android/service/voice/VoiceInteractionServiceInfo.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/VoiceInteractionServiceInfo.java
|