Daniel Sandler d4d2de2a77 Do not vibe when the default notification sound is Silent. ...

(This relates to the new vibration fallback behavior, where
notifications that expect to make a sound should always
vibrate in vibrate mode. We should not vibrate if the
notification's sound is silent, but we should also not
vibrate if the notification uses the default sound and the
default is silent.)

Bug: 7537077
Change-Id: I08e149c8c00ef2d2f61e418d88a086cb5e9cf241

2012-11-14 16:42:04 -05:00

api

…

cmds

…

core

Notification vibration improvements:

2012-11-14 11:50:11 -08:00

data

…

docs

Merge "docs: Update platform version page with 4.2 release" into jb-mr1-dev

2012-11-13 13:36:01 -08:00

drm

…

graphics

…

icu4j

…

include

…

keystore

…

libs

…

location

…

media

Merge "Support Wifi display devices that rename themselves." into jb-mr1.1-dev

2012-11-13 10:00:04 -08:00

native

…

nfc-extras

…

obex

…

opengl/java

…

packages

Fix "keyguard unresponsive" bug

2012-11-12 17:54:22 -08:00

policy

Merge "Synchronize access to Locked methods. DO NOT MERGE" into jb-mr1.1-dev

2012-11-13 08:27:22 -08:00

samples/training/network-usage

…

sax

…

services

Do not vibe when the default notification sound is Silent.

2012-11-14 16:42:04 -05:00

telephony/java

…

test-runner

…

tests

…

tools

Add mechanism to kick keyguard to show the assistant

2012-11-08 00:39:04 -08:00

voip

…

wifi/java/android/net/wifi

Re-use existing thread

2012-11-07 13:02:08 -08:00

Android.mk

…

CleanSpec.mk

…

MODULE_LICENSE_APACHE2

…

NOTICE

…

preloaded-classes

…

Description

No description provided

5.1 GiB

Languages

Java 77.3%

Kotlin 9.2%

PowerBuilder 6.6%

C++ 5.5%

AIDL 1%