forked from aosp-mirror/platform_system_core
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Camera: Add feature extensions #1
Open
adrian1234a
wants to merge
13
commits into
Havoc-OS:thirteen
Choose a base branch
from
adrian1234a:patch-1
base: thirteen
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
Signed-off-by: Anushek Prasal <[email protected]>
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: I6095bbf92267fcb78ab53f37b5d7b443239ce80b Signed-off-by: Anushek Prasal <[email protected]>
Doing this in the userspace allows more properties to be spoofed and eliminate the needs for a hack in the kernel. Change-Id: I6ad755c085491c958c8a7d75db7df2c8e5481a55 Signed-off-by: Anushek Prasal <[email protected]>
aswinas@pixysos: add some more props from magisk hide to userspace hack by arter97 Change-Id: Ib6ad1df4582a2f8333b0cbf650e79e947f6576d0 Signed-off-by: Anushek Prasal <[email protected]>
Change-Id: I1664b3b3fa0fc87bda683d53a56645f6d974ce01 Signed-off-by: Anushek Prasal <[email protected]>
Change-Id: I5c675e3391cc48a95ab9186047e9e9effca95406 Signed-off-by: Anushek Prasal <[email protected]>
Also reformat code Change-Id: I4c0bcb61fea5a7b051c3a770d34a3a09f17db1c4 Signed-off-by: Anushek Prasal <[email protected]>
The real prop values must be retained in recovery/fastbootd in order for fastbootd to allow/deny flashing correctly based on the bootloader lock state. This is accomplished by checking androidboot keys in the kernel cmdline and bootconfig (necessary on Pixel 6), and not spoofing anything if the boot isn't a normal full-blown Android boot. @jhenrique09 - Adapt to PE Change-Id: I8795b16a90eea4e5a03f64a7a56478f01144256b Signed-off-by: Anushek Prasal <[email protected]>
Change-Id: Ic0ddbd6a0dd40c877248f7864082eddab2b32366 Signed-off-by: Anushek Prasal <[email protected]>
Checking androidboot.mode properties will never work on devices where this property is always absent, primarily non-Pixel devices. Use existing IsRecoveryMode() check instead which is ugly, but works for this very purpose. Change-Id: Idc79fb2bf45f0416b242a1e1aa12bdb07bcf56b9 Signed-off-by: Albert I <[email protected]> Signed-off-by: Alexander Winkowski <[email protected]> Signed-off-by: Anushek Prasal <[email protected]>
PixelExperience/android-issues#1008 Change-Id: I4d611ee8b8490832b310fca48f2576fc9790d483 Signed-off-by: Anushek Prasal <[email protected]>
Change-Id: Icef14fa8b2ea353e3ba7cd2c6d1573dbc82474a1 Signed-off-by: xyyx <[email protected]> Signed-off-by: Pranav Vashi <[email protected]> Signed-off-by: Anushek Prasal <[email protected]>
This change includes below commits: Camera bringup changes system-core Change-Id: I1cf98641eca9096bd27645e07ea802646ea1fb96 system/core: Fix for HAL compilation issues while integrating HAL 1.0 Change-Id: Iead9c1ade279b64c5cbdf4d2de1a8b695939c52a Camera: Add enum to specify the frame type Added enum to specify the frame type of either fd/data buffer CRs-fixed: 654901 Change-Id: I1c0b1a2c6a1425cdb6650cdfc20ca65835a1b81f
Amit152505
approved these changes
Aug 4, 2023
SKULSHADY
force-pushed
the
thirteen
branch
3 times, most recently
from
August 23, 2023 23:14
06c0506
to
5dbb512
Compare
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.
This change includes below commits: