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

Root Build CyanogenMod7 from source | Development area

Deleted the folder as you said, repo synced, and then re-extracted the files. Rebuilt.

The Portable Hotspot works great! (at least in my very limited test in tethering my Xoom to my phone.)

So it works?! Well, hot damn. That's good to hear. :)
 
Here's your build Isaac:

MEGAUPLOAD - The leading online storage and file delivery service

md5:
7a172255088c5a81d7ea336b82d2c130

Edit: One more thing, if you don't mind. change the gEnableSuspend=2 to 3 in the qcom_cfg.ini file in your source... My hotspot connection kept getting knocked off until i realized that it was disconnecting when the screen went to sleep, then I noticed that the gEnableSuspend was still set to 2 in the build.
 
Here's your build Isaac:

MEGAUPLOAD - The leading online storage and file delivery service

md5:
7a172255088c5a81d7ea336b82d2c130

Edit: One more thing, if you don't mind. change the gEnableSuspend=2 to 3 in the qcom_cfg.ini file in your source... My hotspot connection kept getting knocked off until i realized that it was disconnecting when the screen went to sleep, then I noticed that the gEnableSuspend was still set to 2 in the build.

does that build have the new mms.apk in it? (with signature feature)

EDIT: also, does anyone know why the volume is so low when listening to music on cm7 or miui? i know this bug has been around for a while, im just wondering if you guys know what is is... or where it is in the code.
 
Here's your build Isaac:

MEGAUPLOAD - The leading online storage and file delivery service

md5:
7a172255088c5a81d7ea336b82d2c130

Edit: One more thing, if you don't mind. change the gEnableSuspend=2 to 3 in the qcom_cfg.ini file in your source... My hotspot connection kept getting knocked off until i realized that it was disconnecting when the screen went to sleep, then I noticed that the gEnableSuspend was still set to 2 in the build.

Much appreciated, man. I'll try pulling the source again and see if I can't build. That's odd about the option in qcom_cfg.ini... I swore I reverted that back. Either way, it's been fixed: https://github.com/ikarosdev/androi...mmit/9e29301c45a55a875978dbb99c3aae7daae7706d
 
im curious why some of the proprietary files are missing from the miui build im running?? would they be in cyanogen? or only stock for some reason?? i only ask because i accidentally removed my stock backup

EDIT: nm i found a stock backup i have no choice but to restore it just for the files..
 
I finally got the proprietary files last night after flashing stock..it took FOREVER but I finally got it built with a working booting zip file..thanks all...now time to go poke around in the tree :)
 
A word to all builders, my manifest is being bumped up to ICS. This may or may not cause breakages when trying to build CM7 (it shouldn't). Should it cause problems, you know the reason why.
 
@mantera:

I've added more experimental HDMI support to CM7. You can try it out if you're curious. I haven't pulled the source, yet, so you'll have to let me know if it works.

You'll need the gingerbread-experimental branch from: android_hardware_msm7k, android_frameworks_base AND android_device_motorola_triumph (yup, even the device config repo has an experimental branch ;) )

Just pull the experimental branches from each of the three repos, add them to the regular CM7 source tree (in their respective locations) and build. Hopefully, it works!
 
hey issac im building on an old dell dimension 3000 (you probably know how bad they are right) my processor probably wont make it past a second build lol :D

i have a better computer that i could build on but i want to watch my crappy pc melt down :p
 
hey issac im building on an old dell dimension 3000 (you probably know how bad they are right) my processor probably wont make it past a second build lol :D

i have a better computer that i could build on but i want to watch my crappy pc melt down :p

Well, just don't burn down your house... ;)

You should be able to build, but I think that would take hours... Probably 6+ hours.
 
For an older computer, I suggest using using a lighter DE (like XFCE). For normal computer usage, I usually use either Unity, gnome-shell, or KDE, but when it comes to development, I sacrifice looks for performance:

6415929337_29fda70a4c_z.jpg


Bigger version: http://farm7.staticflickr.com/6240/6415929337_29fda70a4c_b.jpg

I'll admit, I'm a sucker for the OSX-like workspace. Normally, XFCE doesn't look like this, but I set it up this way to match my workflow preference. In any case, XFCE is pretty lightweight and fast.
 
Well, just don't burn down your house... ;)

You should be able to build, but I think that would take hours... Probably 6+ hours.

yea i built cm7 once and it took 6-7 hrs... lol

p.s- just moved a fire extinguisher to my room that holds the computer from the stone age :D
 
@mantera:

I've added more experimental HDMI support to CM7. You can try it out if you're curious. I haven't pulled the source, yet, so you'll have to let me know if it works.

You'll need the gingerbread-experimental branch from: android_hardware_msm7k, android_frameworks_base AND android_device_motorola_triumph (yup, even the device config repo has an experimental branch ;) )

Just pull the experimental branches from each of the three repos, add them to the regular CM7 source tree (in their respective locations) and build. Hopefully, it works!


Sure, I'll give it a whirl.
 
@mantera:

I've added more experimental HDMI support to CM7. You can try it out if you're curious. I haven't pulled the source, yet, so you'll have to let me know if it works.

You'll need the gingerbread-experimental branch from: android_hardware_msm7k, android_frameworks_base AND android_device_motorola_triumph (yup, even the device config repo has an experimental branch ;) )

Just pull the experimental branches from each of the three repos, add them to the regular CM7 source tree (in their respective locations) and build. Hopefully, it works!

Got this and didn't get a chance to look at it any closer:

build/core/base_rules.mk:78: *** Module name: liboverlay
build/core/base_rules.mk:79: *** Makefile location: hardware/msm7k/liboverlay
build/core/base_rules.mk:80: *
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: *
build/core/base_rules.mk:84: * optional, debug, eng, tests, samples
build/core/base_rules.mk:85: *
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag:
build/core/base_rules.mk:89: *
build/core/base_rules.mk:90: * Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: * Android.mk for the affected module, and add
build/core/base_rules.mk:92: * the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: * into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: * makefile(s) where it's necessary, if
build/core/base_rules.mk:95: * appropriate.
build/core/base_rules.mk:96: *
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: *
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.
 
Got this and didn't get a chance to look at it any closer:

build/core/base_rules.mk:78: *** Module name: liboverlay
build/core/base_rules.mk:79: *** Makefile location: hardware/msm7k/liboverlay
build/core/base_rules.mk:80: *
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: *
build/core/base_rules.mk:84: * optional, debug, eng, tests, samples
build/core/base_rules.mk:85: *
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag:
build/core/base_rules.mk:89: *
build/core/base_rules.mk:90: * Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: * Android.mk for the affected module, and add
build/core/base_rules.mk:92: * the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: * into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: * makefile(s) where it's necessary, if
build/core/base_rules.mk:95: * appropriate.
build/core/base_rules.mk:96: *
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: *
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.

I pushed a fix. Either download this file: https://github.com/ikarosdev/android_hardware_msm7k/commit/cfa74549b32c8b718ce5aea6651cf01c48b0a3ae

or manually add the missing lines to your local copy.
 

Alright, I attempted to address all the build errors from the output. In light of the changes, I have created a new gingerbread-experimental branch for android_hardware_libhardware as well.

These are the commits:

android_hardware_libhardware: https://github.com/ikarosdev/androi...mmit/02b6e9d805125df269f823c32d580902ddba8629

android_hardware_msm7k: https://github.com/ikarosdev/android_hardware_msm7k/commit/6178f74914fa41d24d355a8641efd13d3d16fb19
 
Alright, I attempted to address all the build errors from the output. In light of the changes, I have created a new gingerbread-experimental branch for android_hardware_libhardware as well.

These are the commits:

android_hardware_libhardware: https://github.com/ikarosdev/androi...mmit/02b6e9d805125df269f823c32d580902ddba8629

android_hardware_msm7k: https://github.com/ikarosdev/android_hardware_msm7k/commit/6178f74914fa41d24d355a8641efd13d3d16fb19

I'll give it a whirl.

Edit: Ok so building as is with your updated experimental branches in android_hardware_libhardware, android_hardware_msm7k, android_frameworks_base AND android_device_motorola_triumph. The first attempt, got this:

Code:
Checking build tools versions...
build/core/base_rules.mk:78: *** Module name: gralloc.triumph
build/core/base_rules.mk:79: *** Makefile location: device/motorola/triumph/libgralloc-qsd8k
build/core/base_rules.mk:80: * 
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: * 
build/core/base_rules.mk:84: *     optional, debug, eng, tests, samples
build/core/base_rules.mk:85: * 
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag: 
build/core/base_rules.mk:89: * 
build/core/base_rules.mk:90: *    Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: *    Android.mk for the affected module, and add
build/core/base_rules.mk:92: *    the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: *    into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: *    makefile(s) where it's necessary, if
build/core/base_rules.mk:95: *    appropriate.
build/core/base_rules.mk:96: * 
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: * 
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules.  Stop.

I then added the missing LOCAL_MODULE_TAGS := optional to Android.mk in device/motorola/triumph/libgralloc-qsd8k.

The 2nd attempt after adding the line got this:

[C++] host C: libpng <= external/libpng/pnggccrd.c host C: libpng <= external/libpng/ - Pastebin.com
 
Back
Top Bottom