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.
In here you will find all info about development for the x86 architecture on the Galaxy Tab3
In the OP I will try to gather all info I can find, and what others post here.
Post below I will post my own personal dev stuff
THIS IS ONLY FOR DEVELOPMENT
IF YOUR NOT DEVELOPING PLEASE DON'T POST
If you want to say Thanks... use the button
Links
ANDROID ON INTEL ARCHITECTURE
Google group Android x86
Recovery
My current recovery is build on Android 4.2.1
This made me compile it, and usable.
But we want more and better features, and so we need it on Android 4.2.2
But this doesn't compile
My Setup:
Ubuntu 13.04
Java 6.0
make 3.82
ADT bundle x86_64 (latest)
My current BoardConfig.mk
Code:
USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/samsung/santos10wifi/BoardConfigVendor.mk
TARGET_ARCH := x86
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := clovertrail
TARGET_CPU_ABI := x86
TARGET_CPU_ABI2 := x86
TARGET_ARCH_VARIANT := x86-atom
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_BOOTLOADER_BOARD_NAME := santos10wifi
#TARGET_KERNEL_SOURCE := kernel/samsung/santos10wifi
#TARGET_KERNEL_CONFIG := android_santos10_open_r00_user_defconfig
BOARD_KERNEL_CMDLINE := init=/init pci=noearly console=ttyS0 console=logk0 earlyprintk=nologger loglevel=4 hsu_dma=7 kmemleak=off androidboot.bootmedia=sdcard androidboot.hardware=santos10wifi androidboot.spid=xxxx:xxxx:xxxx:xxxx:xxxx:xxxx androidboot.serialno=01234567890123456789012345678901 ip=50.0.0.2:50.0.0.1::255.255.255.0::usb0:on vmalloc=172M
BOARD_KERNEL_BASE := 0x10000000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
TARGET_PREBUILT_KERNEL := device/samsung/santos10wifi/kernel
BOARD_HAS_NO_SELECT_BUTTON := true
DEVICE_RESOLUTION := 2560x1600
#graphics modes
TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
#TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
#TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"
My current recovery.fstab:
Code:
/efs ext4 /dev/block/mmcblk0p2
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
/recovery emmc /dev/block/mmcblk0p11
/modem emmc /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/boot emmc /dev/block/mmcblk0p10
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1
More info
Just now i got all 3 open source pakages from samsung, and see how different they are, and see if I can find a solution.
While compiling a recovery, I use this:
make -j3 otatools or make ARCH=x86 CROSS_COMPILE=$CCOMPILER otatools
build/tools/device/mkvendor.sh samsung santos10wifi prebuilt/kernel/samsung/santos10wifi/boot.img
. build/envsetup.sh
lunch cm_santos10wifi-eng
. build/tools/device/makerecoveries.sh cm_santos10wifi-eng or make -j3 recoveryimage or make ARCH=x86 CROSS_COMPILE=$CCOMPILER recoveryimage
And get these errors:
Code:
target SharedLib: libc (/home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/SHARED_LIBRARIES/libc_intermediates/LINKED/libc.so)
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/SHARED_LIBRARIES/libc_intermediates/bionic/pthread.o: in function pthread_create:bionic/libc/bionic/pthread.c:374: error: undefined reference to '_thread_created_hook'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/SHARED_LIBRARIES/libc_intermediates/bionic/dlmalloc.o: in function sys_alloc.constprop.11:bionic/libc/bionic/../upstream-dlmalloc/malloc.c:3198: error: undefined reference to 'pthread_atfork'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/SHARED_LIBRARIES/libc_intermediates/bionic/dlmalloc.o: in function sys_trim.constprop.13:bionic/libc/bionic/../upstream-dlmalloc/malloc.c:3198: error: undefined reference to 'pthread_atfork'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/SHARED_LIBRARIES/libc_intermediates/bionic/dlmalloc.o: in function dlmalloc:bionic/libc/bionic/../upstream-dlmalloc/malloc.c:3198: error: undefined reference to 'pthread_atfork'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/SHARED_LIBRARIES/libc_intermediates/bionic/dlmalloc.o: in function dlvalloc:bionic/libc/bionic/../upstream-dlmalloc/malloc.c:3198: error: undefined reference to 'pthread_atfork'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(regcomp.o): in function p_b_cclass:bionic/libc/upstream-netbsd/libc/regex/regcomp.c:1434: error: undefined reference to 'strcpy'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(fgetln.o): in function fgetln:bionic/libc/stdio/fgetln.c:85: error: undefined reference to 'memchr'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(fgetln.o): in function fgetln:bionic/libc/stdio/fgetln.c:126: error: undefined reference to 'memchr'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(fgets.o): in function fgets:bionic/libc/stdio/fgets.c:83: error: undefined reference to 'memchr'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(fvwrite.o): in function __sfvwrite:bionic/libc/stdio/fvwrite.c:171: error: undefined reference to 'memchr'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(strtod.o): in function __dtoa:bionic/libc/stdlib/strtod.c:2158: error: undefined reference to 'strcpy'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(__strcpy_chk.o): in function __strcpy_chk:bionic/libc/string/__strcpy_chk.c:55: error: undefined reference to 'strcpy'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(asctime.o): in function asctime_r:bionic/libc/tzcode/asctime.c:117: error: undefined reference to 'strcpy'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(fork.o): in function fork:bionic/libc/bionic/fork.c:44: error: undefined reference to '__timer_table_start_stop'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(fork.o): in function fork:bionic/libc/bionic/fork.c:45: error: undefined reference to '__bionic_atfork_run_prepare'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(fork.o): in function fork:bionic/libc/bionic/fork.c:62: error: undefined reference to '__bionic_atfork_run_child'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(fork.o): in function fork:bionic/libc/bionic/fork.c:49: error: undefined reference to '__timer_table_start_stop'
/home/dutchdanny/android/source/cm/10.1/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/../../../../i686-linux-android/bin/ld: /home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(fork.o): in function fork:bionic/libc/bionic/fork.c:50: error: undefined reference to '__bionic_atfork_run_parent'
collect2: ld returned 1 exit status
make: *** [/home/dutchdanny/android/source/cm/10.1/out/target/product/santos10wifi/obj/SHARED_LIBRARIES/libc_intermediates/LINKED/libc.so] Error 1
Something with libc
and/or
error: undefined reference to 'memchr'
Ok. Good thread! Some questions:
In your BoardConfig.mk -
1. ARCH_ARM_HAVE_TLS_REGISTER := true - what is it for? It is for ARM architecture and don't used for us, as i know.
2. DEVICE_RESOLUTION := 2560x1600 - this row is only used for TWRP and don't needed for CWM and system (ignored). If we build TWRP it's must be DEVICE_RESOLUTION := "1280x800". (with quotes)
As for you error - i think that problem in GCC compiler.
I will try to use your recovery.fstab last 2 rows for building TWRP (building OK, but do not mount internal storage automaticaly).
P.S. If anyone have problems with last NFS MostWanted game, try to add this lines in powervr.ini file in etc folder:
Code:
[com.ea.games.nfs13_row]
DefaultVertexBufferSize=3584000
MaxVertexBufferSize=4096000
DefaultPDSVertBufferSize=768000
DefaultVDMBufferSize=102400
DefaultIndexBufferSize=1024000
DefaultPregenMTECopyBufferSize=256000
PDSFragBufferSize=768000
ParamBufferSize=104857600
MaxParamBufferSize=125829120
Wit this, i can play well.
DutchDanny said:
Just now i got all 3 open source pakages from samsung, and see how different they are, and see if I can find a solution.
Click to expand...
Click to collapse
What do you mean by 3 open source packages? Where did you get them? The ones that are available here http://o7.no/19M7ZUX on samsung's opensource website?
Yes, original and update1 & update2
Send via my BinDroided HTC ONE
DutchDanny said:
Yes, original and update1 & update2
Send via my BinDroided HTC ONE
Click to expand...
Click to collapse
Thanks. So basically you overlaid all 3 files on the the original CyanogenMod 10.1 sources?
I already downloaded these 3 packages but (original, update1 and update2) but they don't really differ. Did you manually create a santos10 product target?
xmaczi123 said:
Thanks. So basically you overlaid all 3 files on the the original CyanogenMod 10.1 sources?
I already downloaded these 3 packages but (original, update1 and update2) but they don't really differ. Did you manually create a santos10 product target?
Click to expand...
Click to collapse
I did not overlay it to CM, but to aosp, but only with update2... just downloaded all to look inside, but as you saw.. they don't differ much.
The base of the target is created when you:
build/tools/device/mkvendor.sh samsung santos10wifi prebuilt/kernel/samsung/santos10wifi/boot.img
then edit the boardconfig.mk to fit it...
Will try to setup a full device tree by hand later on, so we can build a real cm.
But a good functional recovery is needed first
DutchDanny said:
I did not overlay it to CM, but to aosp, but only with update2... just downloaded all to look inside, but as you saw.. they don't differ much.
The base of the target is created when you:
build/tools/device/mkvendor.sh samsung santos10wifi prebuilt/kernel/samsung/santos10wifi/boot.img
then edit the boardconfig.mk to fit it...
Will try to setup a full device tree by hand later on, so we can build a real cm.
But a good functional recovery is needed first
Click to expand...
Click to collapse
Unfortunately I can't find mkvendor.sh in the whole working directory. How did you get hold of it? I'm also guessing that you copied the boot.img from the existing stock ROM. Am I right?
Thanks.
xmaczi123 said:
Unfortunately I can't find mkvendor.sh in the whole working directory. How did you get hold of it? I'm also guessing that you copied the boot.img from the existing stock ROM. Am I right?
Thanks.
Click to expand...
Click to collapse
Yes I'm using the stock boot.img
All others are made by info I found
Send via my BinDroided HTC ONE
DutchDanny said:
Yes I'm using the stock boot.img
All others are made by info I found
Send via my BinDroided HTC ONE
Click to expand...
Click to collapse
Why do we actually need a working stock recovery in order to compile and use ASOP? Can't we just create a tar.md5 archive and flash it with Odin?
xmaczi123 said:
Why do we actually need a working stock recovery in order to compile and use ASOP? Can't we just create a tar.md5 archive and flash it with Odin?
Click to expand...
Click to collapse
We need stock recovery to build initial device config and tree in source. If i understood your question...
Now then folks,
I'm seriously contemplating getting one of these for my next distraction, although with it being an x86 device, there's still some fun for all the family with or without the hardware,
@DutchDanny You seem to be leading a bit of a charge with this one, you done much raw porting in the past?
I've got the kernel and a 4.2.2 Rom that I've been poking around in, It shouldn't be too difficult to get something going, these some patches requiring in CM build system to add bz kernel image support but If there been following the AOSP bionic etc it should be okay.
trevd said:
Now then folks,
I'm seriously contemplating getting one of these for my next distraction, although with it being an x86 device, there's still some fun for all the family with or without the hardware,
@DutchDanny You seem to be leading a bit of a charge with this one, you done much raw porting in the past?
I've got the kernel and a 4.2.2 Rom that I've been poking around in, It shouldn't be too difficult to get something going, these some patches requiring in CM build system to add bz kernel image support but If there been following the AOSP bionic etc it should be okay.
Click to expand...
Click to collapse
I'm more an HTC guy, and not often work from source beside kernels.
I do know some about aosp, cm etc.
But when on HTC, I modify what they make.
For now the updater-binary is killing custom roms.
When I have a bit more time I will return....
3 other devices need support.
Send via my BinDroided HTC ONE
DutchDanny said:
I'm more an HTC guy, and not often work from source beside kernels.
I do know some about aosp, cm etc.
But when on HTC, I modify what they make.
For now the updater-binary is killing custom roms.
When I have a bit more time I will return....
3 other devices need support.
Send via my BinDroided HTC ONE
Click to expand...
Click to collapse
Yeah no worries, I need to build a cm-10.2 for x86 anyway, updater-binary. There might be a working one in this post http://forum.xda-developers.com/showpost.php?p=35887703&postcount=152 . Basically I built C x86 last year because I want to run it on my desktop but It's not really practical and I got stuck trying to make OpenGLes work with my radeon HD card. That is the CWM that resulted from the build. I just stashed it in a random edify related thread for future reference
Hey guys,
I'm trying to build a unofficial version of CM12.1, but it fails while building with following error:
Code:
build/core/package_internal.mk:351: *** target pattern contains no '%'. stop.
the corresponing line from package_interal:
Code:
[348] private_key := $(LOCAL_CERTIFICATE).pk8
[349] certificate := $(LOCAL_CERTIFICATE).x509.pem
[350]
[351] $(LOCAL_BUILT_MODULE): $(private_key) $(certificate) $(SIGNAPK_JAR)
[352] $(LOCAL_BUILT_MODULE): PRIVATE_PRIVATE_KEY := $(private_key)
[353] $(LOCAL_BUILT_MODULE): PRIVATE_CERTIFICATE := $(certificate)
If you need further information about device (i don't think that's revelant?) etc. just ask.
revide said:
Hey guys,
I'm trying to build a unofficial version of CM12.1, but it fails while building with following error:
Code:
build/core/package_internal.mk:351: *** target pattern contains no '%'. stop.
the corresponing line from package_interal:
Code:
[348] private_key := $(LOCAL_CERTIFICATE).pk8
[349] certificate := $(LOCAL_CERTIFICATE).x509.pem
[350]
[351] $(LOCAL_BUILT_MODULE): $(private_key) $(certificate) $(SIGNAPK_JAR)
[352] $(LOCAL_BUILT_MODULE): PRIVATE_PRIVATE_KEY := $(private_key)
[353] $(LOCAL_BUILT_MODULE): PRIVATE_CERTIFICATE := $(certificate)
If you need further information about device (i don't think that's revelant?) etc. just ask.
Click to expand...
Click to collapse
Sorry for this bump, but being on the fourth site without any replies kinda frustrates me..
cmon guys, halp
Okay, solved problem.
For all of you who experience the same issue, my proprietary-blob list got entries that were not real files. update yours and you should be good.
Note:
I noticed alot more people have been using MultiRom, So I decided to make a really simple basic How to guide for people who pretty much already know what they are doing.
Step #1, you need the omni source tree, I use Omni-lp5.1.1, But to use that, you will need to make some changes to your device tree, like g3-common and qcomm_common,
Only thing you will be doing to those to device tree sections, in g3-common you will remove the "liblight" directory. and in the qcomm_common Dir, you will remove The "power" Directory.
reason for that, because its already defined in hardware.. The above is only if you decide to use Omni LP trees.
If you use the Normal Omni KitKat 4.4.4, Then you dont have to remove anything.. should work right out of the box.
If using Omni 4.4.4, you can use your device from: https://github.com/TeamWin,
if your using Omni LP you can use your own device tree that works with LP..
Ok now for the code part:
open your BoardConfig.mk
and enter this at the bottom:
Code:
# Edited for TWRP Recovery
DEVICE_RESOLUTION := 1440x2560
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TW_NO_USB_STORAGE := true
TW_INCLUDE_JB_CRYPTO := true
TW_INCLUDE_CRYPTO := true
BOARD_SUPPRESS_SECURE_ERASE := true
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
TW_BRIGHTNESS_PATH := "/sys/devices/mdp.0/qcom\x2cmdss_fb_primary.175/leds/lcd-backlight/brightness"
TW_MAX_BRIGHTNESS := 255
TW_SCREEN_BLANK_ON_BOOT := true
# TW_NO_SCREEN_TIMEOUT := false
# MultiROM
MR_INPUT_TYPE := type_b
MR_INIT_DEVICES := device/lge/d851/multirom/mr_init_devices.c
MR_RD_ADDR := 0x2200000
MR_DPI := xhdpi
MR_DPI_MUL := 1.5
MR_FSTAB := device/lge/d851/twrp.fstab
MR_KEXEC_MEM_MIN := 0x0ff00000
MR_KEXEC_DTB := true
MR_USE_MROM_FSTAB := true
MR_DPI_FONT := 420
MR_DEFAULT_BRIGHTNESS := 80
#MR_CONTINUOUS_FB_UPDATE := true
#MultiRom Hooks, So that we can run stock roms as secondary
MR_DEVICE_HOOKS := device/lge/d851/mr_hooks.c
MR_DEVICE_HOOKS_VER := 4
Of course change your device name and locations.
You will need to make changes to omni_(your device).mk (AKA cm_(your device).mk
and add this to it:
Code:
# Copy needed files to make everything work for recovery
PRODUCT_COPY_FILES += \
# device/lge/d851/kernel:kernel \
device/lge/d851/img_info:img_info \
device/lge/d851/postrecoveryboot.sh:recovery/root/sbin/postrecoveryboot.sh \
device/lge/d851/sign:recovery/root/res/sign
PRODUCT_COPY_FILES += device/lge/d851/fstab.g3:recovery/root/fstab.g3
PRODUCT_COPY_FILES += device/lge/d851/twrp.fstab:recovery/root/etc/twrp.fstab
PRODUCT_NAME := omni_d851
PRODUCT_DEVICE := d851
PRODUCT_BRAND := LG
PRODUCT_MODEL := G3
PRODUCT_MANUFACTURER := LG
Im not going to tell you how to get your own fstab. you should already know that.
You will need this for your hooks file: mr_hooks.c
I am sure you can see the location that it will go into, you can change it to meet your device spec.
Now read this for the rest of the way: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
I already created a patch that works very well with the latest MultiRom: D851-CM_hardboot_kexec_kernel.patch
Yes the patch says D851, but its for the G3 kernel which all models use. And yes, it will work with CM based and stock based. If anything you will have to change the config file settings
to match the ones for your device config. This one is set for the d851_defconfig.. So just point it to your config when it asks.
Command to run patch from terminal: patch --verbose -p1 < patch/D851-CM_hardboot_kexec_kernel.patch
Yes when you copy it over, place it in its own dir called patch from your kernel tree.
or if you rather take an already patched kernel: 777Kernel-patched Branch "Testing"
Above kernel was patched by me with pemish from @777jon, I did remove his patch created by @Skin1980 since it didnt work well with todays MultiRom
and I added in mine.. I also made some changes to allow Sabermod 5.1 and 6.0 to compile it.
Ok this is it for me, I told you it was a quick guide for people that already know what they are doing. I am no good at teaching. I wrote this really quick so that others
can have the ability to get MultiRom running on their device (Developers)..
I will only answer questions from Developers that plan on porting to thier device and make it public.
any1 working on this?
I honestly forgot that I posted this. I do hope that some are working on this for their device.
I just dont have the time to port over to every single G3 family device......
Hi,
I currently try building this one myself:
http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-0-samsung-express-gt-t2949359
it's CM 12.1 for the Samsung Galaxy Express GT-I8730
After hours of building it breaks with a missing library.
Code:
frameworks/testing/runner/src/main/java/android/support/test/internal/runner/ClassPathScanner.java:19: error: package android.support.annotation does not exist
import android.support.annotation.VisibleForTesting;
build/core/java.mk:346: recipe for target '~/src/cm-12.1-main/out/target/common/obj/JAVA_LIBRARIES/android-support-test-src_intermediates/classes-full-debug.jar' failed
make: *** [~/src/cm-12.1-main/out/target/common/obj/JAVA_LIBRARIES/android-support-test-src_intermediates/classes-full-debug.jar] Error 41
package android.support.annotation is missing. It's available here
Code:
./frameworks/support/annotations/src/android/support/annotation
./prebuilts/sdk/current/support/annotations/android-support-annotations.jar
But it's not included in build.
This is the code in question, in build/core/java.mk:346
Code:
# Compile the java files to a .jar file.
# This intentionally depends on java_sources, not all_java_sources.
# Deps for generated source files must be handled separately,
# via deps on the target that generates the sources.
$(full_classes_compiled_jar): PRIVATE_JAVACFLAGS := $(LOCAL_JAVACFLAGS)
$(full_classes_compiled_jar): PRIVATE_JAR_EXCLUDE_FILES := $(LOCAL_JAR_EXCLUDE_FILES)
$(full_classes_compiled_jar): PRIVATE_JAR_PACKAGES := $(LOCAL_JAR_PACKAGES)
$(full_classes_compiled_jar): PRIVATE_JAR_EXCLUDE_PACKAGES := $(LOCAL_JAR_EXCLUDE_PACKAGES)
$(full_classes_compiled_jar): PRIVATE_RMTYPEDEFS := $(LOCAL_RMTYPEDEFS)
$(full_classes_compiled_jar): PRIVATE_DONT_DELETE_JAR_META_INF := $(LOCAL_DONT_DELETE_JAR_META_INF)
$(full_classes_compiled_jar): $(java_sources) $(java_resource_sources) $(full_java_lib_deps) \
$(jar_manifest_file) $(layers_file) $(RenderScript_file_stamp) \
$(proto_java_sources_file_stamp) $(LOCAL_ADDITIONAL_DEPENDENCIES)
$(transform-java-to-classes.jar)
How do I find out the content of the variables? How do I modify it?
Since I am building from a branch, it probably is a temporary problem. I issued a repo sync, but it dit not help (yet).
any idea?
thanks
JPT