Open
Conversation
…eystone-qcom-release Change-Id: Ice2ea948345550e3e9c70a9fb4c362ae8a446f15
…eystone-qcom-release Change-Id: I41247988cec8b9af71bde59b8b2c946c13ec2df8
…eystone-qcom-release Change-Id: I86ff239b823b6b999f5c05559a92b723020c34bd
…eystone-qcom-release Change-Id: Ibfbe6d3605cb4044401d876b7fdd6e879c197cbd
…eystone-qcom-release Change-Id: I158bb5a97e59810dcbf0bd460c0a4cc5f84e77a9
…eystone-qcom-release Change-Id: I8bb15db492543c7e3f2663700a86a7c016856ebf
…eystone-qcom-release Change-Id: I071645568166773d69e1758a6a9126ecef3e96a9
…eystone-qcom-release Change-Id: Ifafa8acd409781ea3624717a6fd77b109f06c100
…eystone-qcom-release Change-Id: I71d7db727149f3b74da4d0b5e85b1c9d88cf0416
…eystone-qcom-release Change-Id: I12d4facbfc597873a3622cea2e60e4017cf59d1e
…eystone-qcom-release Change-Id: I7520e51810595f4a2b291c583f6dfd4922dc28cc
…eystone-qcom-release Change-Id: I5b1b068adf7961bae5694113ad7081cbb820802f
…eystone-qcom-release Change-Id: I2801763cea619b6616b97f02182fa2a78131a295
Change-Id: Ie1086cfd5d6a9e5792fc9744d2f39567ab3f67c2
…eystone-qcom-release Change-Id: Ibc4a657f930a9ed1f214e685c9715a03ecea0cc4
…eystone-qcom-release Change-Id: I5cb731c76db50c3635e7f0db2dcd3f11da5fa6f1
Change-Id: I414ce6e0c04eea5d40758bcf89462f6280e6418c
…eystone-qcom-release Change-Id: I3b0129eba00e7cceee8407a9627fda76218aefc1
…eystone-qcom-release Change-Id: I914f24ee218643d660a1f565819d24ebf4f3c032
…eystone-qcom-release Change-Id: I30598903fae30697761e102244c23010d093179e
Change-Id: Ifb40e488df702a947de4cdf0e919ba4b9d7b3fa8
…eystone-qcom-release Change-Id: I539b53f4172044a359a1187a5b488991b86f62b0
…eystone-qcom-release Change-Id: Ia4c60b91a88f49fb50f63283f2ae9b0f46d8661f
Change-Id: I25b5caa7ffe668a80e440cd6aff3eb2542ac8ade
…eystone-qcom-release Change-Id: I3df70660bf687aa8782c967c5c570841592708f6
Change-Id: I9a3389ffceaf79948792e3d2a8475a8397f9ec3d
…eystone-qcom-release Change-Id: Ib312684cb0e201095498e99b0f77ed87c0ee73e0
…eystone-qcom-release Change-Id: I52fda5243496c93f68366e92d8193c5de111a522
…eystone-qcom-release Change-Id: Idedb9d680f429cf59ee5e519dba9082a97713922
…eystone-qcom-release Change-Id: Ibe8d651a0d9840b1ad30f98f5e41f41439b1b9fd
…eystone-qcom-release Change-Id: I32ce1394af0a17f80926aca18cf9ad0743a3d44a
Change-Id: I0697c2c96bab7797104144a064b06618dbe7124d
Allow optional vendor-specific initializations within init. This can be used for runtime initialization setup that init rc scripts do not support. Change-Id: I7623a0d59b18f9ec8e3623958e2f7ccd72b877bf
Change-Id: I99d6884b98e537a58150e2791a0dfc7b99fd2d39
HVDCP_3 is a high voltage DCP charger where the charger's voltage can be changed by issuing pulses on the D+/D- lines. Add support to recognize it and treat it as an AC power source. Change-Id: Ib719529904e8b7a676bbdc5f5953f0f9da6df3fa (cherry picked from commit e9b949ddb926a52cc256dbd8cae2c4b835656c3c)
Booting up the device without usb, the kernel sets the usb power supply type as UNKNOWN. The type of usb power supply changes at run-time as various chargers are plugged in/out. However, healthd initilizes the charger list only at bootup. Change it such that it checks for charger type changes with every battery or usb uevent. While at it, the kernel may have a power supply type which is not known to healthd. This is perfectly fine. Update healthd to not print a warning. Change-Id: I2ec9f9a420ca61814d43c316b418ce94de3691bc (cherry picked from commit 282857e89d591b6704e5d69ec2ae1e53a5de74cf)
Change-Id: Ie422840c85c247cba866c370ce8d970058df2c2f
Change-Id: Ie1ca5018c465f6b2c15cbc00bdf3bb866d98ddef
[Adrian DC] Preserve the log while permissive Change-Id: I3f2887930e15d09014c2594141ba4acbbc8d6d9d Former-commit-id: fa9542f0bb4ac8c3da3c0e240a4f9f39e85221cb Change-Id: I03e442859d458ca6badc56d69cf72b75c5035cf4
The sysfs node of sd blk_device is /sys/fs/f2fs/sd-<num>, we shouldn't skip partition number at this time. Bug: 189257443 Test: access sd-<num> sysfs correctly Signed-off-by: Guo Weichao <guoweichao@oppo.com> Signed-off-by: Huang Jianan <huangjianan@oppo.com> Change-Id: Ibcd7bb265f8fca9cd26f8770403f1bafad433acb
Sometimes we need to override ro.* properties by using our vendor init extension. Previously there was a security check which was blocking that. To resolve the issue, we need to weaken the security check during the execution of our vendor init extension. This is safe because the vendor init extension gets executed as part of init construction and it is considered a trusted system component. Change-Id: Ia7d60686968695f1fb43be4ed58770ce10da88c5 Former-commit-id: 91d12168b9500a44211a7d5a092e0ebcfed48d4d Change-Id: I07629b6c19b5ebfa019307c497c18d8bcc719685
Doing this in the userspace allows more properties to be spoofed and eliminate the needs for a hack in the kernel. Former-commit-id: e036a461c7dd4d97e1df77979c85f3c198e1e784 Change-Id: I76f6e210247a032b764dea2f5a23a184745f59a0
aswinas@pixysos: add some more props from magisk hide to userspace hack by arter97 Former-commit-id: fc79269db601c9cd0dad3781d4e6ee8f209c55fc Change-Id: I8a88862674ca5a9eb8df5050e04344a2acb0a79f
Change-Id: I740afaa27de82bec1e6d58b58d431141ca6b4e3f Former-commit-id: ca62a22d017f44c9f63553a44f5017eb5b8e9095 Change-Id: Icea7076c6c0ffc2ab3d66899335a5a477ccc519a
Change-Id: Ic07539b4a7a97316720defd000425d1b6d15fd67 Former-commit-id: 9d4ca9403943feecd6f902e69d581aad3ee84839 Change-Id: Ic34d95c23afd8caf95c7b2a2517650dbf116fdde
Also reformat code Change-Id: I98aafcc2c1d8dae1448ecf3c18981fb7945599ba
Signed-off-by: Jarl-Penguin <jarlpenguin@outlook.com> Change-Id: Ib6d3808c3b8f3e0cffab685a24d3cdd436b0fe9b
This can have a major impact on performance. We don't want this, even on userdebug/eng builds. Use the new property "ro.console.enable" to enable the console service explicitly. Change-Id: I93e7c65e92261443d1c9c70cfef9aa2ed5ff328a Signed-off-by: Alex Naidis <alex.naidis@linux.com> Signed-off-by: Jason Edson <jaysonedson@gmail.com> Signed-off-by: Akash <akashniki@gmail.com>
When opening and closing activities in Settings, a measurably significant amount of CPU time is spent processing and logging stats events in statsd: 0.02% /apex/com.android.os.statsd/lib64/libstatspull.so @plt 0.01% /apex/com.android.os.statsd/bin/statsd @plt 0.01% /apex/com.android.os.statsd/bin/statsd SocketListener::runListener() 0.01% /apex/com.android.os.statsd/bin/statsd android::os::statsd::LogEvent::parseBuffer(unsigned char*, unsigned long) 0.01% /apex/com.android.os.statsd/bin/statsd android::os::statsd::LogEvent::parseAnnotations(unsigned char, int) Over longer device uptimes with real-world usage, statsd uses a substantial amount of total CPU time. We have no use for the stats recorded by statsd, so disable the service entirely to save CPU in potential hotpaths. This is the system/core part of the change; changes to frameworks/base are also required. Test: simpleperf record -a; verify that statsd no longer appears in sample hits Change-Id: Idf6fdb0eff987169bd5f370dd72315e831a669e6 Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
It is only intended for performance analysis and can impact I/O throughput. Change-Id: Ia7d3a449d52625d911e2cea16249972d01e5cfcf Signed-off-by: Adithya <gh0strider.2k18.reborn@gmail.com>
This allows remount to gracefully mount /system when Magisk is installed. As a sidenote, the ro.debuggable property check can safely be removed due to the simple fact that CPP preprocessor flag ALLOW_ADBD_DISABLE_VERITY=1 is passed when building userdebug/eng. Change-Id: Ic10eccbf5d225468c3dc42f8ae3ae7c05b49a699
/sys/class/block covers all of dm-[0-9], sd[a-z], mmcblk[0-9].
Use it instead of /sys/devices/virtual/block, which only covers dm
devices.
This allows f2fs tunings to be applied more reliably regardless of
how the userdata partition is set up.
Test: Confirm entries under /dev/sys aren't dangling and cp_interval,
gc_urgent_sleep_time, iostat_enable and discard_max_bytes are
all set up properly under FBE, FDE and unencrypted.
Change-Id: I089af5bc068445f33919df6659671e50456d49f9
Signed-off-by: Juhyung Park <qkrwngud825@gmail.com>
Current code is not portable beyond SCSI devices (e.g., UFS). For example, eMMC and NVMe devices fail due to their extra postfix. Change its logic to rewind each character until "queue" directory appears. Test: Confirm md0p1, sda20, nvme0n1p3, mmcblk0p3 are all handled well. Change-Id: I585ccf2d4a72f6ef8ecb203acdd72a1e32d3e749 Signed-off-by: Juhyung Park <qkrwngud825@gmail.com>
:) This pulls in quite a few things into a lot of processes. Removing it separately, in case the use of SetTaskProfiles needs to be reverted, removing this as well might cause that revert to have linker errors if new static users of libutils are introduced in the meantime. Bug: 208895940 Test: build Change-Id: Iaf5b5d41328c1b1f50bb32be8a6a1bd3a0c3f22f Signed-off-by: Akash Srivastava <akashniki@gmail.com>
Threads should always be in the same state as their parents. This also implies that the additional SetTaskProfiles is unnecessary when creating a new thread. Test: boots, TH Bug: 208895940 Change-Id: Id971c6e87d342a695bea106cdd258bc0ef6f7ecb Signed-off-by: Akash Srivastava <akashniki@gmail.com>
With our recent change 0455a2c39c781a8153c1090a4638193b4181379d, there's some logic that can be simplified to make this slightly easier to read. This CL does not change the behavior of this code. Bug: 208895940 Test: TreeHugger Change-Id: I4de2dbaf4406cbb7785df8839bb3ae453186ea69 Signed-off-by: Akash Srivastava <akashniki@gmail.com>
* In recovery we need to be able to edit the block device after it's been mounted. This allows, for example, to wipe system after mounting it Change-Id: Ie536d275643e9d6063bba789e4cd2fa2671fc8fa
Change-Id: I4e64c6d3951dac4a424617d8fdf6d37962d3b4f2
This reverts commit 29dd6b6c01295222fee5ef2fc70692b2ecb12504. Change-Id: I7b76cd920019ae8cb7270b3f83e777ea9de7f7a4
Change-Id: Iaf5eb813e848ef05b1b455ebfe3643f4a8b4f80d
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.