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

Root [DEV] Building Code Aurora JB Source for the Triumph

B

BSydz

Android Expert
What's up guys?

So, I'm trying to see what I can do with M7630AABBQMLZA40701000, the Code Aurora JB code for msm7630_surf. I was trying to pull the JB kernel for 7630 from codeaurora and ended up getting the whole JB repo, so I figured I would give it a go. Once I got it to build, my first attempt just sat at a backlit black screen after the Moto logo, but hey it's a start. Now, I have most of our kernel config integrated and alot of the board info in also. Everything is building fine, after a few days of fighting code. :confused: But, I can't seem to find how to make it create a zip file. I have the edify script in the folder but it is still just putting out the .img files. Just figured I would ask, I am still able to make the zips manually but that is a pain. It also takes forever and a day to build, well over an hour when CM9 builds in about 35 minutes or so on my computer. Any suggestions would definitely be appreciated.
 
When I got it to work way back when I had to take our recovery scripts and replace with the stock ones and make edits based on it. Not all the calls work the same like CM7/CM9 so there is a lot of changes the CM team made to make the code compile easier. Also the reason it takes longer is the code aurora compiles all the libs there is no reason to copy over our libs when it's all built from source. However it needs to work properly for the phone. This is a big project to take on man. If you need anything please post in here and I will try and help as much as I can!
 
Well I can pull a logcat with the CM10 kernel, so it is booting. Seems to be egl and surfaceflinger related as far as the blank screen. I'm gonna see what some of the files from CM10 will do. Maybe we can use some code to get other things working. Building the libs is kinda why it got me interested, like seeing what would work and not work. Wish me luck.
 
BSydz said:
Well I can pull a logcat with the CM10 kernel, so it is booting. Seems to be egl and surfaceflinger related as far as the blank screen. I'm gonna see what some of the files from CM10 will do. Maybe we can use some code to get other things working. Building the libs is kinda why it got me interested, like seeing what would work and not work. Wish me luck.
Click to expand...

The fact you got it to at least boot is amazing! I would check with Chairshot on the video stuff as he did some hacks on cm7 and was getting into building some of the video files from source.
 
BSydz said:
Well I can pull a logcat with the CM10 kernel, so it is booting. Seems to be egl and surfaceflinger related as far as the blank screen. I'm gonna see what some of the files from CM10 will do. Maybe we can use some code to get other things working. Building the libs is kinda why it got me interested, like seeing what would work and not work. Wish me luck.
Click to expand...

Good job getting it to boot!
 
jamesd1085 said:
So what would the finished product of this project be?...like stock jelly bean?
Click to expand...


Yes, basically stock Jellybean, I figure there may be some resources, that we may be able to use with other ICS and JB ROMs. Just trying to think outside the box. My goal is to not include any prebuilt files, I have not so far, also to integrate any fixes I find into CM9 and CM10.
 
BSydz said:
Yes, basically stock Jellybean, I figure there may be some resources, that we may be able to use with other ICS and JB ROMs. Just trying to think outside the box. My goal is to not include any prebuilt files, I have not so far, also to integrate any fixes I find into CM9 and CM10.
Click to expand...

Awesome idea...cool to hear you have already got it booting
 
g60madman said:
The fact you got it to at least boot is amazing! I would check with Chairshot on the video stuff as he did some hacks on cm7 and was getting into building some of the video files from source.
Click to expand...


I would love to help but judging on what you have accomplished already I
 
Wow man so you are building the whole rom from caf sources? That is awesome! This could help with all kinds of libraries and binaries in jb and ics!!

Is it building the jb kernel too??
 
b_randon14 said:
Wow man so you are building the whole rom from caf sources? That is awesome! This could help with all kinds of libraries and binaries in jb and ics!!

Is it building the jb kernel too??
Click to expand...
Hopefully it will help, I have only added things to the board config and kernel defconfig. The kernel builds with most of the stuff added, I even worked in most of the board_msm7x30 but the 3.4.0 kernel that came with it got rid of ioctl so the touchscreen drivers (bi041p_ts.c and bu21018mwv.c) give errors. I can't seem to figure that one out yet, they will have to be rewritten. I haven't gotten a chance to look through the whole code yet, I was just trying to get it to build then after I got that figured out, I added some things to the build and worked out the errors. I think I can just put the kernel source from mantera or G60 in there and work out a few things, cause with the caf source it looks in the kernel for headers and stuff to build from, I believe. It's not booting with the 3.4 kernel just the cm10 kernel, even though it looks the same, backlit blank screen. :D The logcat was streaming so fast, and was on windows, that I didn't catch it all, just the last bit of the egl debug and the surfaceflinger errors.

Just figured out what all the sourceforge Triumph source code packages were for and built a froyo from source this morning. It all looked like stock code until I compared it with android-2.2.2_r1 and saw the FIH tags scattered about. Still didn't build a complete system but I just used the generic build to see what would happen. After reading a few of the build notes, it said some devs would work in the regular code and some would want to create separate device files, so it got me thinking. And after pulling the source and comparing, it all made sense. I've never looked at froyo code so it is kinda different. Any way I'll keep you guys posted when I find stuff.
 
BSydz said:
Hopefully it will help, I have only added things to the board config and kernel defconfig. The kernel builds with most of the stuff added, I even worked in most of the board_msm7x30 but the 3.4.0 kernel that came with it got rid of ioctl so the touchscreen drivers (bi041p_ts.c and bu21018mwv.c) give errors. I can't seem to figure that one out yet, they will have to be rewritten. I haven't gotten a chance to look through the whole code yet, I was just trying to get it to build then after I got that figured out, I added some things to the build and worked out the errors. I think I can just put the kernel source from mantera or G60 in there and work out a few things, cause with the caf source it looks in the kernel for headers and stuff to build from, I believe. It's not booting with the 3.4 kernel just the cm10 kernel, even though it looks the same, backlit blank screen. :D The logcat was streaming so fast, and was on windows, that I didn't catch it all, just the last bit of the egl debug and the surfaceflinger errors.

Just figured out what all the sourceforge Triumph source code packages were for and built a froyo from source this morning. It all looked like stock code until I compared it with android-2.2.2_r1 and saw the FIH tags scattered about. Still didn't build a complete system but I just used the generic build to see what would happen. After reading a few of the build notes, it said some devs would work in the regular code and some would want to create separate device files, so it got me thinking. And after pulling the source and comparing, it all made sense. I've never looked at froyo code so it is kinda different. Any way I'll keep you guys posted when I find stuff.
Click to expand...

Since you clearly have adb working I would recommend running the adb monitor tool.

Right click desktop < Create Launcher < Browse < /adb_location/android-sdk-linux/tools/monitor

This will run the gui version of adb and also color coates it very nicely and has a ton of other features like directory browse, screen shots ect.

More info from google's site
Device Monitor | Android Developers
 
BSydz,

dzo has built the code for ICS. Here is the repo's he used

https://github.com/dzo

frameworks/base
packages/apps/Settings
hardware/libhardware_legacy
packages/apps/Camera
device/qcom/msm7630_surf
bionic
hardware/qcom/media
hardware/qcom/camera
packages/providers/TelephonyProvider
hardware/msm7k
system/vold
packages/apps/Phone
build
packages/providers/MediaProvider
hardware/ril

So my guess is we would need to setup the same thing. If you like I can setup an new organization for this project and add us all to the github. Let me know?
 
g60madman said:
Since you clearly have adb working I would recommend running the adb monitor tool.

Right click desktop < Create Launcher < Browse < /adb_location/android-sdk-linux/tools/monitor

This will run the gui version of adb and also color coates it very nicely and has a ton of other features like directory browse, screen shots ect.

More info from google's site
Device Monitor | Android Developers
Click to expand...
g60madman said:
BSydz,

dzo has built the code for ICS. Here is the repo's he used

https://github.com/dzo

frameworks/base
packages/apps/Settings
hardware/libhardware_legacy
packages/apps/Camera
device/qcom/msm7630_surf
bionic
hardware/qcom/media
hardware/qcom/camera
packages/providers/TelephonyProvider
hardware/msm7k
system/vold
packages/apps/Phone
build
packages/providers/MediaProvider
hardware/ril

So my guess is we would need to setup the same thing. If you like I can setup an new organization for this project and add us all to the github. Let me know?
Click to expand...
Yeah I saw that, I bookmarked it, and was gonna check it out later. I just wanted to see what I have learned over the past few months or so, and put it to practice. When it duh dunked in windows I about soiled my drawers, and hastily ran adb to see if it would work. In linux I have scrolling set to unlimited, but haven't setup adb permissions yet. I'm trying to learn how to fish, I'm not one to starve. ;) I once caught a catfish with a string and a bent nail. My boss hated me for it cause he had a pole and wouldn't let me use it, then he tried with the pole and snapped it in half. :rofl:

Thanks, when I make some progress, I'll hit you up about a git. For now it is still just a project until the video is working.
 
b_randon14 said:
Any logcats on the camcorder errors chairshot?
Click to expand...


Sorry looks like I hit the wrong button or something as my previous response had been removed by the moderator.

Negative but I am going to rebuild the Rom and record another logcat. There is also a few other methods found that will fix the flicker but they all have some sort of issue with crapy camcorder recording so will post logs for those also. One is an msm7k Rom I had used for a few days with the Andro-id Camera.apk as the camcorder worked perfectly. Not so much on the Camera so was using the Andro-id app for camcorder and CM7 app for camera, lol. Was a little back and have been meaning to give this another try since learning a lil bit more and also making the below changes.

https://github.com/Chairshot215/frameworks/commit/b6503b35d7403c221568bd5290437d007e687014

Found msm7k uses "OMX.qcom.video.decoder " wich does not have the flicker and beautiful video playback on Youtube but camcorder recording is choppy. I have tried using it in place of the "OMX.qcom.7x30.video.decoder" with msm7x30 with the same results. Both of these changes as well as another attempt using some of Dzo's code in the Framework stagefreighthw all seem to have the same issue with the choppy camcorder video that I had using the Code Aurora code for the Omx libs. Definitely a whole lot going on I don't understand at this point.

Putting thoughts into written word is not one of my strong suits. [FONT=&quot]Especially when I half understand myself[/FONT] so sorry if some of the above is a little confusing. [FONT=&quot][/FONT] I think sometimes G60 thinks I&#8217;m completely insane until I get a chance to better explain what I&#8217;m doing over the phone, lol.


BSydz said:
First, if you could do a lil write up on how to build the libs that would be awesome. If my memory serves me, you make cheat sheets when you do something. So if you have one sitting on your computer, it would be sweet if you could post it. I don't really need a whole write up, and I assume, nor would anybody who is going this route. Just some basic commands or links to stuff.
Click to expand...

Sorry no guide or notes on building the libs but am going to rebuild the Rom as mentioned above and will take notes this time around. For the most part what I had done was download the files from Code Aurora, replaced all the files in hardware/qcomm/media and then removed the lines in the Vendor.blobs.mk that copy in the prebuilt libs. Remember there being a few build errors that for the most part had been pretty easy to figure out from the actual error. Downloaded all the files individually and sure there is a much better way but honestly not sure how
 
Hey to get it to build a zip its in the ota python files in the releassetools directory in the device repo I believe!
 
You must log in or register to reply here.
Back
Top Bottom