• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM10 Development (moved to upp)

Sorry, it got really late by the time I got home last night. Thank you so much for all the helpful info. I will be trying some of this out in a while. Just woke up and excited :)
 
its all good, i aint tryin to rush ya, just wanted to make sure to put everything that popped into my head out there. i may not be able to really do much on this one myself but i wanna do everything i can to get it running, and we are about to have the first rom release shortly if you hadnt noticed, shinru is uploading now XD
 
you never know which random thought could be the key to figuring it all out, so youre just gonna have to hear them all lol
 
just tried building arthur, but didn't get very far. Here is the output:

superr@ubuntu:~/android$ . build/envsetup.sh && brunch arthur
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including device/zte/arthur/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/arthur/cm.mk]]: "device/*/arthur/cm.mk" does not exist. Stop.
Device arthur not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for arthur not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/arthur/cm.mk]]: "device/*/arthur/cm.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_arthur'
** Do you have the right repo manifest?

No such item in brunch menu. Try 'breakfast'
 
ok and you did all the envsetup and vendorsetup and crap like that?


i mean it shouldnt be TOO hard to recreate one that looks like ours for the arthur but i am not sure it will work right
may not have all necessary info ya kno

try going through the stuff step by step again starting with envsetup

then if that doesnt work you can take the one from our cwm and modify it, there are only 5 things to change in there so it wont be difficult but like i said it might not work either
 
ok, got over my first big hurdle and surprisingly it was a problem with git and the cm10 source using the wrong links to the file libjackpal-androidterm4.so.

Building now using our device tree and some new things i have learned :)
 
Fingers Crossed Cm10 will make this device a beast. Most issues with ZTE devices are caused my crappy coding and/or source on ZTE's part.

I think the massively high ram usage is due to ZTE's modifications to the android source code they used when making the sequent.
 
Ahhh, so close and I am now officially lost. Maybe someone can help. This is the error in the final stages of the build:

+ ENABLE_SPARSE_IMAGE=
+ '[' -s = -s ']'
+ ENABLE_SPARSE_IMAGE=-s
+ shift
+ '[' 5 -ne 4 -a 5 -ne 5 -a 5 -ne 6 ']'
+ SRC_DIR=/home/superr/android/out/target/product/warp2/data
+ '[' '!' -d /home/superr/android/out/target/product/warp2/data ']'
+ OUTPUT_FILE=/home/superr/android/out/target/product/warp2/userdata.img
+ EXT_VARIANT=ext4
+ MOUNT_POINT=data
+ SIZE=0x105c0000
+ FC=
+ case $EXT_VARIANT in
+ '[' -z data ']'
+ '[' -z 0x105c0000 ']'
+ '[' -n '' ']'
+ MAKE_EXT4FS_CMD='make_ext4fs -s -l 0x105c0000 -a data /home/superr/android/out/target/product/warp2/userdata.img /home/superr/android/out/target/product/warp2/data'
+ echo make_ext4fs -s -l 0x105c0000 -a data /home/superr/android/out/target/product/warp2/userdata.img /home/superr/android/out/target/product/warp2/data
make_ext4fs -s -l 0x105c0000 -a data /home/superr/android/out/target/product/warp2/userdata.img /home/superr/android/out/target/product/warp2/data
+ make_ext4fs -s -l 0x105c0000 -a data /home/superr/android/out/target/product/warp2/userdata.img /home/superr/android/out/target/product/warp2/data
Need size of filesystem
+ '[' 1 -ne 0 ']'
+ exit 4
error: failed to build /home/superr/android/out/target/product/warp2/userdata.img from /home/superr/android/out/target/product/warp2/data
make: *** [/home/superr/android/out/target/product/warp2/userdata.img] Error 1
make: *** Deleting file `/home/superr/android/out/target/product/warp2/userdata.img'
 
nope, I am a total noob at building android so any help would be wonderful.
 
uhhh, actually, I think junkie2100 did that in our device tree

BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000

this is from our BoardConfig.mk file
 
Problem: cm10 won't build because the partition sizes are not defined

Solution: I figured out how to get the partition sizes in bytes, but I have no clue how to convert bytes to the format used in BoardConfig.mk. I have been searching google for 2 hours :(

the format it needs to be in is like 0x105c0000
 
downthemachine said:
Just set the user data to match the warp 1 boardconfig.mk
Click to expand...

Thank you for the tip, the warp boardconfig.mk does not use the hex format so I guess it is not necessary. Ok, problem solved.

New problem: it appears as though the warp partition sizes are in bytes which is great as that is easy to determine. However, my data partition on my phone is a different size than the warp data partition.

from warp boardconfig:
BOARD_USERDATAIMAGE_PARTITION_SIZE := 2908749824

My phones data partition is 2757529600

I realize the numbers are very close, but should I redo all of them assuming all of them are a little different or am I making way too big of a deal out of this? :)
 
so after figuring out all the partitions on my phone, here are the diffs:

Mine:
BOARD_BOOTIMAGE_PARTITION_SIZE := 16777216
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 16777216
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 520167424
BOARD_USERDATAIMAGE_PARTITION_SIZE := 2757529600
BOARD_CACHEIMAGE_PARTITION_SIZE := 313737216
BOARD_PERSISTIMAGE_PARTITION_SIZE := 8241152

original warps:
BOARD_BOOTIMAGE_PARTITION_SIZE := 16777216
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 16777216
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 524288000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 2908749824
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 8388608
 
no go...here is the terminal output if anyone cares. I will work on this and try again later.

target thumb C++: libmedia <= frameworks/av/media/libmedia/Visualizer.cpp
make: *** [/home/superr/android/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
 
superr said:
ok, building using my phones numbers now. I will report back. Thanks again for your help downthemachine!!!
Click to expand...

good stuff XD
thanks for pitching in guys, and sorry i wasnt up, i already figured out all the partition sizes and everything probably woulda saved you some time and trouble. examined the /proc/partitions file and multiplied the block sizes by 1024 to convert to bytes because each block is 1kb
hope this works, keep us updated superr and if you run into any more issues ill be here for a few at least

edit...
damn
 
alright, so did you ever try building hoarks source as is? to see if it was compatable? and that is kinda messed up that isnt even anything that we have in our source i dont think that is cm original stuff
 
figured it out, its openjdk

use sun java

Oracle Java Development Kit 6 Downloads

then make sure you are using that one to build after installing
this command here is said to fix that association somehow tho i dont know exactly how it works

[FONT=Courier, Monospaced]sudo update-alternatives --config jar[/FONT]
 
superr said:
no go...here is the terminal output if anyone cares. I will work on this and try again later.

target thumb C++: libmedia <= frameworks/av/media/libmedia/Visualizer.cpp
make: *** [/home/superr/android/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Click to expand...

Google the errors, common errors have easy fixes. There is a thread on xda for building jb and it has fixes to most build errors. They are common and usually just broken files. Sorry I don't remember the link off hand. I've run into this often building ics and cm10 when first starting with the repo'd source
 
You must log in or register to reply here.
Back
Top Bottom