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

Root [DEV] CM7 Building & Development

dsmryder said:
How is the kernel added to this ROM. I wanted to experiment with some stuff, and I have looked for some of the files that are in the whykernel repo. I suppose it is prebuilt and added as a binary?
Click to expand...

Yes, it's prebuilt and is named kernel in the root of the android_device_motorola_triumph repo.
 
And its just the zimage not the boot.img. I found that out the hard way lol! So you just need the zimage without the ramdisk packed into it as a boot.img lol!!
 
Hi guys I have a few quick questions I was hoping I could get a bit of help with. Actually more than a few but at work and also find I get confused more easily when trying to tackle too many things at once so will go one at a time. Basically trying to consolidate the project I have been working on. Had in the beginning used a bunch of different tools based on what resources had been available for what I wanted to accomplish. I
 
klehman215 said:
Hi guys I have a few quick questions I was hoping I could get a bit of help with. Actually more than a few but at work and also find I get confused more easily when trying to tackle too many things at once so will go one at a time. Basically trying to consolidate the project I have been working on. Had in the beginning used a bunch of different tools based on what resources had been available for what I wanted to accomplish. I
Click to expand...
 
Thanks,

Not sure now if I should be posting on this or the other thread but I am editing the triumph.mk for the apps and am guessing an init.d script would be added under # Init.d task management and placed in device/motorola/triumph/files/etc/init.d along with the 99memory script? Going to also try adding to the build.prop by adding a few lines under # Performance tweaks and misc. Going to assume my assumptions are correct for a minute at least and try a build. Otherwise would be nice to be prepared for unfinished projects. If everything works out will probably return with questions about removing apps and adding an mp3 to system/media.
 
klehman215 said:
Thanks,

Not sure now if I should be posting on this or the other thread but I am editing the triumph.mk for the apps and am guessing an init.d script would be added under # Init.d task management and placed in device/motorola/triumph/files/etc/init.d along with the 99memory script? Going to also try adding to the build.prop by adding a few lines under # Performance tweaks and misc. Going to assume my assumptions are correct for a minute at least and try a build. Otherwise would be nice to be prepared for unfinished projects. If everything works out will probably return with questions about removing apps and adding an mp3 to system/media.
Click to expand...

I can help with the sounds part. As for system sounds, I've tried using .mp3's, but they didn't work. I converted them to .ogg's and moved them to (build directory)/frameworks/base/data/sounds. Then you have to update whatever soundpack that you are using. The base one is AllAudio.mk. It's called by (build directory)/build/target/product/full_base.mk. That's of corse you haven't changed the call for full_base.mk
As for removing apps. That can be tricky, there are a few call through out the build. Like various friends who want to play with with whatever.
 
Thanks, the MP3 is actually for the boot sound. Dosed off last night but woke up without any errors. Going to try and flash after work.
 
Hey g60, did you merge the boot sound parts? If so, I need to tell Mike to add the necessary parts to his FAQ.

Edit: The sound needs to be named android_audio.mp3 and it goes in /system/media
 
dsmryder said:
Hey g60, did you merge the boot sound parts? If so, I need to tell Mike to add the necessary parts to his FAQ.

Edit: The sound needs to be named android_audio.mp3 and it goes in /system/media
Click to expand...

What you talking about Willis? :confused:
 
Also and a huge also, if anyone happens to stumble across a way of setting Sliding Tab as the incoming call lockscreen style please let me know. I have spent a countless amount of hours researching and reading code and have not been able to figure it out. I was able to set Tabs as the non-call default but only because I swapped these lines in the Policy Lockscreen,


else if (mUseRingLockscreen) {
mRingSelector.setVisibility(View.VISIBLE);
mRotarySelector.setVisibility(View.GONE);
mTabSelector.setVisibility(View.GONE);


Changed to,


else if (mUseRingLockscreen) {
mTabSelector.setVisibility(View.VISIBLE);
mRotarySelector.setVisibility(View.GONE);
mRingSelector.setVisibility(View.GONE);


and then set Rings as VISIBLE a few lines down so basically you get Tabs when Rings are selected and Rings if Tabs are selected. I then swapped their position in the CMParts arrays XML and then swapped their text in the Strings XML. Not exactly setting as a default but it worked. For the life of me though I can
 
klehman215 said:
Also and a huge also, if anyone happens to stumble across a way of setting Sliding Tab as the incoming call lockscreen style please let me know. I have spent a countless amount of hours researching and reading code and have not been able to figure it out. I was able to set Tabs as the non-call default but only because I swapped these lines in the Policy Lockscreen,


else if (mUseRingLockscreen) {
mRingSelector.setVisibility(View.VISIBLE);
mRotarySelector.setVisibility(View.GONE);
mTabSelector.setVisibility(View.GONE);


Changed to,


else if (mUseRingLockscreen) {
mTabSelector.setVisibility(View.VISIBLE);
mRotarySelector.setVisibility(View.GONE);
mRingSelector.setVisibility(View.GONE);


and then set Rings as VISIBLE a few lines down so basically you get Tabs when Rings are selected and Rings if Tabs are selected. I then swapped their position in the CMParts arrays XML and then swapped their text in the Strings XML. Not exactly setting as a default but it worked. For the life of me though I can
Click to expand...
 
dsmryder said:
I just set mine to "tab" Um, I am not sure what is going on. You probably already know, but the setting is settings--> cyanogenMod settings--> Lockscreen-->Style Options--> Incoming call style.
I doubt you needed that, but I know I've had moments where I couldn't find something.
Click to expand...


Thanks but what I’m trying to do is set it up so that it’s the default in that it’s the selected style after flashing without needing to manually change any settings. Actually had planned on removing the Style option from the menu after figuring out how to set the incoming call Style. Basically I have been trying to turn CM7 into a clone of the Stock Rom. Also why I asked about the boot sound mp3, think I may have figured that out though and treated it like I did the APK’s in the device tree but gave the path for system/media in the Triumph.mk. Not doing it so much because a Froyo styled CM7 Rom is something I really want but more because I wanted to learn how and it helped in that I could make a list of goals or things that I would need to learn in order to pull it off. I also pick up on things better when working towered an objective rather than just reading general explanations. Had to learn images for one but other things like setting up home screen widgets, disabling or enabling specific live wallpapers, editing settings and menus, boot sound & animation even learned how to add the overscroll glow to a Rom that does not have the feature when researching how to disable the effect. Feels like I have learned a lot in a short time but every time I figure something out on the list I get a nice little confidence boost and feel like I can learn things just a few month ago thought would be well beyond what I could ever do. Anyway I feel the explanation may help in understanding what may seem like odd questions. I’m pretty much towered the end of my list and so far the incoming call lockscreen is the only item I have not been able to accomplish and its bugging me that I skipped ahead as I promised myself I would not give up on anything on the list until I figured it out, as cheesy as that may sound. I am now in the process of consolidating all my changes to build 100% from source because learning how to use get-hub is one of the few items left. Otherwise all my friends are iphone fans and I don’t really have anyone who shares my interest so when given the opportunity I tend to rant, sorry about that.
 
mantera said:
In case you're interested in making your camera DCIM compliant, you can pull in this commit i pushed up to my gb camera repo a while ago:

https://github.com/mantera/android_...mmit/15fd8243c5f14cfed5bf614e0ec2e147844cc1ce
Click to expand...

Sweeeeeet! Thanks mantera, nice find! I will add it into r0.11 once I get there. Right now I am working on revamping the device files for the Triumph, basically it's a merge between htc thunderbolt (same proc, and video), and msm7360_surf device files from MSM/QSD for gingerbread. I am using manifest M7630AABBQMLZA404025I.xml. I have yet to get it to build, but in time :rolleyes: As soon as I have a working product (if I can get it to work) I will post it up on github.

My hopes are to be able to build with the default CM7 source. It would be nice to get to a point to have a nightly build but due to our jacked GPS I think that is a pipe dream. I tried to use the qcom/gps from the main line of CM7 but no love. Right now I am trying to build with the MSM/QSD GPS from Gingerbread. However it's all just trial and error right now.
 
g60madman said:
Sweeeeeet! Thanks mantera, nice find! I will add it into r0.11 once I get there. Right now I am working on revamping the device files for the Triumph, basically it's a merge between htc thunderbolt (same proc, and video), and msm7360_surf device files from MSM/QSD for gingerbread. I am using manifest M7630AABBQMLZA404025I.xml. I have yet to get it to build, but in time :rolleyes: As soon as I have a working product (if I can get it to work) I will post it up on github.

My hopes are to be able to build with the default CM7 source. It would be nice to get to a point to have a nightly build but due to our jacked GPS I think that is a pipe dream. I tried to use the qcom/gps from the main line of CM7 but no love. Right now I am trying to build with the MSM/QSD GPS from Gingerbread. However it's all just trial and error right now.
Click to expand...

Have you seen the thread on AGPS? It points to another ROM that has some broken parts, but the GPS is supposed to be perfect. I think the mms is borked. I don't know how they are building, I think they are rebuilding it from a ROM.
 
dsmryder said:
Have you seen the thread on AGPS? It points to another ROM that has some broken parts, but the GPS is supposed to be perfect. I think the mms is borked. I don't know how they are building, I think they are rebuilding it from a ROM.
Click to expand...

I will take a look at that. Right now I have it building using the stock CM7 code

repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

I only replaced the android_hardware_qcom_gps with ours. After fixing some misspellings and missing one lib file that needed to be copied for GPS the build seems to be building and is in it's final zipping stage. While typing it just finished, going to see if it actually works (crosses fingers)

Edit: FAIL Script aborted (Status 7) .....back to the drawing board :)
 
g60madman said:
I will take a look at that. Right now I have it building using the stock CM7 code

repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

I only replaced the android_hardware_qcom_gps with ours. After fixing some misspellings and missing one lib file that needed to be copied for GPS the build seems to be building and is in it's final zipping stage. While typing it just finished, going to see if it actually works (crosses fingers)

Edit: FAIL Script aborted (Status 7) .....back to the drawing board :)
Click to expand...

Let me take a look a the Script
 
Mobstergunz said:
Let me take a look a the Script
Click to expand...

Don't think it's the script I forgot to load usb

# USB
BOARD_USE_USB_MASS_STORAGE_SWITCH := true
BOARD_UMS_LUNFILE := "/sys/devices/platform/usb_mass_storage/lun0/file"

I will try this new build in a sec, if it doesn't work I will post the script ;)
 
Holly crap I got it to boot just using just the stock CM7 code and simply replaced the GPS files w00t!! However video is lagging extremely bad, Wifi doesn't work, camera doesn't work, phone doesn't work, the proximity sensor is acting up, no videos will play, and no audio. Doesn't sound that bad does it :p
 
g60madman said:
Holly crap I got it to boot just using just the stock CM7 code and simply replaced the GPS files w00t!! However video is lagging extremely bad, Wifi doesn't work, camera doesn't work, phone doesn't work, the proximity sensor is acting up, no videos will play, and no audio. Doesn't sound that bad does it :p
Click to expand...


Lol its a start
 
You must log in or register to reply here.
Back
Top Bottom