GitLab

For better or worse, here we go...

Change-Id: Ic1150b59e4ebf34f06c689b2a1b10ae691a027bd

Change-Id: I3159a2a0c37589f9472aba83b699840356da33a7

On at least one device I've tested (htc msm8960), setting the
brightness after gr_init() is necessary for the splash to show.

Note that at this point in the boot process, the settings file has
not yet been read, so tw_brightness has its default value of max
brightness. When settings are finally loaded, the correct brightness
is loaded for the GUI.

Change-Id: Ifc58c1dc80ed9e6f6b2a269a9bb6764038626c84

If a device has several LUN but only one storage volume TWRP
recognizes (e.g. lun0 for microsd and lun1 for emulated cdrom), then
avoid mounting the same partition twice by checking the mount point.

Change-Id: Ie23b88acca1818873792e9f65b73b125a15e4a5d

Conditionally run Add_MTP_Storage() after wipe if:
1) is wiped successfully
2) is storage (already implemented)
3) mount succeeds

Previous to this commit, Add_MTP_Storage() was called before mounting
storage, which fails. Mounting storage right after wipe should not be
a problem since Update_System_Details() does it anyways (and doesn't
complain if already mounted).

Change-Id: I8a5a78d5ac9181f3a9464dfe6b77284458f9868b

Change-Id: I05d0e8516686ba2610ea4b437c83323e84eb4595

Change-Id: I949fe4bd99d2a4471fef3e3967980a6163943e71

- PS2: generic xml instead android xml
- PS3: formatting

Change-Id: I4c552e172d670278ab2bad1897ceb89b7ee7fec2

Change-Id: I06ab906ed94b1aaea35c32494880bf85d7564d4d

Seems that previous translator is overmind
Anyway, thanx him for initial translation

Change-Id: Ia98e344c24671cb60a0765e7c6dcb8aace6428fb

also correct typo in all language files
also remove dummy language files for ES and FI

german translation was done on omni crowdin by multiple translators:
https://crowdin.com/project/OmniROM/de#



result was updated in line with latest changes (as of 02032016) to en.xml


Change-Id: Iddd8dbee7e050833a4dc61174288514d408267f7
Signed-off-by: z31s1g <z31s1g@googlemail.com>

Developers and device maintainers may find it useful to have access
to logcat in recovery. This patch set adds the following build flags:

TARGET_USES_LOGD - This is an Android build flag that enables logd
support. Devices that don't have built in kernel logging to dev/log/*
will need this flag for logcat. We'll also use this to include the
necessary support files for logd in TWRP.

TWRP_INCLUDE_LOGCAT - This enables logcat support in recovery.

I pulled the init entries from my HTC One M8 GPE boot.img,
so I'm not certain whether these will work for all devices
or if they're all necessary.

Feedback is welcome.

PS2: Use "TARGET_USES_LOGD" instead as this flag already exists, and
previous flag was named incorrectly (logd isn't kernel logging)

PS3: Start logd service on load_persist_props action, needed for 6.0+

PS4: More info on "TARGET_USES_LOGD" flag as related to liblog
compilation can be found at the below links:

https://android.googlesource.com/platform/system/core/+/android-6.0.1_r10/liblog/Android.mk#27
https://android.googlesource.com/platform/system/core/+/android-6.0.1_r10/liblog/Android.mk#50

Whether or not this flag is needed for logcat in TWRP is dependent
on whether liblog was compiled with this flag.

PS5: Update commit message to better describe "TARGET_USES_LOGD" flag

PS6: Another commit message update

Change-Id: Iaac6c6c822dc93fbe4b6eadcf24eef6995dd6b50

if the image has the right magic bytes to be a sparse image,
use simg2img to flash the image

create a rule to make a fully dynamic simg2img which results in a
much smaller increase in gzip ramdisk size (2KB vs 40KB)

Change-Id: I1b0f6bc127da46103888b1154a9bddd8ac02c01d

Change-Id: I79d58fd680dd04161b89d42fed04a86a931defd3
Signed-off-by: Xuefer <xuefer@gmail.com>

Change-Id: I5d2d92f0d24228de9c63640d866e087542499d9d

Builder using a custom theme may have need for this.  Add a flag to
easily enable jpg support.

Change-Id: Ica74f8cb1312d3193105f2201a5cf8073e2edc82

Fix incorrect translation Again. Sync en.xml changes.

Change-Id: Icc9020095f7b795758457ba5a661c22a8ef13267

 1. ws fix
 2. typos
 3. use double-width Chinse punct

Change-Id: I561295c2e5562c59ce005459d1f178241130c6cd

sync with en.xml and update translations accordingly

Change-Id: Ic67b0496145c8a450c198520d7bb667dfe31f16d
Signed-off-by: Xuefer <xuefer@gmail.com>

Change-Id: I663f327585b4037eba62508a1f6484ca152bf3c5

fixes auto-generating backup name before editing the backup name.

Change-Id: Ied1c07b7dbdec9fa7fc80b3345970d95ac0ed1bb

While not all of these old build flags are active or implemented
yet (and they may not ever be implemeted until we find a device
that needs them), we need to make sure that the old build flags
are only applied when actually needed. Since there are a lot of
device trees that probably won't get updated due to lack of device
maintainers, we will rename the build flags and fix up devices on
a case by case basis.

Also added some pixel format related build flags to the make file
from AOSP so that AOSP devices should work in TWRP without
additional build flags.

Change-Id: I11ab475297d02b6aeffe89404fe50b4799a36be3

minor changes to the storage selection that was intrduced with commit 16373 (improve sdcard partitioning)


Change-Id: I50437111f45d0b7e2b78a655424daa63aea374cc
Signed-off-by: z31s1g <z31s1g@googlemail.com>

Change-Id: Ide3510d2efc1c1b39c756691776938e42424b61d

The driver already has the capability to do so.
It needs only to be flagged, if required.

Change-Id: I1d81b00a7499e493d1dbba0a440b45fc1202f7c1

list height now accomodates 4 entries


Change-Id: Ib5a5e2bad408f393abbd433b5f23a5d25711ca6c
Signed-off-by: z31s1g <z31s1g@googlemail.com>

Add script to compare string values between 2 language xml files
which will make it easier to identify strings that are missing
between the 2 files.

Move relink-binaries.sh to scripts folder and update it to handle
relinking 64 bit binaries.

Change-Id: Ia7a8bdbeea02256b3b864ab77e15912795275d33

Change-Id: I5deef665ab374491c0f498b498971abd525d1111

Change-Id: I5b4c3b90d579573536e9de2df5127160cdc9a10f

Fix permissions rarely fixed anything on more recent versions of
Android and usually made things worse. Instead we will replace it
with a more dumbed down option that should fix contexts on
/data/media with a few improvements to ensure that contexts get
fixed for multiple users and on adopted storage.

Change-Id: If5523781936a0b04196e2ad871cae767ebae2583

make it easier to add aditional resource files not just complete new theme

Change-Id: I6daca75929da03031812e66f25455e189b37a780
Signed-off-by: Xuefer <xuefer@gmail.com>

Change-Id: I417779259b08834d0bd9ec12ce31dda8c62d669b
Signed-off-by: cofface <cofface@163.com>
Signed-off-by: 996314227@qq.com
Signed-off-by: kaneawk <kaneawk@gmail.com>
Signed-off-by: Xuefer <xuefer@gmail.com>

Change-Id: I16f71797901ed21763b52a5cf750f383a460ce4d
Signed-off-by: sndnvaps <sndnvaps@gmail.com>

Doing it at display time is easier.

Change-Id: Ic0f2ca1f425f6267452157524a05b51d9324be16

Change-Id: Iebb5763277eec83fd6db4fdca8b7ecfd3c78dc6b

Secure block discard/trim was fixed by:
https://github.com/CyanogenMod/android_external_f2fs-tools/commit/6b39b93d83ab4ccb1913ecbc7a5a3e16766a011f

Once fixed, formatting using discard/trim takes a LONG time.  Other TWRP
formatting methods are already insecure.  It doesn't make sense for this
one type of partition to have secure wipe when none of the others do.

Change-Id: Ib5ad5a722895b0e0c7aa4e3af98b705e2574b762

Change-Id: I436bab6ef679168d3625d8e1837917077cf89908

Change-Id: Ibc4c4cc209c5f5f1a332fddcb450f983dc1a666a

Chances are there are not many themes in widespread use that are
using jpeg images, but this will be easy to revert back or even
just temporarily modify if we need jpeg support in a pinch.

Change-Id: If17b05ce3ebccce724fd74b26ed8ea91b287c3cf

Note: events.cpp is still old code renamed to cpp to make it
easier to call functions like gr_fb_width().

I had to modify AOSP fbdev code to provide a separate memory
surface for drawing to as drawing directly to the framebuffer
resulted in rendering taking about 5 times longer.

I also modified AOSP adf code to provide a separate memory surface
for drawing for the same performance reasons. The Nexus 9 supports
adf graphics.

Overlay graphics work on at least one device. Overlay provides a
separate memory buffer already so performance is good.

I do not have a drm device yet that I know of. I made some attempt
to update the drm code to determine the correct pixel format based
on the drm graphics format, but what is available in pixel flinger
and what is available in drm do not line up all that well. Reports
are that the Pixel C is using drm graphics, but performance is
slow, likely due to the use of a mmap instead of a memory buffyer.

Change-Id: Ibd45bccca6ac2cb826037aa9b2aa5065cf683eed