Improve location / timing of vibration
Split out vibrate settings for buttons, keyboard, and long actions
Change-Id: I282825cc5f3e44ed6dcabe65dc1f4cb21b407b67
Example: f2fs on Moto G needs fsflags="inline_xattr" in the stock
ROM but the Google Edition uses ext4 which fails to mount with that
option.
Change-Id: I01bce214e7f15e43e66ac35729fd3521609ffad3
Do a restore of loaded file contexts to /data/media directory. This will help denials to be prevented when internal storage is wiped.
Change-Id: Ie49bbfa48d2f3ee4f08376d9c1877b92c051017c
* The difference isn't as big as there are not many big non-transparent
bitmaps in TWRP, on install screen on flo it is about 5-10ms better.
Only place where the difference is noticable is keyboard, which is
pretty big non-transparent bitmap, where it speeds up the render
by ~40ms on flo.
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
Change-Id: I4c51ef957ae2a1829ada4eb566e9964f708efcf0
* This makes the rendering several times faster, because the giant
rectangle used as background no longer uses expensive blending
calculations, and there are also many other big rectangles which
don't need it (fileselector, ...).
* Results on hammerhead:
- WITHOUT the patch - scrolling in fileselector on install page:
I:render 67 ms, flip 6 ms, total 73 ms
I:render 82 ms, flip 6 ms, total 88 ms
I:render 81 ms, flip 6 ms, total 87 ms
I:render 80 ms, flip 5 ms, total 85 ms
- WITH the patch - scrolling in fileselector on install page:
I:render 32 ms, flip 6 ms, total 38 ms
I:render 16 ms, flip 6 ms, total 22 ms
I:render 16 ms, flip 7 ms, total 23 ms
I:render 18 ms, flip 3 ms, total 21 ms
I:render 18 ms, flip 2 ms, total 20 ms
* On flo, the results are even more noticable - 160ms -> 40ms
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
Change-Id: I5685763ba21745d7cd93133adf5f0bcb4c9a581f
Use intptr_t/uintptr_t to cast between pointer and int to allow
building with -Werror=pointer-to-int-cast and
Werror=int-to-pointer-cast turned on.
Cast to char* instead of unsigned int for pointer arithmetic.
Change-Id: Ia862306fdcca53866b330e8cf726f3d62f2248a0
Eliminate the use of tarDirs and Generate_MultipleArcives in
favor of Generate_TarList so that we have one method for backup
creation instead of three.
Change-Id: I267937b6e40b32d43fbac8b4cca82f7468d4f94c
* Some devices rely on the LCD backlight to blank/unblank the display,
support them by allowing a custom LCD backlight path to be used.
Change-Id: I8406b4b55cd7a2afc4f8f8ba65de2c53b949489d
Some kernels require the usb functions be defined before UMS mounting
of storage partitions will work. This sets the sys.storage.ums_enabled
property upon mount/unmount which can be listened for in init.rc.
Example routines to include in init.rc:
on property:sys.storage.ums_enabled=1
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/functions adb,mass_storage
write /sys/class/android_usb/android0/enable 1
on property:sys.storage.ums_enabled=0
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/functions adb
write /sys/class/android_usb/android0/enable ${service.adb.root}
Change-Id: I8a8ad4b392abbaa173d402714bcb4049ba84ccca
When adbd runs as root, it should transition into the
su domain. This is needed to run the adbd and shell
domains in enforcing on userdebug / eng devices without
breaking developer workflows.
Use the new device_banner command line option.
Change-Id: Ib33c0dd2dd6172035230514ac84fcaed2ecf44d6
In kernel(3.10) USB ADB gadget driver is removed.
Using Functionfs for USB adb gadget.
Android recovery uses a stripped down version
of adb command for sideload only. It's missing
the ffs function support, so add the ffs
support to allow sideload command to work
b/12608946
Change-Id: I4ad024723dfc5bdb544548391f99637c390b171e
Signed-off-by: Pierre Couillaud <pierre@broadcom.com>
uncrypt can read a file on an encrypted filesystem and rewrite it to
the same blocks on the underlying (unencrypted) block device. This
destroys the contents of the file as far as the encrypted filesystem
is concerned, but allows the data to be read without the encryption
key if you know which blocks of the raw device to access. uncrypt
produces a "block map" file which lists the blocks that contain the file.
For unencrypted filesystem, uncrypt will produce the block map without
touching the data.
Bug: 12188746
Change-Id: Ib7259b9e14dac8af406796b429d58378a00c7c63
Changes minzip and recovery's file signature verification to work on
memory regions, rather than files.
For packages which are regular files, install.cpp now mmap()s them
into memory and then passes the mapped memory to the verifier and to
the minzip library.
Support for files which are raw block maps (which will be used when we
have packages written to encrypted data partitions) is present but
largely untested so far.
Bug: 12188746
Change-Id: I12cc3e809834745a489dd9d4ceb558cbccdc3f71