summaryrefslogtreecommitdiffstats
path: root/core/java/android/os/Binder.java
Commit message (Collapse)AuthorAgeFilesLines
* Add Binder.getCallingUserHandle().Dianne Hackborn2012-09-071-1/+13
| | | | Change-Id: I2a7eedfdc7baeeb4c2cd2ca0153aa95e0cf0bf45
* Remove Binder.getOrigCallingUid().Dianne Hackborn2012-08-311-28/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | Replaced all remaining places that used it with explicit user specification. While doing this, I ran into stuff that was creating PendingIntent objects (that now need to specify the explicit user they are for), which are also posting notifications... but have no way to specify the user for the notification. So the notification manager in the system process now also gets a formal concept of a user associated with the notification, which is passed in to all the necessary aidl calls. I also removed the old deprecated aidl interface for posting/cancelling notifications, since we now always need a user supplied. There is more work that needs to be done here, though. For example I think we need to be able to specify USER_ALL for a notification that should be shown to all users (such as low storage or low battery). Along with that, the PendingIntent creation needs to be tweaked to be able to handle USER_CURRENT by evaluating the user at the point the pending intent is sent. That's for another change, however. Change-Id: I468e14dce8def0e13e0870571e7c31ed32b6310c
* Rename UserId to UserHandle.Dianne Hackborn2012-08-161-2/+2
| | | | | | This is the start of turning this into a formal public API. Change-Id: I5786d2c320f1de41a06ed5d0f65adb68967287a0
* docs: fix broken linksScott Main2012-08-061-1/+1
| | | | | | and update sitemap text file Change-Id: I6982c3f029c46135ae856b8484d906c2882bad3a
* Multi-user - 1st major checkinAmith Yamasani2012-02-031-1/+30
| | | | | | | | | | | | | | | Switching activity stacks Cache ContentProvider per user Long-press power to switch users (on phone) Added ServiceMap for separating services by user Launch PendingIntents on the correct user's uid Fix task switching from Recents list AppWidgetService is mostly working. Commands added to pm and am to allow creating and switching profiles. Change-Id: I15810e8cfbe50a04bd3323a7ef5a8ff4230870ed
* Clear reply before writing exception.Jeff Sharkey2011-12-141-0/+3
| | | | | | | | | Changes Binder.execTransact() to clear any partial reply before writing the exception. Specifically, this fixes case where an onTransact() could leave a writeNoException() floating in the reply. Bug: 5686023 Change-Id: Ibc944464a010f5ec2fd8ef3cc84ac23d8260a491
* Remove the deprecated things from Config.java. These haven't been working ↵Joe Onorato2011-04-071-3/+2
| | | | | | since before 1.0. Change-Id: Ic2e8fa68797ea9d486f4117f3d82c98233cdab1e
* Improve activity manager debug dumps.Dianne Hackborn2011-04-071-0/+33
| | | | | | | | | Activity manager now does all dump requests into apps asynchronously, so it can nicely timeout if there is an app problem. Also lots of general cleanup of the am dump output. Change-Id: Id0dbccffb217315aeb85c964e379833e6aa3f5af
* Fix binder proxy death notice trackingChristopher Tate2011-03-011-0/+1
| | | | | | | | | | | | | There was an issue with stale recipient tracking when BinderProxy weak references had been purged and a new proxy object allocated for a still-live underlying IBinder. The death recipient bookkeeping has now been reworked so that it's fundmentally tied to the BinderProxy instances, not maintained as global state, to prevent this sort of confusion entirely. Bug 3499939 Change-Id: I75c5216b6d53b90868ac969e32c9725201e51be3
* am d34c1495: Merge "Prevent system crash when OOM in Binder thread."Jean-Baptiste Queru2010-11-171-0/+4
|\ | | | | | | | | * commit 'd34c1495020e5d72dd18959fb906375dc0874c04': Prevent system crash when OOM in Binder thread.
| * Prevent system crash when OOM in Binder thread.Mattias Petersson2010-11-051-0/+4
| | | | | | | | | | | | | | | | | | | | | | When handling large images during an update of a widget, we can run out of memory in the Binder thread. This will cause an OutOfMemoryError to be thrown. When an Error is thrown in the Binder thread, the entire system will crash. This was fixed by catching this OutOfMemoryError and instead throw a RuntimeException to keep the system alive. Change-Id: If27199676c6f8aef23fb249be1197ca5dfe0fe99
* | Fix StrictMode for Binder.dump()Brad Fitzpatrick2010-07-261-1/+11
| | | | | | | | Change-Id: I378f5e3d6512d06b46248b9bb6d9c727e3f6bf1d
* | StrictMode: gather and return violating stacks in Binder repliesBrad Fitzpatrick2010-07-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | Now, when Thread A has a strict mode policy in effect and does a Binder call to Thread B (most likely in another process), the strict mode policy is passed along, but with the GATHER penalty bit set which overrides other policies and instead gathers all offending stack traces to a threadlocal which are then written back in the Parcel's reply header. Change-Id: I7d4497032a0609b37b1a2a15855f5c929ba0584d
* | More StrictMode work, keeping Binder & BlockGuard's thread-locals in-sync.Brad Fitzpatrick2010-07-151-1/+24
|/ | | | Change-Id: Ia67cabcc17a73a0f15907ffea683d06bc41b90e5
* Clarify some Binder docs regarding things that are thread-local.Brad Fitzpatrick2010-03-251-8/+9
| | | | Change-Id: I433c9c2f4593866b2e9846893676b93a670817d4
* auto import from //depot/cupcake/@135843The Android Open Source Project2009-03-031-0/+355
|
* auto import from //depot/cupcake/@135843The Android Open Source Project2009-03-031-355/+0
|
* auto import from //branches/cupcake/...@130745The Android Open Source Project2009-02-101-11/+33
|
* Initial ContributionThe Android Open Source Project2008-10-211-0/+333
generated by cgit v1.1 at 2025-03-23 01:55:17 +0000