i was trying to build framework-res.apk
i went into android_frameworks_base/core/res from terminal
theres an Android.mk file there:
Code:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
LOCAL_NO_STANDARD_LIBRARIES := true
LOCAL_PACKAGE_NAME := framework-res
LOCAL_CERTIFICATE := platform
# Tell aapt to create "extending (non-application)" resource IDs,
# since these resources will be used by many apps.
LOCAL_AAPT_FLAGS := -x
LOCAL_MODULE_TAGS := optional
# Install this alongside the libraries.
LOCAL_MODULE_PATH := $(TARGET_OUT_JAVA_LIBRARIES)
# Create package-export.apk, which other packages can use to get
# PRODUCT-agnostic resource data like IDs and type definitions.
LOCAL_EXPORT_PACKAGE_RESOURCES := true
include $(BUILD_PACKAGE)
# define a global intermediate target that other module may depend on.
.PHONY: framework-res-package-target
framework-res-package-target: $(LOCAL_BUILT_MODULE)
and then i did
make framework-res
make: *** No rule to make target `framework-res'. Stop.
can u help me with the process? im just a beginner.
This ROM 4.0 for Dell Venue is NOT stabilized yet with non working camera. I wish to open New Thread to ask Help from member here in building Jelly Bean 4.2.2 for Dell Venue on AOKP Source Tree.
I hav succesfully built the ROM but can not BOOT to dell venue and I can Not do adb logcating since the file /system/bin/sh is symlinks from /system/bin/mksh .... SEE ATTACHED SCREENSHOT.
[q] Is it Normal in 4.2.2 ? so How to do logcating at 4.2.2 ROM or should I used latest adbd .. I have built system.img and boot.img from command make systemimage thus I don't have CWR Flashable zip file .. but I can rebuild if it will help to evaluate.
Config :
/device/dell/venue/BoardConfik.mk
# inherit from the proprietary version
-include vendor/dell/venue/BoardConfigVendor.mk
#--
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := qsd8k
TARGET_BOARD_PLATFORM_GPU := qcom-adreno200
# CPU Stuff
TARGET_ARCH := arm
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_CPU_SMP := true
TARGET_BOOTLOADER_BOARD_NAME := venue
TARGET_CORTEX_CACHE_LINE_32 := true
# Boot stuff
BOARD_KERNEL_CMDLINE := androidboot.hardware=venue
BOARD_KERNEL_BASE := 0x20000000
BOARD_PAGE_SIZE := 2048
#- depending on your taste to put kernel sources
TARGET_KERNEL_SOURCE := device/dell/venue/vn2634
TARGET_KERNEL_CONFIG := venue_defconfig
#---
TARGET_GLOBAL_CFLAGS +=-mfpu=neon -mfloat-abi=softfp
TARGET_GLOBAL_CPPFLAGS +=-mfpu=neon -mfloat-abi=softfp
#--
### cat /proc/mtd
# dev: size erasesize name
# mtd0: 00500000 00020000 "boot"
# mtd1: 00600000 00020000 "recovery"
# mtd2: 00600000 00020000 "recovery_bak"
# mtd3: 00040000 00020000 "LogFilter"
# mtd4: 00300000 00020000 "oem_log"
# mtd5: 10400000 00020000 "system"
# mtd6: 22600000 00020000 "userdata"
# mtd7: 06600000 00020000 "cache"
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00500000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00600000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x10400000
BOARD_FLASH_BLOCK_SIZE := 131072
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0X22600000
TARGET_USERIMAGES_USE_EXT4 := false
BOARD_HAS_NO_SELECT_BUTTON := true
BOARD_USE_CUSTOM_RECOVERY_FONT := '"font_7x16.h"'
COMMON_GLOBAL_CFLAGS += -DREFRESH_RATE=60 -DQCOM_HARDWARE
TARGET_SPECIFIC_HEADER_PATH := device/dell/venue/include
USE_OPENGL_RENDERER := true
BOARD_VENDOR_USE_AKMD := true
# QCOM stuffs
BOARD_USES_QCOM_HARDWARE := true
TARGET_USES_OVERLAY := true
TARGET_HAVE_BYPASS := false
TARGET_USES_C2D_COMPOSITION := true
TARGET_USES_GENLOCK := true
TARGET_QCOM_HDMI_OUT := false
TARGET_FORCE_CPU_UPLOAD := true
BOARD_USES_QCOM_LIBS := true
BOARD_USES_QCOM_PMEM := true
BOARD_EGL_CFG := device/dell/venue/configs/egl.cfg
TARGET_PROVIDE_LIBRIL := true
# RIL
BOARD_USES_LEGACY_RIL := true
#-- TO DO and Check
TARGET_GRALLOC_USES_ASHMEM := false
#-- End of TO DO and Check
BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true
# to enable the GPS HAL
BOARD_USES_QCOM_LIBRPC := true
BOARD_USES_QCOM_GPS := true
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := venue
# AMSS version to use for GPS
BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION := 50000
# --builable for ics wpa_0_8_x
BOARD_WLAN_DEVICE := bcm4329
WIFI_EXT_MODULE_MODULE_PATH := /system/lib/modules/librasdioif.ko
WIFI_DRIVER_MODULE_PATH := /system/lib/modules/dhd.ko
WIFI_EXT_MODULE_NAME := librasdioif
WIFI_DRIVER_MODULE_NAME := dhd
WIFI_DRIVER_FW_PATH_STA := /system/vendor/firmware/fw_bcm4329.bin
WIFI_DRIVER_FW_PATH_AP := /system/vendor/firmware/fw_bcm4329_apsta.bin
WIFI_DRIVER_MODULE_ARG := "firmware_path=/system/etc/wlan/sdio-g-cdc-full11n-reclaim-roml-wme-aoe-pktfilter-keepalive-wapi.bin nvram_path=/etc/wlan/nvram.txt"
WIFI_AP_DRIVER_MODULE_ARG := /system/etc/wlan/sdio-g-cdc-roml-reclaim-wme-apsta-idsup-idauth.bin
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_wext
BOARD_WPA_SUPPLICANT_DRIVER := WEXT
WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WEXT_NO_COMBO_SCAN := true
#--- Vold stuffs
#BOARD_VOLD_MAX_PARTITIONS := 16
# Camera
CAMERA_USES_SURFACEFLINGER_CLIENT_STUB := true
COMMON_GLOBAL_CFLAGS += -DICS_CAMERA_BLOB -DNO_UPDATE_PREVIEW
BOARD_NEEDS_MEMORYHEAPPMEM := true
TARGET_DISABLE_ARM_PIE := true
#
#
Click to expand...
Click to collapse
device/dell/venue/full_venue.mk just to follow common naming policy of aokp
LOCAL_PATH := device/dell/venue
# The gps config appropriate for this device
$(call inherit-product, device/common/gps/gps_us_supl.mk)
# Inherit non-open-source blobs.
$(call inherit-product-if-exists, vendor/dell/venue/venue-vendor.mk)
# Inherit Device build
$(call inherit-product, build/target/product/full_base_telephony.mk)
PRODUCT_TAGS := dalvik.gc.type-precise
PRODUCT_PROPERTY_OVERRIDES := \
dalvik.vm.heapstartsize=5m \
dalvik.vm.heapgrowthlimit=32m \
dalvik.vm.heapsize=76m
PRODUCT_AAPT_CONFIG := normal mdpi ldpi
PRODUCT_AAPT_PREF_CONFIG := mdpi
# Init file boot ramdisk set-up
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/init/init.rc:root/init.rc \
$(LOCAL_PATH)/init/ueventd.rc:root/ueventd.rc \
$(LOCAL_PATH)/init/init.venue.rc:root/init.venue.rc \
$(LOCAL_PATH)/init/init.venue.usb.rc:root/init.venue.usb.rc \
$(LOCAL_PATH)/init/initlogo.rle:root/initlogo.rle
# Configuration
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/configs/8k_handset.kl:system/usr/keylayout/8k_handset.kl \
$(LOCAL_PATH)/configs/surf_keypad.kl:system/usr/keylayout/surf_keypad.kl \
$(LOCAL_PATH)/configs/qwerty.kl:system/usr/keylayout/qwerty.kl \
$(LOCAL_PATH)/configs/surf_keypad.kcm.bin:system/usr/keychars/surf_keypad.kcm.bin \
$(LOCAL_PATH)/configs/mXT224_touchscreen.idc:system/usr/idc/mXT224_touchscreen.idc \
$(LOCAL_PATH)/configs/audio_effects.conf:system/etc/audio_effects.conf \
$(LOCAL_PATH)/configs/vold.fstab:system/etc/vold.fstab
# Media Profile
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/configs/media_profiles.xml:system/etc/media_profiles.xml
Click to expand...
Click to collapse
vendor/aokp/product/venue.mk
# Inherit AOSP device configuration for venue.
$(call inherit-product, device/dell/venue/full_venue.mk)
# Inherit AOKP common bits
$(call inherit-product, vendor/aokp/configs/common.mk)
# Inherit GSM common stuff
$(call inherit-product, vendor/aokp/configs/gsm.mk)
# venue Overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/aokp/overlay/venue
# Setup device specific product configuration.
PRODUCT_NAME := aokp_venue
PRODUCT_BRAND := dell
PRODUCT_DEVICE := venue
PRODUCT_MODEL := Dell Venue
PRODUCT_MANUFACTURER := dell
UTC_DATE := $(shell date +%s)
DATE := $(shell date +%Y%m%d)
PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=${PRODUCT_DEVICE}_${PRODUCT_SFX} \
BUILD_NUMBER=${DATE} \
TARGET_DEVICE=${PRODUCT_DEVICE_PREFIX}_${PRODUCT_DEVICE} \
BUILD_FINGERPRINT=${PRODUCT_BRAND}/${PRODUCT_DEVICE}_${PRODUCT_SFX}/${PRODUCT_DEVICE_PREFIX}_${PRODUCT_DEVICE}:${PLATFORM_VERSION}/${BUILD_ID}/${DATE}:user/release-keys \
PRIVATE_BUILD_DESC="${PRODUCT_DEVICE_PREFIX}_${PRODUCT_DEVICE}-user ${PLATFORM_VERSION} ${BUILD_ID} ${DATE} release-keys" \
PRODUCT_BRAND=${PRODUCT_BRAND} \
BUILD_UTC_DATE= \
PRODUCT_DEFAULT_LANGUAGE=en \
PRODUCT_DEFAULT_REGION=ID \
# Venue specific packages
PRODUCT_PACKAGES += \
Thinkfree \
libstagefrighthw \
audio.a2dp.default \
audio.primary.qsd8k \
audio_policy.qsd8k \
libgenlock \
liboverlay \
gralloc.qsd8k \
hwcomposer.qsd8k \
copybit.qsd8k \
gps.venue \
camera.qsd8k \
libOmxCore \
libOmxVidEnc
PRODUCT_COPY_FILES += \
vendor/aokp/prebuilt/bootanimation/bootanimation_400_800.zip:system/media/bootanimation.zip
Click to expand...
Click to collapse
vendor/dell/venue/venue-vendor.mk
$(call inherit-product, vendor/dell/venue/venue-vendor-blobs.mk)
# Live wallpaper packages
PRODUCT_PACKAGES := \
LiveWallpapers \
LiveWallpapersPicker \
MagicSmokeWallpapers \
librs_jni
# Publish that we support the live wallpaper feature.
PRODUCT_COPY_FILES := \
packages/wallpapers/LivePicker/android.software.live_wallpaper.xml:/system/etc/permissions/android.software.live_wallpaper.xml
Click to expand...
Click to collapse
vendor/dell/venue/venue-vendor-blobs.mk
LOCAL_PATH := vendor/dell/venue
# CAMERA STUFF
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/proprietary/lib/libcamera.sobj/lib/libcamera.so \
$(LOCAL_PATH)/proprietary/lib/liboemcamera.so:system/lib/liboemcamera.so \
$(LOCAL_PATH)/proprietary/lib/libcamera_client.so:system/lib/libcamera_client.so \
$(LOCAL_PATH)/proprietary/lib/libcameraservice.so:system/lib/libcameraservice.so
# WIFI
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/proprietary/etc/firmware/yamato_pfp.fw:system/etc/firmware/yamato_pfp.fw \
$(LOCAL_PATH)/proprietary/etc/firmware/yamato_pm4.fw:system/etc/firmware/yamato_pm4.fw \
$(LOCAL_PATH)/proprietary/etc/wlan/sdio-g-cdc-full11n-reclaim-roml-wme-aoe-pktfilter-keepalive-wapi.bin:system/etc/wlan/sdio-g-cdc-full11n-reclaim-roml-wme-aoe-pktfilter-keepalive-wapi.bin \
$(LOCAL_PATH)/proprietary/etc/wlan/sdio-g-cdc-roml-reclaim-wme-apsta-idsup-idauth.bin:system/etc/wlan/sdio-g-cdc-roml-reclaim-wme-apsta-idsup-idauth.bin
# $(LOCAL_PATH)/proprietary/etc/wlan/nvram.txt:system/etc/wlan/nvram.txt
# AUDIO
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/proprietary/etc/01_qcomm_omx.cfg:system/etc/01_qcomm_omx.cfg \
$(LOCAL_PATH)/proprietary/lib/libsc-a2xx.so:system/lib/libsc-a2xx.so \
$(LOCAL_PATH)/proprietary/lib/libOmxCore.so:system/lib/libOmxCore.so \
$(LOCAL_PATH)/proprietary/lib/libOmxVidEnc.so:system/lib/libOmxVidEnc.so
# TOUCHSCREEN DISPLAY
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/proprietary/usr/idc/qwerty.idc:system/usr/idc/qwerty.idc \
$(LOCAL_PATH)/proprietary/usr/keychars/surf_keypad.kcm.bin:system/usr/keychars/surf_keypad.kcm.bin \
$(LOCAL_PATH)/proprietary/usr/keychars/qwerty.kcm:system/usr/keychars/qwerty.kcm \
$(LOCAL_PATH)/proprietary/usr/keychars/Virtual.kcm:system/usr/keychars/Virtual.kcm
# RIL
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/proprietary/lib/libreference-ril.so:system/lib/libreference-ril.so \
$(LOCAL_PATH)/proprietary/bin/rild:system/bin/rild \
$(LOCAL_PATH)/proprietary/lib/libril.so:system/lib/libril.so \
$(LOCAL_PATH)/proprietary/lib/libril-qcril-hook-oem.so:system/lib/libril-qcril-hook-oem.so \
$(LOCAL_PATH)/proprietary/lib/libril-qc-1.so:system/lib/libril-qc-1.so
# EGL
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/proprietary/lib/egl/libGLESv2_adreno200.so:system/lib/egl/libGLESv2_adreno200.so \
$(LOCAL_PATH)/proprietary/lib/egl/libGLESv1_CM_adreno200.so:system/lib/egl/libGLESv1_CM_adreno200.so \
$(LOCAL_PATH)/proprietary/lib/egl/libEGL_adreno200.so:system/lib/egl/libEGL_adreno200.so \
$(LOCAL_PATH)/proprietary/lib/egl/libq3dtools_adreno200.so:system/lib/egl/libq3dtools_adreno200.so
#
# HW
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/proprietary/lib/hw/gps.venue.so:system/lib/hw/gps.venue.so \
$(LOCAL_PATH)/proprietary/lib/hw/gralloc.qsd8k.so:system/lib/hw/gralloc.qsd8k.so \
$(LOCAL_PATH)/proprietary/lib/hw/hwcomposer.qsd8k.so:system/lib/hw/hwcomposer.qsd8k.so \
$(LOCAL_PATH)/proprietary/lib/hw/copybit.qsd8k.so:system/lib/hw/copybit.qsd8k.so \
$(LOCAL_PATH)/proprietary/lib/hw/sensors.venue.so:system/lib/hw/sensors.venue.so
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/proprietary/bin/qmuxd:system/bin/qmuxd \
$(LOCAL_PATH)/proprietary/bin/calibrate:system/bin/calibrate \
$(LOCAL_PATH)/proprietary/bin/sensors_daemon:system/bin/sensors_daemon \
$(LOCAL_PATH)/proprietary/lib/libauth.so:system/lib/libauth.so \
$(LOCAL_PATH)/proprietary/lib/libcm.so:system/lib/libcm.so \
$(LOCAL_PATH)/proprietary/lib/libbluedroid.so:system/lib/libbluedroid.so \
$(LOCAL_PATH)/proprietary/lib/libdiag.so:system/lib/libdiag.so \
$(LOCAL_PATH)/proprietary/lib/libdsutils.so:system/lib/libdsutils.so \
$(LOCAL_PATH)/proprietary/lib/libdsm.so:system/lib/libdsm.so \
$(LOCAL_PATH)/proprietary/lib/libgsdi_exp.so:system/lib/libgsdi_exp.so \
$(LOCAL_PATH)/proprietary/lib/libgstk_exp.so:system/lib/libgstk_exp.so \
$(LOCAL_PATH)/proprietary/lib/libidl.so:system/lib/libidl.so \
$(LOCAL_PATH)/proprietary/lib/libmmjpeg.so:system/lib/libmmjpeg.so \
$(LOCAL_PATH)/proprietary/lib/libmmipl.so:system/lib/libmmipl.so \
$(LOCAL_PATH)/proprietary/lib/libmmgsdilib.so:system/lib/libmmgsdilib.so \
$(LOCAL_PATH)/proprietary/lib/libnv.so:system/lib/libnv.so \
$(LOCAL_PATH)/proprietary/lib/liboncrpc.so:system/lib/liboncrpc.so \
$(LOCAL_PATH)/proprietary/lib/liboem_rapi.so:system/lib/liboem_rapi.so \
$(LOCAL_PATH)/proprietary/lib/liboverlay.so:system/lib/liboverlay.so \
$(LOCAL_PATH)/proprietary/lib/libpbmlib.so:system/lib/libpbmlib.so \
$(LOCAL_PATH)/proprietary/lib/libqueue.so:system/lib/libqueue.so \
$(LOCAL_PATH)/proprietary/lib/libqmi.so:system/lib/libqmi.so \
$(LOCAL_PATH)/proprietary/bin/lightsensor:system/bin/lightsensor \
$(LOCAL_PATH)/proprietary/lib/libwmsts.so:system/lib/libwmsts.so \
$(LOCAL_PATH)/proprietary/lib/libwms.so:system/lib/libwms.so
Click to expand...
Click to collapse
If someone wanna to have copy of boot.img and system.img.. I will be happy to share or I will rebuild and create cwr-flashable-zip
FASTBOOT FLASHABLE IMAGES
attached boot.img flashable via fastboot and can recognize adb command
From Cyanogenmod wiki
In short: yes, you have to use updated adb tools (read:sdk).
Also, could you provide us with default.prop for this build?
Sent from my Dell Streak Pro using xda app-developers app
Kibuuka
Ok I will provide this evening upon reach my pc. Im mobile now
sent by Tapatalk on Android Device
x1123 said:
Kibuuka
Ok I will provide this evening upon reach my pc. Im mobile now
sent by Tapatalk on Android Device
Click to expand...
Click to collapse
lil' explanation: ro.adb.secure=1 is default setting sitting in default.prop, enforcing secure adb. I suggest setting it to 0 (at build time - change it and rebuild boot.img) to make adb useable in pre-interface-available stages (since current build isn't able to boot into graphical interface yet).
kibuuka said:
wiki.cyanogenmod.org/w/Doc:_adb_intro#Secure_USB_Debugging_.28NEW_in_Android_4.2.2.29
In short: yes, you have to use updated adb tools (read:sdk).
Also, could you provide us with default.prop for this build?
Sent from my Dell Streak Pro using xda app-developers app
Click to expand...
Click to collapse
ATTACHED .. indeed since GB build I made this ... ro.secure=0
x1123 said:
ATTACHED .. indeed since GB build I made this ... ro.secure=0
Click to expand...
Click to collapse
Just add ro.adb.secure=0 in there and you're all (in theory ) set.
Erm.
Kernel feature proposal (sort of): I'm currently messing with kernel for my primary device (Streak Pro). While doing this i've did number of things (easiest part was bumping to 2.6.35.14 from .11 it originally had) including:
1. added bcmdhd driver (venue uses bcm4329, am i right? if so, #1 is useable)
2. updated kgsl (kernel part of adreno drivers) to version 3.10 (opposed to 3.8 dsc kernel has at the moment)
Both these are easily portable so i can update my dsc fork (making a pull request on completion so it gets included in main dsc repo) if we're interested.
kibuuka said:
Just add ro.adb.secure=0 in there and you're all (in theory ) set.
Click to expand...
Click to collapse
sorry I overlooked your post ... probably I'm boring to see this script .... many thanks for point out
Erm.
Kernel feature proposal (sort of): I'm currently messing with kernel for my primary device (Streak Pro). While doing this i've did number of things (easiest part was bumping to 2.6.35.14 from .11 it originally had) including:
1. added bcmdhd driver (venue uses bcm4329, am i right? if so, #1 is useable)
2. updated kgsl (kernel part of adreno drivers) to version 3.10 (opposed to 3.8 dsc kernel has at the moment)
Both these are easily portable so i can update my dsc fork (making a pull request on completion so it gets included in main dsc repo) if we're interested.
Click to expand...
Click to collapse
Yessss ... venue wifi is bcm4329 ... I don't mind to patch kernel etc. However patching kernel's drivers in many of situation WE DON'T KNOW what should be patched kernel is low level programming which is far away from my knowledge and capability
on adb
Could you be more specific on
I can Not do adb logcating since the file /system/bin/sh is symlinks from /system/bin/mksh
Click to expand...
Click to collapse
Are you trying to say you're getting:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
when issuing adb logcat? If yes, this indicates that's /system ain't mounted, there's noting regarding sh being symlink to mksh.
You need to check your init.*.rc to find what's wrong.
If adb doesn't seem to run at all -
add:
Code:
ADDITIONAL_DEFAULT_PROPERTIES += \
ro.secure=0 \
ro.adb.secure=0 \
ro.allow.mock.location=1 \
ro.debuggable=1 \
persist.service.adb.enable=1
to device's .mk file, remove /out/target/product/YOURDEVICE/root/ (to make sure it will be regenerated - sometimes)
and issue make. This will rebuild boot.img and from now on it will contain above-mentioned properties in default.prop
If you're referring to _other_ problem with adb - again, be more specific.
Hi Kib,
I believed you are know better to Android related. I think AOKP did not support QSD8k device, but Evervolv did. Is it correct my understanding, build qsd8k device will be much easier with evervolv code base rather than AOKP, since I'm NOT capable to port a device from scratch. upon a source tree basically support a device, we will easier to add another device with similar platform. At least most most codebase is available and we can use as Template . Even about 80% the code base is similar for aokp, cm10, avervolv ...they are in same boat.
I hold my build test on JB and spent time to poke qsd8k Camera for DV on 4.0 rom. Another question do you thing we can bring device configuration from 4.0 to 4.1 / 4.2 (?) my Understanding 4.0 is louzy android version but 4.1/4.2 is barely smooth, lightweight Just my personal opinion , my crespo run a lot of better on JB than ICS. My linux's friend told me ICS is like linuxmint / ubuntu in linux distro camp. linux mint and ubuntu is FAT linux distro, but easier to boot in various PC machine. JB is more specific and "tighter" thus more difficult to boot, but very slim and fast.
back to source tree ... do you any suggestion. which source tree, better for building and porting dell venue : cm-10 / aokp JB or evervolv JB
Thanks a lot
To be honest - haven't checked evervolv for about an year. But - if it still supports nexus one as a target device - it will be tree of choice.
any news?
Any news on this rom or ics rom?
Sent from my Dell Venue using xda app-developers app
x1123 said:
ATTACHED .. indeed since GB build I made this ... ro.secure=0
Click to expand...
Click to collapse
any improvement in developing jelly bean for venue?
I have been 1824 km away from my compiling machine and last couple days in July I try to make camera working for ICS rom, but still no lucks. I saw available reference for qsd8k running jelly bean. The best reference is in xperia project, but still a lot of code base need to be rewrote. Most time I busy with "Hardware" tweak and play with some kinds of boxes .... but I will continue to build this JB aokp
Any news on the development of jb?
Sent from my Dell Venue using xda app-developers app
terminal17 said:
Any news on the development of jb?
Sent from my Dell Venue using xda app-developers app
Click to expand...
Click to collapse
I'm still on holiday and going to take a look into my source in this coming week end. Frankly, I little bit pesimistic with available code base in which I have no capability to write from scratch
jb
x1123 said:
I'm still on holiday and going to take a look into my source in this coming week end. Frankly, I little bit pesimistic with available code base in which I have no capability to write from scratch
Click to expand...
Click to collapse
pls try something and bring out a rom! so tat v can test and go ahead
Can anyone reupload the rom??
Sent from my Dell Venue using xda app-developers app
Any news on development of ics or jb rom for our dear dell venue?
Sent from my Dell Venue using xda app-developers app
x1123 said:
ATTACHED .. indeed since GB build I made this ... ro.secure=0
Click to expand...
Click to collapse
Can you pls help me how to install jelly bean on dell venue
I'm compiling android from source. I've set up the environment, and tested the builds. Everything works fine.
My current objective is to add 10 custom xml files to /system/etc/permissions. I've tried modifying the Android.mk file in frameworks/base/data/etc to include the files, but the additions aren't appearing in the compiled system. What's strange is that the default files that were in the same folder and already in the makefile appear, so the makefile seems to be read and parsed at compile.
This is the code I'm using:
Code:
LOCAL_PATH := $(my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE := [B]default_file_already_present.xml[/B]
LOCAL_MODULE_CLASS := ETC
LOCAL_MODULE_PATH := $(TARGET_OUT)/permissions
LOCAL_SRC_FILES := $(LOCAL_MODULE)
include $(BUILD_PREBUILT)
include $(CLEAR_VARS)
LOCAL_MODULE := [B]my_custom_file.xml[/B]
LOCAL_MODULE_CLASS := ETC
LOCAL_MODULE_PATH := $(TARGET_OUT)/permissions
LOCAL_SRC_FILES := $(LOCAL_MODULE)
include $(BUILD_PREBUILT)
For some reason, my_custom_file is not added, while the default_file_already_present is. Any ideas?
I've searched around, but can't find any decent documentation. I feel like I’m very close, so any help is much appreciated!
tl;dr - Adding files to system partition with makefile partially fails.
Solution!
For those who also run in to this problem:
As per Jean-Baptiste Quéru's post on a google group;
The Android makefiles are essentially split into 2 primary categories,
parsed in this order.
-the product definitions, which specify what modules need to be
installed for each product.
-the module definition, which specify how to build each module.
The build system protects itself against situation where you modify
the product definition from a module definition. PRODUCT_COPY_FILES is
part of the product definition, and can't be modify from a module
definition.
JBQ
Click to expand...
Click to collapse
What this means is that in order to copy files as is to the system image, we need to use product definitions.
What I did was first run ./build/envsetup.sh, in order to get access to commands like mgrep, etc.
I noticed that in frameworks/base/data/keyboards there was a keyboards.mk file, which got included correctly.
I made a copy and modifies it to suit my needs:
Code:
# Copyright (C) 2010 The Android Open Source Project
#
blah blah blah...
#
# This is the list of custom permissions to be injected in /system/etc/permissions
permissionsfiles := \
android.hardware.camera.front.xml \
android.hardware.usb.accessory.xml \
android.hardware.usb.host.xml \
android.hardware.wifi.direct.xml \
android.hardware.wifi.xml \
android.software.sip.voip.xml \
com.google.android.maps.xml \
com.google.android.media.effects.xml \
com.google.widevine.software.drm.xml \
handheld_core_hardware.xml \
platform_plus.xml \
features.xml
PRODUCT_COPY_FILES := $(foreach file,$(permissionsfiles),\
frameworks/base/data/etc/$(file):system/etc/permissions/$(file))
I ran "mgrep keyboards" and noted which makefiles included the keyboards.mk file, then I opened each file and duplicated that line, modifying it to instead include my custom_permissions.mk located in frameworks/base/data/etc/.
I compiled and the files were all there.
Hope this helps.
I am working with AOSP. I downloaded the Gingerbread 2.3.7 code and compiled successfully. Now I added an apk in the system/apps/ folder. After running make it is compiled successfully and the installed-files.txt contain the name of apk I included. But once I run the emulator after replacing the system.img, user.img and ramdisk generated in the out folder, I am unable to see the app in emulator anywhere.
Makefile
LOCAL_PATH := $(call my-dir) include $(CLEAR_VARS)
# Module name should match apk name to be installed.
LOCAL_MODULE := ThemeChooser
LOCAL_SRC_FILES := $(LOCAL_MODULE).apk
LOCAL_MODULE_CLASS := APPS
LOCAL_MODULE_TAGS := optional
LOCAL_CERTIFICATE := PRESIGNED
LOCAL_MODULE_SUFFIX := $(COMMON_ANDROID_PACKAGE_SUFFIX)
include $(BUILD_PREBUILT
hi, i want to build my custom rom from the source of PixelExperience with my app included as system app.
I already built the rom and flashed it with success on my asus x00dt.
what i tried to include my app as system app on the rom:
- added folder ./packages/apps/MyApp
- copied my.awesome.app.apk to folder
- created Android.mk in same folder with following content
Makefile:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE := MyApp
LOCAL_CERTIFICATE := PRESIGNED
LOCAL_SRC_FILES := my.awesome.app.apk
LOCAL_MODULE_CLASS := APPS
LOCAL_MODULE_SUFFIX := $(COMMON_ANDROID_PACKAGE_SUFFIX)
include $(BUILD_PREBUILT)
when i build and flash the rom the app is "not installed". but i can see the folder and app under /system/app
also when i run "pm list packages" i dont see it in the list.
Could you guys help me adding the app to my custom rom?
EDIT:
I also created an entry in build\make\target\product\handheld_product.mk
PRODUCT_PACKAGES += \
MyApp
i could not find core.mk or common.mk which was mentioned in other posts (here: https://stackoverflow.com/questions/10579827/how-do-i-add-apks-in-an-aosp-build)
EDIT 2:
Seems like a signing issue. If i dont sign my app and use LOCAL_CERTIFICATE := platform it works.