• 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).

fatal: manifest 'default.xml' not available
fatal: no name in <project> within /root/CM7/.repo/manifests/default.xml


Set up a brand new linux build environment on my laptop. Its doing this on both my laptop and desktop.

I did a repo init on your ics and it works fine. I guess I'll just try to build that. It will build correctly right?

sorry. I missed a line when I updated the default.xml file for gingerbread. It's fixed. You can try again if you want.

As for my ics repo, it probably won't build yet or boot. I haven't pushed up my device files yet.

If you run into anymore problems syncing, I won't be able to get to a computer until late tonight or tomorrow.
 
sorry. I missed a line when I updated the default.xml file for gingerbread. It's fixed. You can try again if you want.

As for my ics repo, it probably won't build yet or boot. I haven't pushed up my device files yet.

If you run into anymore problems syncing, I won't be able to get to a computer until late tonight or tomorrow.
I too had the same error as afore mentioned. I used your repo init to update mine and will try a build shortly. Question, are the updates that Whyzor listed in his/your build also in your repo? If so, great, because I had to switch to TG reloaded after I inadvertently caused some stability issues with my setup (trying to make changes while running). I want to try ICS, but my computer may actually be too slow to build it. I still have a 32 bit machine and I need to upgrade badly.
 
I too had the same error as afore mentioned. I used your repo init to update mine and will try a build shortly. Question, are the updates that Whyzor listed in his/your build also in your repo? If so, great, because I had to switch to TG reloaded after I inadvertently caused some stability issues with my setup (trying to make changes while running). I want to try ICS, but my computer may actually be too slow to build it. I still have a 32 bit machine and I need to upgrade badly.

It's current with Whyzor's stuff as of 4 days ago or so. Yes.
 
Im talking to edowar right now.

I kept getting errors with the networking modules not being there so i gave up.
But i need to get his commits that make hardware accel working and try to get the audio going.
It's ******* frustrating. I will figure this out though.

I feel you konspiracy! I have been making a few edits here and there and then build for 3 1/2 hours to have a non-working ROM. Don't give up brother we can do it! :cool:
 
I feel you konspiracy! I have been making a few edits here and there and then build for 3 1/2 hours to have a non-working ROM. Don't give up brother we can do it! :cool:

Well, I would have to say that is how dev work generally is. :p

I am really glad all you guys are working hard on it. Once you reach a certain point it should get easier. :)

Keep up the good/hard work guys.
 
agentc13, can we sticky this thread? It has been valuable to alot of us trying to help/build and to get this going.

It's pretty active and you all know where it is. I agree that it is valuable and useful, but don't think it needs stickied.

When there is a releasable ROM and accompanying thread, I am sure that will be stickied for a little while at least. Only because I know most members will want to have it there. I really try to keep ROM threads not stickied as I cannot sticky them all, and it isn't fair to the ones that don't get a sticky.

We are trying to not have that many sticky posts cluttering up the top of the forums and active/important threads will be near the top anyway. I will make sure it is added to the Root guide as I don't think it has been yet. That seems to be an appropriate place for now.

I hope you guys understand my reasoning. If you want to discuss it further feel free to shoot me a PM as I don't want to clutter up this thread with non dev stuff. :eek:
 
Im talking to edowar right now.

I kept getting errors with the networking modules not being there so i gave up.
But i need to get his commits that make hardware accel working and try to get the audio going.
It's ******* frustrating. I will figure this out though.

What errors? Are they "No rule to make target ... " with some mixed case .o files? If someone is running into this building edowar's kernel, I had to change the capitalized version of the filename in the relevant Makefile to lowercase in order to get it to build. Also, curious what toolchain folks are using to build the kernel? I'm currently using the one in the android sources - prebuilt/linux-x86/toolchain/arm-eabi-4.4.3
 
It's pretty active and you all know where it is. I agree that it is valuable and useful, but don't think it needs stickied.

When there is a releasable ROM and accompanying thread, I am sure that will be stickied for a little while at least. Only because I know most members will want to have it there. I really try to keep ROM threads not stickied as I cannot sticky them all, and it isn't fair to the ones that don't get a sticky.

We are trying to not have that many sticky posts cluttering up the top of the forums and active/important threads will be near the top anyway. I will make sure it is added to the Root guide as I don't think it has been yet. That seems to be an appropriate place for now.

I hope you guys understand my reasoning. If you want to discuss it further feel free to shoot me a PM as I don't want to clutter up this thread with non dev stuff. :eek:

I can certainly understand not wanting to clutter things up. Especially here, where there is more concentrated info on the Triumph than I have found anywhere else.
 
What errors? Are they "No rule to make target ... " with some mixed case .o files? If someone is running into this building edowar's kernel, I had to change the capitalized version of the filename in the relevant Makefile to lowercase in order to get it to build. Also, curious what toolchain folks are using to build the kernel? I'm currently using the one in the android sources - prebuilt/linux-x86/toolchain/arm-eabi-4.4.3

yumbrad,

I have not compiled the KERNEL yet. I downloaded the original KERNEL files and tried to build with no luck. Do you have a working KERNEL yet? As far as I know marc is the only one that has a working KERNEL http://androidforums.com/triumph-al...-ics-source-isaacs-github-10.html#post3798753
 
To save any new devs the hassle of flashing back to Froyo ROM just to pick up the proprietary blobs. You can grab them here and just untar them into /vendor/motorola/triumph/proprietary, then run the extract-files.sh as usual (it'll just error on the adb pull part).

http://androidforums.com/triumph-al...7-source-development-area-11.html#post3634312


This same post claims to have the propitiatory blobs to build ICS. Are these confirmed to work with manteras ics source?
 
This same post claims to have the propitiatory blobs to build ICS. Are these confirmed to work with manteras ics source?

I was asked by another member to add them to my post. I would assume that they would work, but I don't have time to work on building ICS right now so you will have to test that yourself. They worked when building from Isaacs source.
 
yumbrad,

I have not compiled the KERNEL yet. I downloaded the original KERNEL files and tried to build with no luck. Do you have a working KERNEL yet? As far as I know marc is the only one that has a working KERNEL http://androidforums.com/triumph-al...-ics-source-isaacs-github-10.html#post3798753

No, I'm currently building my attempt at merging Isaac's android/system with the latest from CM. Has anyone tried the binary kernel included in edowar's kernel repo? I built from source, but it may simply match the binary kernel in the repo as I only changed the filenames I mentioned to get it to build. As soon as my android/system finishes I'll try with both kernels.
 
Grabbed the quote sorry about that :)

Ehh its fine. I just don't want people giving me credit for something I didn't do...

And in other news, edowar is getting more and more ahead of us... If only we could get the touchscreen working on his build... although I tried his newest build and it would get random errors while booting and stop, it took me like 5 battery pulls just to get to the lockscreen... And mantera's kernel still acts like a pointer on that build...
 
No, I'm currently building my attempt at merging Isaac's android/system with the latest from CM. Has anyone tried the binary kernel included in edowar's kernel repo? I built from source, but it may simply match the binary kernel in the repo as I only changed the filenames I mentioned to get it to build. As soon as my android/system finishes I'll try with both kernels.

I was able to build a .zip from CM9 source listed in my install instructions

http://androidforums.com/triumph-al...uide-setting-up-your-android-environment.html

and used Issac's Device file which I highly edited to work in CM9.

https://github.com/ikarosdev/android_device_motorola_triumph

The .zip installed booted and turned off. Right now at home I have the same build running but I replaced the kernel and recovery_kernel from edowar's repo. I will post when I get home on the out come.
 
guys over at "XDA Land" the ideos x6 moved to alpha state... can you merge some changes from his source to yours? then build to get more things working?

also, if we were to swap the kernel and touchscreen files out of "user/idc" would this boot? or just be a waste of time? :confused:

Alpha1 AOSP ICS Rom for Huawei x6 and other FB0 devices - xda-developers

I can try... But the thing is it seems really unstable, it took me like 5 battery pulls to get past the boot animation, and thats when it wants to get past it... I'll let you know how it goes in a bit...
 
Back
Top Bottom