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

ziggy46 said:
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
Click to expand...

I had tired replacing the touchscreeen files in user/idc but it was still the same but I only did one file and I didn't replace the kernel. The toucscreen was still not working. :(
 
ziggy46 said:
what happens when you replace the kernel too? :confused:
Click to expand...

I'm booting into it now... I'll let you know in a bit...

Edit: still acts like a pointer even with the idc files replaced :/ A very non functional pointer too :/

Edit: it wouldn't be too bad except for the fact that the pointer always returns to the middle of the screen when you release your finger meaning you can only click on stuff in the middle of the screen...
 
oldmanstatic said:
No I didn't replace because I don't know how to. I just replaced their bu21012mwv-ics.idc with our bi041p.idc from ICS.
Click to expand...

To replace the kernel all you have to do is take the boot.img from mantera's build and replace the boot.img in edowars build... All it does is make it act like a pointer though... you can't do much...

Edit: Hah I got into the settings! :D something I learned from when I had to get into the settings on the g1, since I had to use my friends deactivated sim card... Anyways get into adb make sure your connected, then adb shell, once there copy and paste this:
Code: 
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
into the shell and it will open settings!
 
Still can't get CM7 to build even using manteras git... Maybe I should just move onto ICS since thats what everyone is on currently anyway?
 
BadAngel said:
Okay I'm in. If you guys could just give me a quick rundown of what the latest is, and where I should be grabbing my code from, I'll get cracking today.
Click to expand...

The problem is there is no code. No one except mantera has a booting device but he has not put all his code up on github yet. We are still in a "work in progress" at this point. If I have something working tonight when I get home I will gladly upload but right now as it stands it's you need to pave the path or wait for mantera.
 
g60madman said:
The problem is there is no code. No one except mantera has a booting device but he has not put all his code up on github yet. We are still in a "work in progress" at this point. If I have something working tonight when I get home I will gladly upload but right now as it stands it's you need to pave the path or wait for mantera.
Click to expand...

Well there's no way I'm going to catch up to mantera by the time he pushes everything tonight or tomorrow, so I guess I'll wait and then pull his stuff and work from there.
 
BadAngel said:
Still can't get CM7 to build even using manteras git... Maybe I should just move onto ICS since thats what everyone is on currently anyway?
Click to expand...

I used Issac's to do the initial pulls, then I used mantera's to move up to the most up-to-date setup. Build finished successfully, flashed into my phone and currently using (as of this afternoon).

ICS, on the other hand will have to wait for tomorrow. The build will probably take all day for me to complete/compile on my desktop. I will do my best to get a successful run and build and let you guys know where I get with it. I will post up if I have any issues.
 
Built another ICS zip however same problem doesn't boot. It hits the Motorola logo and then turns off. Using edowar's KERNEL did not help. Like others I think it's time to wait for mantera as he does have a working build and then we can all work together to get it working. Of course that's not going to stop me from trying one more build tonight :cool:
 
g60madman said:
Built another ICS zip however same problem doesn't boot. It hits the Motorola logo and then turns off. Using edowar's KERNEL did not help. Like others I think it's time to wait for mantera as he does have a working build and then we can all work together to get it working. Of course that's not going to stop me from trying one more build tonight :cool:
Click to expand...

Sounds perfect... I only wish there was something like github that we could all share and document changes that we make. Oh well.
 
\My question is Im in contact with edowar and it seems we are taking things from a compiled zip and just altering the boot image to get it to boot. I want to know if we have anybody that has a build environment that has compiled and booted. because all Edowar has given me is some INIT.rc files to change out


So if yall are hoping for a dev that has some answers well you better keep looking.

Like I said before, anybody can setup a build environment its the ones who can get it to boot from that environment that are the man.
 
konspiracy said:
Like I said before, anybody can setup a build environment its the ones who can get it to boot from that environment that are the man.
Click to expand...

I think right now mantera is the only man standing. I have got the system to build using CM9 using Issac's device code and made some major changes so it would complie. What would be interesting if I copied over Edowar's INIT.rc into the zip I made to see if it boots. I might be able to at least pin point whats going on with the fail I am having.
 
mantera said:
I pushed up what I got for device files and started a new thread to keep everything more easily managed.
Click to expand...

I'm currently pulling down your repo now. Seems to be working fine. Hopefully (fingers crossed) I can get a build and see if it runs. I have been able to follow a tree of sorts to decifer where things should go, esentially how the code works/flows. Maybe I can figure out a few things and finally help you guys out.

BTW, special thanks to mantera, Whyzor, and others that have help me immensely over the past few weeks to get other things going. I really appreciate it.
 
Chingling said:
Got it! Thanks to Google my hero, I found a solution to the signapk.jar error. For those of you that are getting this error, locate ~/android/system/build/tools/releasetools/common.py Find this line:
Code: 
cmd = ["java", "-Xmx2048m", "-jar",
           os.path.join(OPTIONS.search_path, "framework", "signapk.jar")]
...and change it to this:
Code: 
cmd = ["java", "-Xmx[B]1024[/B]m", "-jar",
           os.path.join(OPTIONS.search_path, "framework", "signapk.jar")]
If that does not work then you can try changing the number to a lower one. This number defines how much RAM the program uses. It solved my problem and now I have built successfully! :D Will test it out later.
Click to expand...

Tried the above fix because I ran into this again with mantera's current repo --->


Code: 
running:  java -Xmx2048m -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpJ6Q4oK out/target/product/triumph/cm_triumph-ota-eng.heath.zip
Could not create the Java virtual machine.

Thing is, that changing the lines above did nothing to change the execution below. Tried running a search, and a ton of files have the Xmx2048m reference. Anyone have any ideas where this final bit of code is? The build finished, but this can't finalize and create the zip. SO CLOSE!!! If I can get this to finish, I will have my first build, and for me and this little notebook, that would be a great feat.

Edit:

Found it! Has to be changed here, too :

Code: 
/device/motorola/triumph/releasetools/triumph_common.py
 
h.haulman said:
I guess the 3G fix isn't in the git just yet? Sync'd this AM, built, flashed, no data still. Must be jumping the gun.
Click to expand...

No, not yet. I'm verifying it first. I hate to push stuff up that breaks stuff for everyone else. Also I threw in a fix for the browser not working. so we'll see if that helps.
 
mantera said:
No, not yet. I'm verifying it first. I hate to push stuff up that breaks stuff for everyone else. Also I threw in a fix for the browser not working. so we'll see if that helps.
Click to expand...

OK, I just finally got a build going. It may take me 3 days to build, but it is running--really slow. Hopefully, no errorring out.

*edit* Several hours later and still building! Had to restart after manteras push with data enabled and a resync.

*edit 2* spoke too soon @*%$! errored out. Going to resync again and try again. The thing built solid for several hours. I need to build another computer!

Code: 
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:6141: error: 'struct vdec_ioctl_msg' has no member named 'inputparam'
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:6142: error: 'struct vdec_ioctl_msg' has no member named 'outputparam'
make: *** [out/target/product/triumph/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/src/omx_vdec.o] Error 1
 
sharpe351 said:
OK, I just finally got a build going. It may take me 3 days to build, but it is running--really slow. Hopefully, no errorring out.

*edit* Several hours later and still building! Had to restart after manteras push with data enabled and a resync.

*edit 2* spoke too soon @*%$! errored out. Going to resync again and try again. The thing built solid for several hours. I need to build another computer!

Code: 
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:6141: error: 'struct vdec_ioctl_msg' has no member named 'inputparam'
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:6142: error: 'struct vdec_ioctl_msg' has no member named 'outputparam'
make: *** [out/target/product/triumph/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/src/omx_vdec.o] Error 1
Click to expand...

Resync and try again
 
You must log in or register to reply here.
Back
Top Bottom