-
Notifications
You must be signed in to change notification settings - Fork 42
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
vanirAOSP #7
Open
28vicky
wants to merge
259
commits into
diego-ch:cm-10.1
Choose a base branch
from
TeamCanjica:cm-11.0
base: cm-10.1
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
vanirAOSP #7
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
the fix is being done directly on libhardware_legacy
We want to use these in devices, not just include them by a if equal (ifeq) in common
Otherwise the vendor_cm cannot found it's bootanimation :)
This is needed by the vendor_cm repo, it will not resolve the bootanimation required otherwise
Already defined in cm.mk
Include RIL on BoardConfig Move NFC packages to be build on janicep, not to be overriden :) NFC access files to janicep Move the RIL to device Build.prop overrides to device
We have everything defined in the .c file, we don't want to include vibrator from legacy because it will complain about the function being defined in other way
Just as we did with janicep, we update the delay slightly TeamCanjica/android_device_samsung_janicep@f134020
For some reason, the build just doesn't come out with the RIL class, just add it to system.prop since it's common
following ImVic advices, we change the directory of the copy files (was trying to get them copied to rootdir/system?) to the correct one as every other product copy file. We add the missing separator which made our RIL class not being added at build.prop :)
We make Tee blobs to be specific to avoid the annoying bug of janice blobs that are being copied to janicep We also modify the system.prop so it doesn't include the RIL strings anymore, they are now properly overriden
Suggestion(s) from OliverG96
WE NEED TO SOLVE DAT PROBLEM DisplayDevice: Backwards compatibility with old EGL From 4.1 to 4.2, the display subsystem was reworked to use SurfaceTextureClient/BufferQueue instead of FramebufferNativeWindow for the framebuffer itself. Unfortunately, some legacy EGL libraries make assumptions that any framebuffer device will be FramebufferNativeWindow. These EGL libraries will fail when used in 4.2 as if the framebuffer is not FramebufferNativeWindow, they will try to dequeue more than one buffer at a time, which will cause a hang of the graphics subsystem http://review.cyanogenmod.org/#/c/28005/ Also, we disable triple buffering for now, since it's the handler of the bad-done VSYNC, so, we cap the FPS rate by refresh_rate cflag to 60, and let the screen do the actual capping of Hertz screen refresh rate. As explained here, the triple framebuffering is NOT checking the actual refresh rate of the screen, so it's running as fast as it can :) Due to the software algorithm not having to poll the graphics hardware for monitor refresh events, the algorithm is free to run as fast as possible.
we still need the legacy_fb cflag
Update permissions for NovaThor Settings
Change-Id: I5930c38476e30483beb5828e057e3ceccdc8fad6
janices needs to fix this commit: http://review.cyanogenmod.org/#/c/59752/ in Settings package too Change-Id: I498767fb63bfce9bb5c6be8b0e48cf9a041d8336
export Novathor Settings permissions to device_tunnables.rc for better compatibility and reduce init.<device>.rc size
and fix typo on torch permission...
copy paste typo
- rename device_tunnables.rc > device_tunables.rc - wait "on property:sys.boot_completed=1" before setting permissions
+Move audio_policy.conf to common +Remove useless file
+Make common usb init
update README.md to current version
thanks Davide Pianca (KINGBabasula) for the new pwm sysfs, (original idea from codeworkx)
chown /sys/vibrator/pwm_value to system:system
Very basic. TODO: fix SELinux policies and change to Enforcing mode Change-Id: Ibc61752d359c7564ed487a0f6b9a238aa90ca43d Reminder: Kill Rox.
SELinux is moved to common This reverts commit addcb2e.
+Move storage_list.xml to common
there's a permission error when stericsson blobs try to access those files ie. playing media results on this error: V/OmxILOsalPrm( 1833): ChangeResourceState(0, 50, 0x447e79f4) E/OmxILOsalPrm( 1833): updateSocDvfsOpp - failed to open /dev/ape_opp V/OmxILOsalPrm( 1833): ChangeResourceState(1, 50, 0x447e79f4) E/OmxILOsalPrm( 1833): updateDDROpp - failed to open /dev/ddr_opp V/OmxILOsalPrm( 1833): ChangeResourceState(2, 600, 0x447e79f4) changing user to media and group to system fixes the error
Change-Id: Id65d3c1b6c1914ae9af365a5a8a5af9a626969e6
Change-Id: I3c71e4339a21514abacadf0e084aaffba8569aa7
fix broken linking due to not exported sendit()
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.
No description provided.