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

Root [Discussion - Developers _ONLY_] Building ICS from source (Isaac's github).

aaronfitz said:
Here's the error output -
Code: 
target R.java/Manifest.java: Camera (out/target/common/obj/APPS/Camera_intermediates/src/R.stamp)
aapt: warning: string 'help_page' has no default translation in packages/apps/Browser/res; found: af am ar be bg ca cs da de el en_GB es es_US et fa fi fr hi hr hu in it iw ja ko lt lv ms nb nl pl pt pt_PT ro ru sk sl sr sv sw th tl tr uk vi zh_CN zh_TW zu
device/motorola/triumph/overlay/packages/apps/Camera/res/values/config.xml:25: error: Resource at ffc_canFocus appears in overlay but not in the base package; use <add-resource> to add.
device/motorola/triumph/overlay/packages/apps/Camera/res/values/config.xml:26: error: Resource at ffc_canZoom appears in overlay but not in the base package; use <add-resource> to add.
device/motorola/triumph/overlay/packages/apps/Camera/res/values/config.xml:27: error: Resource at ffc_supportedEffects appears in overlay but not in the base package; use <add-resource> to add.
make: *** [out/target/common/obj/APPS/Camera_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....
Click to expand...

Check out my post #279 on this thread. You just need to delete the file.

After that you should bump into the problem noted in my post on this thread #301.

I'm not sure how well I did, but I tried to capture all of the edits done to get to a complete compile. I have not attempted to compile kernels yet. If I do so I'm likely to go back to the cm7 so that I can confirm a working ROM. Since I've been able to build there hasn't been a working ROM to test for cm9. I do have both cm7 and cm9 compiling to final zip under both Fedora 14 and 16.

I also have noted everything necessary for compiling under a Fedora Core 16 distribution of Linux. I haven't confirmed bootable ROM images yet, so I haven't posted it. It is available if anyone is running Fedora. I had it working with FC14 (i686) and now FC16 (x64).
 
I have a question for all the kernel makers out there:

What is required to make a new kernel for ICS? (Better yet, how do you make one for our device while running ICS?)

I know from other post (see http://androidforums.com/3722820-post305.html) we need a kernel with genlock... :/ I don't want to sound "impatient" or disrespectful to anyone here, I just want to learn how to do it, and more importantly, help our development of ICS. :)
 
lifeblows10 said:
I have a question for all the kernel makers out there:

What is required to make a new kernel for ICS? (Better yet, how do you make one for our device while running ICS?)

I know from other post (see http://androidforums.com/3722820-post305.html) we need a kernel with genlock... :/ I don't want to sound "impatient" or disrespectful to anyone here, I just want to learn how to do it, and more importantly, help our development of ICS. :)
Click to expand...

I have basically the same question. I know that we don't really want to start with the ICS linux 3.0 kernel, since that would be a challenge. The first step would be to get comfortable building one of the cm7 kernels. I believe that is what Whyzor is doing now with his reloaded ROM.

I had this past week to spend doing this, and I have spend more time on another project, mostly because I wasn't sure how to deal with the kernel issue here.
 
I followed this Cyanogenmod kernel building guide originally, and specifically for Mantera's TheOC kernel for CM7:

mkdir ~/android/kernel/
cd ~/android/kernel/
git clone git://github.com/mantera/WX_435_Kernel-CM7.git #----- or substitute with another github kernel link
cd WX_435_Kernel-CM7
cp config .config
CROSS_COMPILE=$CCOMPILER ARCH=arm make -j<#_of_cores>

When it's done, copy zImage to a new dir & run:

mkbootimg --kernel zImage --ramdisk ~/android/system/out/target/product/triumph/ramdisk.img --cmdline "console=ttyMSM1 androidboot.hardware=triumph" -o boot.img --base 0x00200000 --pagesize 4096

This creates a boot.img, which you can replace in a flashable zip.
 
You have to take out the genlock stuff.
The phone is trying to load the genlock driver but its failing. Like I said before there will be no ICS on the triumph untill that problem is fixed.
 
This thread is dying. Has development come to an instant halt? Been quite a few days, this used to be in the top 5 threads, constantly.
 
Well ticker guy and Isaac were the only real devs for this phone.
If Isaac doesnt come back we will prolly be stuck with CM7. I havent felt like messing around with the genlock stuff because with cm7 all my needs are covered. The phone is already really snappy and I doubt that hardware acceleration is not going to make anything faster but the launcher.

Also I cant port that well but Im looking into the desire ICS and Im gonna work off of that.
Because there kernel should kinda sorta work.
 
konspiracy said:
Well ticker guy and Isaac were the only real devs for this phone.
If Isaac doesnt come back we will prolly be stuck with CM7. I havent felt like messing around with the genlock stuff because with cm7 all my needs are covered. The phone is already really snappy and I doubt that hardware acceleration is not going to make anything faster but the launcher.

Also I cant port that well but Im looking into the desire ICS and Im gonna work off of that.
Because there kernel should kinda sorta work.
Click to expand...

That kinda sucks, it would be really cool to see ICS on the Triumph.

I'd be willing to try to learn and I have some experience Java coding, but a project this big is hard to know where to start. If anyone more experienced wants someone to bounce ideas off, let me know.
 
I just think people really want to see ICS on our device, and got overly excited about Isaacs remarkable early success. If it is possible to get all the drivers I'm sure we'll see it, but it is going to take some time.

It is really unrealistic for anyone to expect anything useful until an official Cm9 release. We might get parts working, but it will not be a usable phone for awhile after Cm9.0

This is just my opinion. I would love to be wrong, but I think I'm just being annoyingly realistic.
 
RedAnt said:
I just think people really want to see ICS on our device, and got overly excited about Isaacs remarkable early success. If it is possible to get all the drivers I'm sure we'll see it, but it is going to take some time.

It is really unrealistic for anyone to expect anything useful until an official Cm9 release. We might get parts working, but it will not be a usable phone for awhile after Cm9.0

This is just my opinion. I would love to be wrong, but I think I'm just being annoyingly realistic.
Click to expand...

i agree, and i think "im" annoyingly excited about cm9 on the triumph :D (but i try not to bug you guys too much)... if i new half the stuff about source that isaac, tickerguy, and you all do. id help, but sadly i dont lol. :p

BTW... where is isaac? havent heard from him in awhile. :(
 
Sorry for the late response. I've been working on merging some changes that may fix the genlock problem. I will recompile the kernel and post it soon.
 
I have a vmlinux file now with a size of 81 MB. I extracted the boot.img from an old rom and used the ramdisk to create a new boot.img. However, the file size of the new boot.img is 81 MB. What am I doing wrong?
 
can someone post a not booting copy of the system files? you know for the people who dont have linux can try to do stuff to this...
 
Ended up wiping out the laptop & reinstalled Ubuntu 10.04. Haven't been able to get a clean sync for the past couple days. As soon as I can I'll try out the kernel. Posting this from the nook running ics. Now really hoping to see it on the phone. It's quite nice.
 
You must log in or register to reply here.
Back
Top Bottom