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
For Remove Hardware features check following files in android source : | |
1. Check the device.mk file for your device(Like : device/<vendor>/<device>.mk) | |
2. Check the common.mk file for your device(Like : device/<vendor>/common/common.mk) | |
There both files is probably a line like the following: | |
PRODUCT_COPY_FILES += \ | |
frameworks/native/data/etc/android.hardware.location.gps.xml:system/etc/permissions/android.hardware.location.gps.xml \ |
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
make cts -j8 TARGET_PRODUCT=msm8960 |
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
==> ffmpeg decode video | |
ffmpeg -i Untitled_Project-Apple_ProRes_422.mov -f rawvideo -pix_fmt yuv420p Untitled_Project-Apple_ProRes_422.yuv | |
==> ffmpeg slicing video | |
ffmpeg -i Untitled_Project-Apple_ProRes_422.mov -pix_fmt yuv420p -ss 00:00:00 -t 00:00:15 part1_420p.mov | |
==> adding into container format |
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
Create a scroll bar in drawable(scrollbar.xml) using this | |
<?xml version="1.0" encoding="utf-8"?> | |
<shape xmlns:android="http://schemas.android.com/apk/res/android" | |
android:shape="rectangle"> | |
<gradient | |
android:angle="45" | |
android:centerColor="#669C79E7" | |
android:endColor="#66C0C0C0" | |
android:startColor="#669C70E2" /> |
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
# Built application files | |
/*/build/ | |
# Crashlytics configuations | |
com_crashlytics_export_strings.xml | |
# Local configuration file (sdk path, etc) | |
local.properties | |
# Gradle generated files |
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
<supports-screens | |
android:resizeable="true" | |
android:smallScreens="true" | |
android:normalScreens="true" | |
android:largeScreens="true" | |
android:anyDensity="true" | |
/> |
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
Well you can have a BroadcastReceiver declared in your manifest to receive the BOOT_COMPLETED broadcast and then respond to that in your BroadcastReceiver and do what you like. | |
<receiver android:name="MyBootReceiver" | |
android:enabled="true" | |
android:exported="true" | |
android:label="BootReceiver"> | |
<intent-filter> | |
<action android:name="android.intent.action.BOOT_COMPLETED"></action> | |
</intent-filter> |