* As per commit 11a113a67e ("Add disable_configstore").
[SebaUbuntu] Remove manifest entry as well
Change-Id: I5482989a8a96227a3e2a5317eacf613c641bfa8e
This CL moves mm_event and relative sepolicy
into common
Bug: 152414692
Test: build
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: Ie6d9c40f5fd2ac3f9abb86edc4d43baa88864f55
Power HAL start "on boot" trigger and we start processing hints on
boot_complete. The power start time and hint processing time different,
the reasons are both boottime and also availability of governors. The
notification of IPC is done by setting vendor.setup.power to 1.
This has been always the case. However there is new dependency in
surfaceflinger for Power HAL availability.
To workaround the dependency for early bootanim: bootanim =>
surfaceflinger => power hal, we could start Power HAL earlier by moving
from on boot to on late-fs here, as Pixel Power HAL doesn't need
anything in data/ partition e.g. neither persist property nor
configuration file.
Bug: 152131148
Test: build
Change-Id: I87d0b0ea32c86898f6bc19958d321ed177c2a739
Define CHRE_DAEMON_USE_SDSPRPC for wahoo since the daemon needs it to
be built properly now.
Additionally, the daemon's init.rc config is now included as part of the
daemon makefile so remove it from the device's init.hardware.rc.
Bug: 139693714
Test: compile
Change-Id: I0aaf7a3d965abeac63f4f62d743e655be3bebc09
This directory isn't actually used, and vendor_init shouldn't be
creating things in /data
Bug: 140259336
Test: Set up a hotspot, check logs for issues.
Change-Id: I923be96d69d783476cfb65acdeae063e1b4d4f87
Prefetching appears to have a slightly negative effect on boot time, and
actually makes boot time much worse when the available dm-bufio cache
shrinks. Since we anticipate the dm-bufio cache will shrink (because of
an increasing number of APEX dm-verity targets), disable prefetching
completely.
Boot time w/o this change: 12.085
Boot time with this change: 11.958
Boot time w/o this change with 128kB dm-bufio cache: 22.82
Boot time with this change with 128kB dm-bufio cache: 12.007
Test: atest google/perf/boottime/boottime-test
Bug: 136247322
Change-Id: I12e342c5692fa89855d9c217f2e94287ff5642a6
In Q, we added a new bugreport API that asks for user consent before
showing the "Share" notification for the bugreport. We will be migrating
all bugreporting clients to use the API in R.
In the new API workflow we are moving away from broadcasts and using
callbacks to communicate with dumpstate. Finished bugreport notification
broadcast used to share the final path of the bugreport but API now uses
file descriptors instead. Hence, moving away from broadcasts.
The full bugreport in this case can be retrieved from dumpstate directory
using 'adb pull' or finding and attaching the file directly to gmail or
betterbug.
Remove outputfile flag since it's unused.
Bug: 135186519
Bug: 137825702
Test: Build and flash to the device. Create a bugreport using combo
keys, share notification does not pop up. Full bugreport created in
bugreports/ dir
Change-Id: I3c15123a6a4ed62ae9cb87f5dd07db60b1416dfc
This is already handled in the rootdir/init.rc. There is no need for the
device specific .rc to do this again.
Bug: 135683539
Bug: 113174748
Test: Verified config store loading on reboot.
Test: Will resend for regression testing.
Change-Id: I434a573b33926419f16eeba654faced89aed9c43
ag/6722341 will set WLAN driver/FW when start legacy HAL.
The patch removes init.qcom.wlan.sh because it is not necessary
Bug: 127715974
Test: Property with wlan driver/FW version at enforcing mode:
It can be verified by the below command:
# adb shell getprop vendor.wlan.driver.version
# adb shell getprop vendor.wlan.firmware.version
Change-Id: Id94874cb96bc489a0f3eccfb97d780001b712330
Set stune.boost to 100 to boost process to big cores and prefer_idle to
1 to spread tasks. This saves ~370ms from kernel boot to boot_complete.
Before CL:
BootComplete : 10.046 0.067631
Post CL:
BootComplete : 9.6713 0.083226
Test: boottime
Bug: 80345258
Change-Id: I29159ba3102a23f302ddc2a2747879fd1ca39c27
Origin CLs that introduced these init.rc entries:
ag/2066998: wahoo: Create PDX socket dirs and cpusets for VR services
ag/2485419: Fix DVR cpusets for wahoo
ag/2645621: wahoo: toggle special touch mode when VR mode is active
Bug: 129787612
Test: Build walleye, taimen, walleye_xr, taimen_xr
Change-Id: I358689e73d2a214a9f3e90e106739dfe0fc2b6b6
Recently, I saw some of bugreports doesn't include mm_event dump.
dumpstate_board.txt says just permission error instead of dumping trace.
I could reproduce it with android restarting( shell$ stop; start).
The permission in pixel-trace directory is changed from
drwxr-xr-x 5 root root 0 2019-02-15 21:21 pixel-trace
to
drw------- 5 root root 0 2019-02-15 21:21 pixel-trace
Originally, 600 permission is buggy from the beginning because directory
needs execution permission bit to allow access the file. However, question
is why the permission is not set when the directory is created but does
android is restarted.
The tracefs in kernel seems to not support permission when the directory
is created. It just use 755 hardcoding if I parse it rightly.
https://elixir.bootlin.com/linux/v5.0-rc6/source/fs/tracefs/inode.c#L430
I also read mkdir script implementation(i.e., do_mkdir). It does fchmod
if it founds the file is already existing. That's why the restart changes
the permission to the one I wrote in the script.
Let fix it to set the permission to 755 for directory and 660 files
from the beginning so that it should work even though android restart
accidentally.
Test: confirmed it works device $ stop; start; host$ adb bugreport
Change-Id: I36305283c327b44e476c6eb39ec028ef271c304f
Signed-off-by: Minchan Kim <minchan@google.com>
/data/vendor/tombstones should be root which be define
in system/core/rootdir/init.rc.
Previous change (ag/4706914) lead wifi_hal cannot write files to
/data/vendor/tombstones/wifi.
Bug: 121294677
Test: device can boot up
Test: wifi_hal can dump data to /data/vendor/tombstones/wifi.
Change-Id: Id62ec21bc9a71018b03deba17c9befcd8d7b1c31
Signed-off-by: Roger Wang <wangroger@google.com>
Commit aosp/836840 changes permissions for accessing /dev/uinput. That
broke the folio_daemon.
This daemon is responsible for supportic magnetic folio cases on Pixel
2. We need to continue to support this operation.
Allow the folio daemon to access /dev/uinput by enrolling it into the
uhid group.
Note: this is not an sepolicy issue, but a permission issue.
Bug: 120306105
Test: adb logcat | grep uinput
Before the change, see a bunch of permission denials from folio_daemon.
After the change, not seeing anything in the logcat.
Change-Id: Idb33c8427d55b165f5aca2a68c09fa7e749fef57
Add new mechanism for stopping FP HIDL after several times init fail.
This prevents the case of FP HIDL keeping trying to do init process and
raising CPU usage when sensor totally dead.
After limited times init retry fail (default 10 times), FP HIDL will
be stopped.
init-fingerprint-sh is for stopping fps_hal after init retry fail
serval times.
It keeps running until max init retry or fps_hal running successfully.
vendor.fps_hal restarts until max init retry times fail.
Test: build pass and FP functionaily are good.
Test: init process will be stopped after limited times retry fail
Bug: 111710758
Change-Id: I8a19bdd351e5d712f8e23c6a0849acb1771e61e5
Signed-off-by: emilchung <emilchung@google.com>
This patch creates a pixel owned tracing instance apart from
main tracer(i.e., /d/tracing/instances/pixel-trace) so that
we will keep a certain mount of data without interference from
others(e.g., traceur, atrace and so on). It's important to not
lose the information to investigate problems at bugreport.
This CL also adds dumpstatez and bugreport property hooks to
stop/restart the trace during bugreport to keep more old trace.
Allow dumpstate read mm_event trace from /d/tracing/instances/
pixel-trace/trace. With that, it could dump the trace into
bugreport file.
Bug: 116825025
Test: confirm with adb bugreport/bugreport via power menu shortcut/
volume up/down/power key combination. They includes traces in
dumpstate_board.txt with kernel turns on CONFIG_MM_EVENT_STAT.
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: I699f362089b61247b2937accbd331327563b1e0c
All servicemanagers are started in rootdir/init.rc's `on init`
trigger, so there's no need to start them manually in device specific
rc files.
Test: boot
Change-Id: Ibdea8d5289322aae49af50e325beb793936ea525
This CL increase zram swap size from 512M to 1024M of p17.
It also increase swappiness from 60 to 100.
It has more benefit for overall system performance.
Detail is in the bug.
Bug: 117522738
Test: confirmed zram size and swappiness change manually
Change-Id: If75e47962915f6d4957e5fa9337e40dd6878fa65
Signed-off-by: Minchan Kim <minchan@google.com>
This was removed from the device in
I6fe5148d6b50b7c5706c09662a1ed0e7da4cb987.
Bug: 79551588
Test: Booted device and observed no relevant errors.
Change-Id: I35a114c10e8e116879ef2fd90487503805610c98
