Dualshock 4 is not working on lineage 18.1 #4
Conversation
This file contains 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
This option never had any effect for some reason as max_comp_streams was set to 1 even with this option and it had to be manually changed, and since commit "zram: remove max_comp_streams internals" with hash a2747b492c53ecdd239556abfe7c0d7992bc43a6 in the kernel, changes to max_comp_streams don't take any effect. Change-Id: I597e63ec07e02966ab4921375f1df0c37cc4ab3a
Change-Id: I63f16b2c62aaff7034d0125eb5f2c0a07e2b772d
…rom source again. It doesn't appear to be necessary to use the prebuilt version of this library. This change depends on the removal of the prebuilt version of this library in vendor. This mostly reverts commit e1fcf31. Change-Id: Id780d9a272c9f16acb92d3e337f8950bda033f22
Since commit "sm5703_fled: use more appropriate permissions
for device attributes rear_flash and rear_torch_flash."
("9ecacaa5e2c7e63cc06befa7e6d98bede7d6fb7d") in the kernel,
the permissions for /sys/class/camera/flash/rear_torch_flash
are already 0660 by default.
Change-Id: Ie515d7284bb5b0f6126d246417fd3a5c3ce31962
Change-Id: I32da44ee64a78d69584394512dffc886dd52e190
That change doesn't cause any issues. This reverts commit 89f0f16. Change-Id: I35352e071702ab12a04dc857731960d030c04432
Change-Id: If3b993fffd0f8f1d7537577d7a7984eb9e31c8d7
…/dev/network_throughput. Change-Id: I8352b60b1045b618c185b4cc920b4cd2f970104d
Change-Id: If01f485ac6f885a926a7cb0a26d26b20aa017944
Change-Id: I8d0192f7a61e6230f20d0425c1b2be36b4021959
Change-Id: I81b8009e67707821a755dc3bf587eb0d38ebe66c
Change-Id: Ia43179b5e930488b8dd2ae86b0faa6b22593bac4
Change-Id: Ieb244c6c1abcf240e1ae0a26e7b7376c6746a4f3
…ugin. Change-Id: I1ea100fd837933b4f399c6b7d301a374cd9131a3
This reverts commit e4c72de.
Labeled as only for gtaxlwifi as this removes rules that are irrelevant to gtaxlwifi, but are relevant for gtaxllte. Not that this sepolicy was likely ever complete for gtaxllte, anyway.
* We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. * 128MB ought to be enough for anybody. Test: builds, boots Bug: 62024591 Change-Id: I412ed9b0a885668ebe4c6c677a3bd0cd7f44080b
…dio.effect@2.0-impl.
Bug: 142286265 Test: charger mode Change-Id: I677335873cd1efac0a3d2bce6d59b23edf70545c
Add CAP_SYS_BOOT capability for charger service so that it can shutdown/reboot the system. Change-Id: I17ccba74d5a3c38bd751c55bcf42fb3689d730a7
Make charger binary run as system instead of root. Since it needs to handle input key events, add input as a supplemental group in addition to system and graphics. Change-Id: Id1dc46f335087147b7d8cf674664c26f0b511de1
2.2 isn't of any use as there's no support for HWC2. Change-Id: I18364ac99859fb71516ccd47f223b3bd329d5130
…bling touchkey input Fixes an issue where enabling the "Enable on-screen nav bar" setting at Settings -> System -> Buttons (at least) would cause touchscreen input to also not work as it was disabled along with the touchkeys through the default node, since input from them is provided by the same driver and touchscreen controller, through only one unified input. Something of note is that through the new sysfs node, touchkey input is technically accepted or ignored, rather than enabled or disabled, since it can't be disabled properly separately from touchscreen input in hardware. Change-Id: I1734c69e690155e35803efeec58aea1d4e2fe342
- stops the unnecessary logspam of camera parameters during boot - we are in production state, so its kind of meaningless now [ TALU - Technically, we're not totally in a production state since we still have the problem with camera preview squashing and video squashing with the rear-facing camera at some resolutions, but it's certainly not fixable given proprietary blobs, anyway. ] Change-Id: Id16020e604d3f9eb8d1dafb65517bc36149e957e
Bug: 38396207 (VK_KHR_variable_pointers) Bug: 64982680 (maxPerStageDescriptorStorageBuffers >= 16) Test: CtsGraphicsTestCases:.VulkanFeaturesTest (ag/2810565) Change-Id: I61cde61f53f0e9a1c657e6bd6658a4393360b0a6
This commit adds the IPSEC_TUNNELS feature flag, with XFRM Interfaces used as the implementation of choice. Bug: 117183273 Bug: 137629222 Test: Compiles, passes tunnel-mode CTS tests Test: adb shell pm list features Change-Id: I19c598947525783850b29d149db85db89f8b347e
With the OSS audio HAL, and with reduced playback and low-latency capture period sizes, audio latency is now much lower. According to tests with the Superpowered audio latency test app [1], with very rough tests with the Dr. Rick O'Rang loopback app [2][3] with just my wired headphones and the built-in microphone confirming, on my tablet, round-trip audio latency is now around 14-16 ms. Therefore, seeing as all of the other requirements for pro audio support to be reported seem to be satisfied as well, it's now doable. [1] https://superpowered.com/latency [2] https://source.android.com/devices/audio/latency/measure#measuringRoundTrip [3] https://github.com/gkasten/drrickorang/tree/master/LoopbackApp Change-Id: I8ba63da90e7309afb3c06cb3ce80c1848c6f4f91
…ing/disabling touchkey input" This reverts commit eca1b1a.
d88d29a4384a27366fe47e40c977a65e43566159 moved audio hal to vendor but props audio hal is reading can't be used as vendor props so turn them into vendor props in case some treble compatible device ends up using this hal and can't cross read props Change-Id: I439b07011b681af05cbfaa4b7d88ae337751a6ff
…ro.vendor.' as per the latest change to the audio HAL. Change-Id: Ibe2f1a11a559a6e030639d4f4ce8e66603609535
This reverts commit 7ec86b2. The conversion to Android.bp causes this error with the build system when trying to build for certain other devices, in this case, gta4xlwifi: [100% 1013/1013] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja FAILED: out/soong/build.ninja cd "$(dirname "out/soong/.bootstrap/bin/soong_build")" && BUILDER="$PWD/$(basename "out/soong/.bootstrap/bin/soong_build")" && cd / && env -i "$BUILDER" --top "$TOP" --out "out/soong" -n "out" -d "out/soong/build.ninja.d" -t -l out/.module_paths/Android.bp.list -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used Android.bp error: device/samsung/gtaxl-common/shims/libshim_camera/Android.bp:16:1: module "libexynoscamera_shim" variant "android_vendor.32_arm_armv8-a_cortex-a53_shared": non-VNDK module should not link to "libgui" which has `private: true` 18:05:24 soong bootstrap failed with: exit status 1 No idea for a more proper fix (if there's any), so just revert it. Change-Id: I93426d2f64811483600134591e37e319b290d4fe
Change-Id: Ib429a7091e9bdabd7df95bf44959a4d38746aaa6
Change-Id: Idaf469ed3ab6ea8499d4d97572cbb6bcab13fab6
[ TALU - and get rid of the old method of doing so ] Change-Id: I25501e0ffcb86b8e21ee44c648b9f14bbb931b8b
Gets OMX libs from sources working properly, except for HEVC decoding and encoding. Change-Id: I8e1189340625c11baad957b13dc109af01a4a1b4
Change-Id: I936731fae679ff66c0f97512f6aed74c2ad3db09
Change-Id: I3de874cc38489e297476f37868a449a3f863c50d
Change-Id: I1c3a30f8f107e4947464ce31082e8a9b2858c44c
Change-Id: I8dd487f7832c290587694bb5daa9c26a1551c763
* Just bind mount gps.conf to gps_debug.conf We can't directly build gps_debug.conf because it's a common target and we're not allowed to override targets anymore. * Allow the bind mount in SEPolicy Change-Id: Ia3c96665b50b0fe478e44186d1c65be723acbf5a
gps.conf is now bind mounted to gps_debug.conf instead. Change-Id: Ie4fb1190a629d41bd5c841ef2a7e8fe462d4f7e1
No longer necessary. Change-Id: I6a16c0f0425d3d294eaf2645403edf17cb89b4f4
Does seem to improve the performance of animations somewhat. Change-Id: Ibf3a680aa83215dc83cd0b6d25f501e5759f0027
…able Gets the torch working again. Change-Id: Ic34bd4feb56d3105b4c350e99303cebd16a2f6ae
The only use it had was to define some custom gralloc usages used in the BSP sources. However, those are now defined within them, so it's no longer necessary. Having the gralloc header overridden somehow caused some issue somewhere that causes Codec2 to not work, so with this, Codec2 is now fixed and usable. Change-Id: I2a41f2812db7874417857de6a212f87e3d7fe782
…nges) Change-Id: I3153a80b807e87ee736aea4d5e5750087651c7f6
Change-Id: Ieb1e849706fce8a51509c0f2aca3160bc24dd3b5
…ndroid.bp"" This reverts commit 6c1ffa0. Change-Id: Ie496dd24bac73e29ef9ec3d4b0b7e3980e4f2e23
…braries Change-Id: I1f7beb24a7f9f958b9be8276815b04825399ad45
…b.config Change-Id: I33dbe82d47c7090e8c222fd4ef97fb425d250558
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The dualshock 4 can connect to bluetooth but it doesnt work at all