Age | Commit message (Collapse) | Author |
|
Otherwise we run into following error on post Android 13 builds:
"init: Control message: Could not find \
'aidl/android.hardware.wifi.supplicant.ISupplicant/default' \
for ctl.interface_start from pid: 322 (/system/bin/servicemanager)"
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
Change-Id: Ib73738bbc5fb6665e68237502d9128ccee85315d
|
|
Reuse Cuttlefish's suspend blocker service to avoid
suspending the device while running CTS tests.
This is actuallly a cherry-pick of Amit's change on db845c here:
https://android-review.googlesource.com/c/device/linaro/dragonboard/+/1723130
The problem is that "adb shell stop" is causing a PM suspend and
subsequent loss of adb connectivity. The problem could also be reproduced by
the vts ltp test.
Test: booted to homescreen with hikey and hikey960 board,
and adb shell stop does not cause suspend any more
Signed-off-by: Yongqin Liu <yongqin.liu@linaro.org>
Change-Id: I290faa5182135a619c4053d12a88a2d534641d7f
|
|
This fully enables metadata encryption on hikey960 by following
the instructions here:
https://source.android.com/security/encryption/metadata?hl=en
Mostly just adding --early/--late mountall arguments in the
init.rc and the "latemount" and
"keydirectory=/metadata/vold/metadata_encryption" options to the
userdata fstab line.
Note: You will likely need to flash new userdata (and possibly
reflash metadata as well) after applying this. Use the flashall
script if you are having any trouble.
Test: atest vts_kernel_encryption_test
Reported-by: YongQin Liu <yongqin.liu@linaro.org>
Signed-off-by: John Stultz <john.stultz@linaro.org>
Change-Id: Idd57774ac21ca1535259e679fc92f127e1e710e0
|
|
am: 6aa7c17f1b
Change-Id: Ie6d66488f87394c30eb4888a341dbab14c83b6ef
|
|
This reverts commit ad4b0cc47f80b71e2bc58a31f775332c5626b369.
We seem to only see errors about pdx sockets and I'm not sure
we have any actual VR users, so I think its safe to drop these.
Change-Id: I724984e3dd961f7989e1c3d22dcfe198777ac418
Reported-by: Robert Foss <robert.foss@collabora.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
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: I380e11d6494d7241f2911df4bd2e1c50395195f2
|
|
We recently added a workaround for for an adb/ffs crash:
https://android-review.googlesource.com/c/device/linaro/hikey/+/930268
Which due to other changes is no longer sticking. Using
PRODUCT_PRODUCT_PROPERTIES is the preferred way to set properties
so switch to code to do that.
Change-Id: I330131f29c51acc6027885300bce5346053c94ca
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
Instead of conditionally compiling hwcomposer.drm for hikey and
hikey960, compile two different modules and selectively use them
on hikey and hikey960.
Bug: 122332597
Test: none
Change-Id: Ifcb64798bc34101d9e1f851454c3fe361c478c12
|
|
Recent changes to adbd have enabled nonblocking_ffs by default.
These have seeminly uncovered some bad memory corruption in the
kernel ffs gadget driver on every kernel I've tried so far.
Unfortunately I've not been able to diagnose what is going wrong,
so for now, lets disable the nonblocking_ffs.
We still need to root cause the issue as its a problem even with
the mainline kernel on HiKey, so its likely a generic kernel issue.
Change-Id: I7a0797cc9e8e5f263e533beea23642f768c0f017
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
Changes:
- Add a hikey960_tv-userdebug lunch target.
- Add a hikey_tv-userdebug lunch target.
- Use the TvSampleLeanbackLauncher to replace Launcher 3.
- Removed navbar and notification bar.
- Increased DPI to 260
- Added TvSetting to replace Settings
- non tv targets remain unaffected.
Minor Issue with AOSP TV:
- WiFi connection UI doesn't have a "next" button.
To be able to connect we have to use third-party apps
- hikey boots to UI with kernel 4.4 or less
Test: Builds and boots to Leanback Launcher UI
Change-Id: I43fa609f486bfa71482b62bf36dff15bcd46647c
Signed-off-by: Sahaj Sarup <sahaj.sarup@linaro.org>
|
|
The eBPF trafficController in netd need as least 8MB memlock rlimit to
run properly due to the size of eBPF maps. To make this feature
avalaible on hikey, the rlimit is set to 8MB for all processes.
Bug: 70945407
Bug: 79938294
Test: dumpsys netd trafficcontroller doesn't show errors
Change-Id: Ie0b4ceb889a838dd5b0ddb1630d28811f6ddc983
|
|
Modifications needed to enable the drm_hwcomposer in
the hikey build.
This enables drm_hwcomposer for 4.14+ on HiKey and HiKey960
This requires updated drm_hwc source and changes to the kernel
source and 4.14 kernel prebuilt to be updated (and merged
together with this change).
So DO NOT MERGE until pre-built kernel which incldues
the following commits is submitted:
https://android-review.googlesource.com/c/kernel/hikey-linaro/+/743923
As well as the following update to drm_hwcomposer:
https://android-review.googlesource.com/c/platform/external/drm_hwcomposer/+/743902
Bug: 62066689
Change-Id: Ifbe76eed77672d06ceb3bce16de4b4d8cac56f17
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
am: 2d8fb579d5
Change-Id: I7c312754b2ec6d5f0094b04a6a6bfbbe395e07ae
|
|
watchdogd is now removed from init and treated like any other system
executable.
Bug: 73660730
Test: watchdogd still runs
Change-Id: I4b1cf0b39933fa6c60948c0d977fef6c0e112703
|
|
am: 531fb4c307
Change-Id: I15f95c5413fecb009c95f414c1e6c0effbd91dfc
|
|
When we moved the fstab files over, we probably shouldn't have
copied them to /vendor/etc/init/ and instead used /vendor/etc/.
Thus this patch corrects this.
Change-Id: I2143fb6596d50289701158b58c91dfb440943231
Reported-by: Mark Salyzyn <salyzyn@android.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
am: 1ec2b08e98
Change-Id: I95bc4efdf99940783d4ee768d98f3d30919ac685
|
|
This is basically the current state of the rest of the
FULL_TREBLE enablement bits for both hikey/hikey960
This patch also requires kernels that are rebuilt to include the
DTS fstab changes seen here:
https://git.linaro.org/people/john.stultz/android-dev.git/log/?h=dev/treble
Credit for this patch goes to Vishal Bhoj <vishal.bhoj@linaro.org>
who basically was the original author and magician
who got things working.
I've only refactored and split up his changes to help
with the submissions.
Change-Id: Iab0f5fc93bdfd1b86c98aa1d54974fde33514063
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
am: 6e5ccc6938
Change-Id: Ib29f7274ddfa9708cce0325fa2c1d7a516f4039e
|
|
Test: Manual
Change-Id: I6c1664c8068073ff490051e375204e18804e8b07
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
Framework will now add interface to supplicant (via HIDL) when it
needs to control an interface, so don't specify them in the startup
params.
Bug: 74084729
Test: Manual
Change-Id: I867877123a82fd3487dc631752621c07ed97a621
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
am: a614726b5f
Change-Id: Ifa50054399e6e0799ea62b0ad63dcc9c0e3410f9
|
|
Bug: 73171425
Test: Manual
Change-Id: I0a96d5e0e928f1de411e29e23f97c6a059ebda74
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
Bug: 72394251
Test: Compiles
Change-Id: Ifc60f2908ee51baaefa3aa046bd0be85c89b5d22
|
|
Treble compliance.
Bug: 70228425
Bug: 70393317
Test: Manual
Change-Id: Ia9c7a903307e7b7b86369199eb3195667d0a5da6
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
Wpa_supplicant's random pool is not necessary on Android. Randomness
is already provided by the entropymixer service which ensures
sufficient entropy is maintained across reboots. Commit b410eb1913
'Initialize /dev/urandom earlier in boot' seeds /dev/urandom with
that entropy before either wpa_supplicant or hostapd are run.
Bug: 34980020
Test: Use wifi and wifi tethering on Taimen.
Change-Id: Id07e6bd157baa4855fff6ddfbf248ad0bd512a40
|
|
remove the disabling of randomize_va_space which will cause
CtsAslrMallocTestCases test failed.
And this should not be a performance problem any more.
Test: CtsAslrMallocTestCases with hikey
Change-Id: I303b9b9379c30d3e38fab368d5d259e8c2963bb8
Signed-off-by: Yongqin Liu <yongqin.liu@linaro.org>
|
|
This functionality was removed at
https://android.googlesource.com/platform/frameworks/base/+/a712d4058f6f85268838
|
|
Since the HiKey are mostly used with HDMI displays, its annoying to get
the rotation back to default if an app decides to force change it.
This patch allows the rotation to reset once the app has
exited/minimised
Test: Manual, with apps like Androbench that force rotation to portrait
Change-Id: I5d90aed2a9ef9a150151bfc6a54bc99e4ce60bce
Signed-off-by: Sahaj Sarup <sahajsarup@gmail.com>
|
|
Bug: 65159511
Test: Manual
Change-Id: Ib1b9aeb0afd13ad7c5479a2a84e39efa65c563e7
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
Bug: 65046852
Test: Manual
Change-Id: Ic440d132342bcf1037902dd271a3c37ca7aae05e
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
Kernel 3.18 doesn't have default settings for these
CGROUPS causing system crash before setting sys.boot_completed
Bug: 64023829
Test: Manual
Change-Id: I4d0200b1bfbf5a3c58a90d4fb0d48d8674360b78
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
Hikey960 has different CPU architecture with Hikey, these two platforms
should use their own dedicate configurations for power, especially for
EAS related settings.
This patch is to split the power related settings into two files, one
is init.hikey.power.rc and another is init.hikey960.power.rc. The main
different setting for power setting is related with EAS parameters in
proc nodes.
For Hikey we set the parameters as below:
write /proc/sys/kernel/sched_is_big_little 0
write /proc/sys/kernel/sched_cstate_aware 1
write /proc/sys/kernel/sched_sync_hint_enable 1
write /proc/sys/kernel/sched_initial_task_util 0
For Hikey960 we set the parameters as below:
write /sys/kernel/debug/sched_features "ENERGY_AWARE"
write /proc/sys/kernel/sched_is_big_little 1
write /proc/sys/kernel/sched_cstate_aware 1
write /proc/sys/kernel/sched_sync_hint_enable 0
write /proc/sys/kernel/sched_initial_task_util 0
On Hikey960 we also set default boost margin to 50%, and
touch-boost to 100%. This will let the CPU frequency to reach
highest OPP so can reduce scheduling latency; this is used to
improve the GPU rendering performance.
write /dev/stune/top-app/schedtune.boost 50
write /dev/stune/foreground/schedtune.boost 50
Change-Id: I641f5c78075012153fb73e830cb31dfc8dfd6e87
Signed-off-by: Leo Yan <leo.yan@linaro.org>
[jstultz: Added and tweaked some of the parameters to work with
the parameterized powerHAL]
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
In the aosp common init.rc file, all cpusets are initialized to
use all cpu cores here:
https://android-review.googlesource.com/#/c/373574/
And to help to make boot much faster, need to keep to use all cpu cores
till the boot completed.
btw, put the "on post-fs-data" after "on post-fs" as well
Test: manual with hikey, the average(from 10 times) android boot time is about
0.8s faster. The measurement is taken from lines like "Boot is finished (17288 ms)" from logcat
Change-Id: I42b42c1b8af717ab305fcbdb939404725f6bd88a
Signed-off-by: Yongqin Liu <yongqin.liu@linaro.org>
|
|
The initial EAS hikey powerhal was added before N was released, which
introduced the top-app category. So refactor the code to use top-app.
This also tweaks the build so that the module can be more easily
reused on other hardware.
Change-Id: I2847cbf62ea45b15fa2b8d3ee249c153cea351b0
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
Bug: 35684372
Test: Compiles
Change-Id: Id49e340f63c24340d3ad53596d7a9eddd0888298
(cherry-picked from 71745bd31fddc7e01cbe4c60192a7f17104177b9)
|
|
Test: VtsHalBluetoothV1_0TargetTest passes
Change-Id: I31612e9511d3e80e02fd19e2a258fe187d90337c
|
|
No functional changes. Just moved around the configuration files and
restructured them to support future hikey family devices. Similar to
how Marlin and Sailfish devices are configured.
Split the board configuration into BoardConfigCommon.mk (for common
configuration) and hikey/BoardConfig.mk (for hikey specific
configuration e.g. Image sizes and kernel commandline).
Similarly split device.mk into device-common.mk and hikey/device-hikey.mk.
Updated hikey.mk to include both device-common.mk and hikey/device-hikey.mk.
Renamed init.hikey.rc to init.common.rc and modified it to import
init.${ro.hardware}.usb.rc and mount fstab.${ro.hardware} instead.
Changes to be committed:
renamed: BoardConfig.mk => BoardConfigCommon.mk (68%)
renamed: hikey.kl => common.kl (100%)
renamed: device.mk => device-common.mk (74%)
modified: hikey.mk
new file: hikey/BoardConfig.mk
renamed: board-info.txt => hikey/board-info.txt (100%)
new file: hikey/device-hikey.mk
renamed: fstab.hikey => hikey/fstab.hikey (100%)
renamed: fstab.hikey-4.1 => hikey/fstab.hikey-4.1 (100%)
renamed: init.hikey.rc => init.common.rc (97%)
renamed: init.hikey.usb.rc => init.common.usb.rc (100%)
renamed: ueventd.hikey.rc => ueventd.common.rc (100%)
Test: Manual
Change-Id: I032323aa8846a3bc144e40b4b5e5348c8f8d11c5
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|