Instead of using a series of booleans, create a single flags integer
that contains all of the dexopt options.
Change-Id: Ia8fa968f64b164267f43dd29cea9dc0413058125
Propagate the boot status explicitly to installd so that we do not
have to rely on dev.bootcomplete, which isn't meaningfully set
when the device needs the decryption screen on boot.
Bug: 23898216
(cherry picked from commit 06bb908b78e3c790d3db52fef9f2ab0a129e53cd)
Change-Id: I9b34298caf70b1e5d40970cc0d04c469016a80a7
This became dead with the removal of support for the non-runtime-init
code path in f48029f00a66e23d7872a00b56fbcf88528ba476.
Change-Id: Id68e0da4658e83f0d3bfd8645152165faacac5fa
If the id is negative, it is not from Resource.
Passing the negative value to getResourcePackageName makes AssetManager dump unnecessary warning logs.
It is reasonable not to get package/type/entry information for the negative id.
The warning logs :
W/ResourceType( 3711): No known package when getting name for resource
number 0x9b010100
Change-Id: Ic89acb4f32205ba5a2fdac61dc14b00ccf251148
This has been moved into its own repository at
//system/tools/aidl
Test: Built aosp_arm-eng from scratch.
Bug: 23691099
Change-Id: Ic45d55682b9dcafe894efe0a6317792f9c1236c6
After boot when status bar donot have any notification, the
overscroll is rubberbanded , changes have been done to fix
this and make the behaviour consistent with other scenarios.
In NotificationStackScrollLayout when there is no childview
present at the touch coordinate, initialization of some
variable was not done which was resulting into overscroll
being rubberbanded.
Usecase of the issue:
1. Reboot the phone.
2. Make sure that no notification is present
3. Pull the status bar.
4. Now pull the "No notifactions" view ,the overscroll
is rubberbanded
5. Get some notifications, pull the status bar and then
the notifications, the overscroll is not rubberbanded
6. Remove all the notifications, now pull the statusbar
and then pull "No notifications" view the overscroll is not
rubberbanded.
Change-Id: I06d4f0e3d6ed980744be21b9fd7ed307dca69ca3
Signed-off-by: Jayasri bhattacharyya <jayabhatt@codeaurora.org>
This is attempting to fix build breakage caused by redefining the isatty stub
for win32.
Change-Id: I5f854934cb9d2b2981f6349045e85d9ad737aa77
Signed-off-by: Casey Dahlin <sadmac@google.com>
Bug: 22926131
This is the documentation update corresponding to our new named
structures for RS object types.
Change-Id: I282ce78192da7c9f68951ce05100819a306694f0
We have to step up to a GLR parser to do this without exceptions (for no
reason other than Bison happens to use exceptions for the LALR(1) template and
not for the GLR one), but this should let us smooth out integration going
forward.
Change-Id: Iff44662914b4a65dfa5612d07c3a1ede07e6e4a9
Signed-off-by: Casey Dahlin <sadmac@google.com>
We're flipping Flex/Bison in to reentrant mode, cutting down on global
variables, and exposing a more C++-like interface earlier. This is the first
phase. There's still a couple of weird hacks to deal with the previous code's
reckless disregard for scope sanity, but the outline of things to come is
starting to appear, and this CL really doesn't need to get any bigger.
Change-Id: Ife2d70db026d7ab1319bdf6c586959315666d0bb
Signed-off-by: Casey Dahlin <sadmac@google.com>
