These are permissions that an application can request, but won't
normally be granted. To have the permission granted, the user
must explicitly do so through a new "adb shell pm grant" command.
I put these permissions in the "development tools" permission
group. Looking at the stuff there, I think all of the permissions
we already had in that group should be turned to development
permissions; I don't think any of them are protecting public APIs,
and they are really not things normal applications should use.
The support this, the protectionLevel of a permission has been
modified to consist of a base protection type with additional
flags. The signatureOrSystem permission has thus been converted
to a signature base type with a new "system" flag; you can use
"system" and/or "dangerous" flags with signature permissions as
desired.
The permissions UI has been updated to understand these new types
of permissions and know when to display them. Along with doing
that, it also now shows you which permissions are new when updating
an existing application.
This also starts laying the ground-work for "optional" permissions
(which development permissions are a certain specialized form of).
Completing that work requires some more features in the package
manager to understand generic optional permissions (having a
facility to not apply them when installing), along with the
appropriate UI for the app and user to manage those permissions.
Change-Id: I6571785c6bb5f6b291862b7a9be584885f88f3a5
Pre-focusable in touch mode ? cursor moves to tapped position.
or previous position when using d-pad/keyboard.
Change-Id: Iac725ff233bfeac2dc14e870118047a9a8418ff9
When we encounter youtube <embed> objects, we replace them on the fly
with an element that will redirect to the youtube application.
Currently, this element is a canvas, that we add to the document wrapped
into a Frame. This cause some problems when we switch to have canvas
elements on their own individual layer (which drastically improves
performances). Note that we do support correctly composited layers
into frameset/iframes on normal websites, the problems we see here
are due to us creating the frame on the fly, messing with webkit's
compositing logic.
This CL rewrite the HTML code we insert to not use canvas and instead
use normal html elements positioned via CSS. This work around the
composited canvas issue as well as simplifying the code.
Change-Id: Ie6043f9445e8bc191b229db9f9ff5de192d8b5db
1. Added methods to the ActivityManagerService remote interface
that allow accessing content providers outside of an application.
These methods are guarded by an internal signature protected
permission which is given to the shell user. This enables a
shell program to access content providers.
2. Implemented a shell command that takes as input as standart
fagls with values and manipulates content via the content provider
mechanism.
Change-Id: I2943f8b59fbab33eb623458fa01ea61a077b9845
Since CDMA doesn't use APN settings there was no place to say what a cdma
device's DUN connection would support, so by default normal device
originating traffic would be blocked on a tethering single-connection device.
With this change you can (via overlay) say that it supports everything
so mms and on-device browsing/email will still work even when on a dun connection.
The reason to allow both: some carriers will charge per byte for dun access
and so they don't want lots of non-tethering traffic used (costs the user alot)
but other carriers just use a dun connection to limit access to tethering, but
once there give unlimited data, so it makes sense to support everything there.
bug:5972599
Change-Id: I78fd7f3ac63c51a0560b659ed5ec219b10a93f8d
Improving load time by:
- using window animation for fade-in and not
waiting to create HW layer
- starting loading of thumbnails/icons earlier
- only initially creating views for the first
screenful of items
- recycling views
Change-Id: I529b1085fe35d81aaafeb7433ccaed8e0537f01c
