| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add APNType info to notifications so you can tell what's happening. Now, even if a new APN
shares a connection with an already-connected-to- apn type, the new type will get all
the connecting and connected messages on connect and disconnecting/disconnected on disconnect
even though the shared connection remains connected.
Cleaning out the hacks MobileDataStateTracker needed to deal with the old situation.
bug:2226092
Change-Id: Iddd7421d6b91cda7c8405f9c3d5404ac04ef8e42
|
|\ \
| | |
| | |
| | | |
into kraken
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When dealing with any kind of limited operating system resource,
we should ensure that we properly close everything that we
open, rather than relying on the system garbage collector.
Change-Id: Ic71f710eb85ac71a91b7a1215647c75010d37643
|
|\ \ \ \
| |/ / /
| | | /
| |_|/
|/| | |
Change-Id: Ia4538f73d8bade9e6565835d484dcb650830feca
|
| | |
| | |
| | |
| | | |
Change-Id: Ie495a41dac03e1fe5ddccefcbd2a0673090a6db1
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This lets it turn off the LED. However, it seems like somebody broke
the notification LEDs. GRRR.
Change-Id: I3f7066c2b2e1673dc0144a34cf59946351a647be
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Then, now that StatusBarManagerService is the only thing in that package,
move it up to the regular services package. (I've been waiting for 4 years
to delete that package!)
Change-Id: If5faf44641319fd19e486d1f4e5bc1c6dfcff3ad
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
trampolining through
a braodcast receiver.
Change-Id: I6ae0740fea07350b80c35c0ee2d938e0364d773e
|
| | |
| | |
| | |
| | | |
Change-Id: I57b2d296e0d0cef0d256ae6697fffc47188d14df
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On an inflation error, the StatusBarService cleans up, removes / doesn't add
the views, and calls into the StatusBarManagerService, which tells the
NotificationManagerService to remove the notification.
That then calls all the way back into the StatusBarService, but I think being
extra careful is okay. Throughout the status bar, it's all keyed off of the
IBinder key, so if the app comes in with a good notification while we're
cleaning up, we won't lose the new notification or anything like that.
Change-Id: Iea78a637495a8b67810c214b951d5ddb93becacb
|
|\ \ \
| |/ /
| | |
| | | |
I4a11f027,Ib2c4abf6,Id0c7ef9f,I839d7771 into kraken
|
| | |
| | |
| | |
| | |
| | |
| | | |
Right now the number is 50, just to prevent apps that have gone completely bonkers. I think the limit should be lower.
Change-Id: Ib2c4abf669c8b0250e5421b6d5aeb81aeb2f82ce
|
| | |
| | |
| | |
| | |
| | |
| | | |
Also fix the notification to show properly when the runtime is restarted.
Change-Id: Id0c7ef9f9dc9c9df18428cbaa7db1703f085137e
|
| | |
| | |
| | |
| | | |
Change-Id: Ib633eb144277ec2598f25eac3a9cfe0f0184959e
|
| | |
| | |
| | |
| | | |
Change-Id: I81f7a8118876ee7cb6c356c63b0d0613d9777d4f
|
| | |
| | |
| | |
| | | |
Change-Id: If54cb7209d65eef826d474d7e0dbbef63d2f2b47
|
|\ \ \
| |/ /
| | |
| | | |
KeguardManager API if device policy is enabled" into froyo
|
| |\ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
is enabled" into froyo
Merge commit '75b6a6b972e6b18143fd629d3d9c824c442c5f4c' into kraken
* commit '75b6a6b972e6b18143fd629d3d9c824c442c5f4c':
Fix 2737842: Disable KeguardManager API if device policy is enabled
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change adds notification to find out when the device policy
has changed. When an admin adds or changes a policy, we get notified
and reset the state of keyguard to be enabled.
It also moves disabling keyguard into the TokenWatcher.acquired()
method to avoid disabling keyguard when a policy doesn't permit it.
This avoids reference counting issues in TokenWatcher and hence relieves
the ordering issue.
There is one remaining caveat. An application that uses KeyguardManager
to disable keyguard will need to disable keyguard again after any
policy change.
Tested:
Install and run app that disables keyguard with no admin. Result: keyguard is enabled/disabled as expected.
Enable admin and set quality = "something" after installing & running app. Result: keyguard is enabled.
Change admin password quality to "unspecified" and re-run app (per caveat). Result: keyguard is disabled.
Change admin password quality to "something" again. Result: keyguard is enabled.
Disable admin : Result: keyguard is enabled until app runs again (per caveat).
Added minor cosmetic changes after review.
Change-Id: I302f2b01446bf031f746b0f3e8b5fd7a6cc0e648
|
|\ \ \
| |/ /
| | |
| | | |
API when device policy is enabled." into froyo
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
enabled." into froyo
Merge commit 'bde25c207731783a62e3611586fe05cd35add0d9' into kraken
* commit 'bde25c207731783a62e3611586fe05cd35add0d9':
Fix 2737842: disable keyguard API when device policy is enabled.
|
| | |\
| | | |
| | | |
| | | | |
into froyo
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fix disables KeyguardManager's enable/disable API when any
device policy admin requests a policy that enforces a password.
Change-Id: Idb1da16b14ed8963142f7b1f62d2b060d84ffa65
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
after boot complete" into froyo
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
froyo
Merge commit 'ac24d23cd4a96f38b4e9cb0318a7c298794b9b6a' into kraken
* commit 'ac24d23cd4a96f38b4e9cb0318a7c298794b9b6a':
Don't bring up Launcher until after boot complete
|
| | |\ \ |
|
| | | |/
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The preboot upgrade handling was bringing up the acore process with a default
application object, then the normal "start the HOME app" code was bringing up
Launcher2 [hosted in acore] in anticipation of boot completion... but then it
saw that the host process was alive and continued with Launcher2's init.
Launcher2 depends on a custom application object, however, so it crashed
immediately.
This change ensures that the HOME app is not actually initted at that level
until after boot has completed, at which point its proper application class
can be instantiated.
Fixes bug #2732250
Change-Id: I1a15384e2c0d50e14300df0c0db236bd7b1a187c
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
addPackageToPreferred throws SecurityException" into froyo
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
SecurityException" into froyo
Merge commit 'd1d9047d5c34fb05be08099fa8cd73e4301ee0ff' into kraken
* commit 'd1d9047d5c34fb05be08099fa8cd73e4301ee0ff':
Fix issue #2749322: addPackageToPreferred throws SecurityException
|
| | |\ \
| | | | |
| | | | |
| | | | | |
into froyo
|
| | | |/
| | | |
| | | |
| | | | |
Change-Id: I96cdc110fd9acca4b6c95d281e819bad1e4557f8
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
Change-Id: I8b0b595580d9c6d44b84e636012705dc913fa6ac
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | | |
Merge commit '5a671d03e3abe522a761a43b0460f9f3816b14ed' into kraken
* commit '5a671d03e3abe522a761a43b0460f9f3816b14ed':
Cut logging, boost efficiency of ThrottleService
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changed the Alarms to be non-waking.
bug:2748959
bug:2747862
Change-Id: I9e4294162a4fc2f90aed36393b858edcf82aa307
|
|\ \ \
| | | |
| | | |
| | | | |
com.android.server.AccessibilityManagerServiceTest:testInterrupt is failing"
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
failing
Change-Id: I73d056c7dcf8edddae2ef9cb28ec7d2b3203bb9b
|
|\ \ \ \
| | |/ /
| |/| |
| | | | |
native binaries from .apk" into kraken
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
kraken
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The previous implementation fails to work properly when the .apk
and installed versions of the binaries have the same size and date.
Change-Id: I296e34505ab4f0af028de5bcff7a83969f160ec1
|
|\ \ \ \ \
| |/ / / /
| | | / /
| |_|/ /
|/| | | |
component.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also add new action to show an app's details.
Change-Id: I6ad3b3ac8462f5acf726ce76130882a262adff92
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
stacks when it fires" into froyo
|
| |\ \ \
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | | |
Merge commit 'df2e2eff9446c0220515fa7aab7857135e04e12e' into kraken
* commit 'df2e2eff9446c0220515fa7aab7857135e04e12e':
Watchdog now records kernel stacks when it fires
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The kernel threads are appended to the usual /data/anr/traces.txt file
and dropboxed along with the usual Dalvik stack dumps.
Change-Id: I120f1f5ee54c965efe9ac0c7f40fdef56385f1fa
NOTE: this change depends on the kernel publishing /proc/$PID/stack
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | | |
into froyo
|
| |\ \ \ \
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Merge commit 'f9610b3842e030138c1dc327a3a467aaea02c227' into kraken
* commit 'f9610b3842e030138c1dc327a3a467aaea02c227':
Make the DUN apn data secure.
|
| | |\ \ \ |
|