01-16-2013 11:07 PM
1,060 ... 89101112 ...
tools
  1. JerryScript's Avatar
    I'm betting it's the omap libraries. I just got finished building after syncing with IHO+CM, and the build would error out with undefined omap classes. I did a quick google search, and found this post in an asian language:
    Richard's Blog - ITeye
    It shows you need to add the following line to /build/core/pathmap.mk
    Code:
    project build/
    diff --git a/core/pathmap.mk b/core/pathmap.mk
    index 6cd3b8f..68e61f9 100644
    --- a/core/pathmap.mk
    +++ b/core/pathmap.mk
    @@ -89,6 +89,7 @@ FRAMEWORKS_BASE_SUBDIRS := \
     	    vpn \
     	    keystore \
     	    voip \
    +	    omapmmlib \
     	 )
    (you add the line that starts with +, removing the + of course )

    This seems to fix the build errors, testing on my phone now.
    BobZhome, mrg666 and jdcnosse like this.
    11-08-2011 11:40 PM
  2. jdcnosse's Avatar
    We can't see your errors, there are up further. Copy and paste the whole log on pastebin.com and post the link here.
    Where is the log file? lol I honestly just copied and pasted from the terminal window...but I will try JerryScript's possible fix to see if that is what it is. If it is, then woohoo! I built my first android system lol
    11-09-2011 12:14 AM
  3. JerryScript's Avatar
    When you build, and there are errors, the error output will have a pointer icon beneath the character that begins the error, example:
    Code:
        int Stuff = "Some text";
                        ^
    This example is showing there is an error begining at the quotation mark (you can't set an integer to a string)

    These errors are sometimes high up in the output, since the build system is sometimes working on multiple packages simultaneously. When your build errors out, scroll up to the first instance of a line such as I've shown above. There you will find the clues as to what the problem is.
    11-09-2011 12:32 AM
  4. pbailey212's Avatar
    Its not necessarily building an android system, blarf did that for us. You are just compiling from his source. There is still a sense of satisfaction when you finally got your own. Zip file you created
    11-09-2011 12:34 AM
  5. jdcnosse's Avatar
    Its not necessarily building an android system, blarf did that for us. You are just compiling from his source. There is still a sense of satisfaction when you finally got your own. Zip file you created
    Well yes, creating my own zip. I should say that instead, but it's a big step up from just modifying an existing zip
    11-09-2011 01:22 AM
  6. jdcnosse's Avatar
    Okay, just ran it again lol

    Here's the log: first build - Pastebin.com

    However I believe it is the omap library's JerryScript is talking about, as after scrolling through all that, I found two error references to omap library.

    the first and second
    Code:
    frameworks/base/core/java/android/widget/VideoView.java:46: package com.ti.omap.omap_mm_library does not exist
    import com.ti.omap.omap_mm_library.OmapMMLibrary;
                                      ^
    frameworks/base/core/java/android/widget/VideoView.java:62: cannot find symbol
    symbol  : class OmapMMLibrary
    location: class android.widget.VideoView
        private OmapMMLibrary mOmapMMHandle = null;
                ^
    third error
    Code:
    frameworks/base/core/java/android/widget/VideoView.java:196: cannot find symbol
    symbol  : class OmapMMLibrary
    location: class android.widget.VideoView
                mOmapMMHandle = new OmapMMLibrary();
                                    ^
    I'll try that fix now and see if it works then

    EDIT: Yep that fixed it. It went through and compiled everything then made my zip, I flashed it to my phone and it worked! Obviously it's got some unnecessary stuff on it since it's pure IHO/CM7.1 but now is the time to tinker with it and start adding and deleting stuff
    11-09-2011 04:17 AM
  7. JerryScript's Avatar
    Glad you got it working! Welcome to the addiction!
    11-09-2011 06:03 AM
  8. jdcnosse's Avatar
    Glad you got it working! Welcome to the addiction!
    More like obsession haha

    Reminds me of this animated gif my programming professor put up on the first day of class. It depicts a stick figure sitting at a computer typing away, and then his keystrokes become furious and he smashes his hands on the keyboard and then his hands start to disappear (it was kinda graphic for a stick figure lol)
    11-09-2011 05:45 PM
  9. thekraven's Avatar
    I'm betting it's the omap libraries. I just got finished building after syncing with IHO+CM, and the build would error out with undefined omap classes. I did a quick google search, and found this post in an asian language:
    Richard's Blog - ITeye
    It shows you need to add the following line to /build/core/pathmap.mk
    Code:
    project build/
    diff --git a/core/pathmap.mk b/core/pathmap.mk
    index 6cd3b8f..68e61f9 100644
    --- a/core/pathmap.mk
    +++ b/core/pathmap.mk
    @@ -89,6 +89,7 @@ FRAMEWORKS_BASE_SUBDIRS := \
             vpn \
             keystore \
             voip \
    +        omapmmlib \
          )
    (you add the line that starts with +, removing the + of course )

    This seems to fix the build errors, testing on my phone now.
    Does this fix allow this surfaceflinger commit or do we still need to revert? https://github.com/CyanogenMod/andro...comment-698298
    11-11-2011 02:04 PM
  10. mrg666's Avatar
    Does this fix allow this surfaceflinger commit or do we still need to revert? https://github.com/CyanogenMod/andro...comment-698298
    I still had to revert that surfaceflinger commit.
    thekraven likes this.
    11-11-2011 02:58 PM
  11. OptimusNate's Avatar
    Jerry, thanks for the wonderful writeup! Not sure if if the instructions need updating, but after trying many times to get the repo working from the link you posted and nothing happening, I downloaded repo from http://git-repo.googlecode.com/files/repo-1.13 and now I can sync.

    Can't wait to see if it builds after the sync
    JerryScript likes this.
    11-12-2011 02:06 AM
  12. mrg666's Avatar
    Just a heads up: CM repo just switched to 7.2-RC0.

    There are so many commits in just one night. Among them, the following commits sound very promising to resolve the sound problem in movie recording possibly due to a race condition. Check them out. I will be testing them.

    Call stopRecording first then start beepSignal
    Camera: Initialize the camera shutter sounds asynchronously.
    framework/base: Fix for Camera shutter sound heard twice
    bigsupersquid and JerryScript like this.
    11-14-2011 08:36 AM
  13. BobZhome's Avatar
    To fix the sound problem in movie recording was a permission issue, grab this file to fix it: https://github.com/BobZhome/android_...td.thunderc.rc
    Also, you can grab the new kernel here: Kernel_v3.3.zip
    And to added custom carrier label to your builds, grab these two cherry-picks:
    Code:
    git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git cherry-pick FETCH_HEAD
    git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts refs/changes/13/7313/3 && git cherry-pick FETCH_HEAD
    11-14-2011 02:53 PM
  14. mrg666's Avatar
    To fix the sound problem in movie recording was a permission issue, grab this file to fix it: https://github.com/BobZhome/android_...td.thunderc.rc
    Are you referring to this problem? A wrong file permission would consistently, always disable the sound. But this problem happens inconsistently and triggered by another reason IMHO. Thanks, I will check anyway.

    By the way, could you please briefly tell what is different in v3.3 kernel?
    11-14-2011 03:19 PM
  15. JerryScript's Avatar
    ICS source is up, but the servers are swamped atm:
    Android 4.0 Ice Cream Sandwich source posted by Google - SlashGear
    11-14-2011 05:37 PM
  16. BobZhome's Avatar
    Yes, it fix's issue #54
    Your using 3.1, 3.2 was the failed headset try, and 3.3 has Drew's axis-inversion(a multi touch tweak). It's a very small improvement...I didn't notice much of a change.
    JerryScript and mrg666 like this.
    11-14-2011 05:38 PM
  17. jdcnosse's Avatar
    And to added custom carrier label to your builds, grab these two cherry-picks:
    Code:
    git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git cherry-pick FETCH_HEAD
    git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts refs/changes/13/7313/3 && git cherry-pick FETCH_HEAD
    I can't seem to "fetch" these files.

    I get this error:

    Code:
    From http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts
     * branch            refs/changes/13/7313/3 -> FETCH_HEAD
    fatal: You do not have a valid HEAD
    11-16-2011 12:56 AM
  18. mrg666's Avatar
    Yes, it fix's issue #54
    Your using 3.1, 3.2 was the failed headset try, and 3.3 has Drew's axis-inversion(a multi touch tweak). It's a very small improvement...I didn't notice much of a change.
    I have built IHO after syncing with the huge number of changes in the CM repo that came with 7.2.0-RC0. Camera app started crashing/ freezing and complaining that it cannot connect to hardware afterwards. I have deleted the camera app from my copy of CM repo and switched the camera in BobZhome repo. It now works with all the changes in the CM repo (thank you Bob, thank you). There are no other problems to report, everything seems to be in order. Additionally, I can confirm that issue #54 is fixed now in this latest build. I have merged the file permission changes Bob very kindly gave to us. Just FYI.

    However, I will not upload this build to Wiki but just post an announcement in the IHO thread for the users who want to test these large number of changes while I also test for another couple of days.
    JerryScript likes this.
    11-16-2011 08:53 AM
  19. thekraven's Avatar
    These two commits broke the CM7 video camera, so revert if you want a working video cam. But BobZhome's camera is still the better choice.

    https://github.com/CyanogenMod/andro...0f201d293cbc8a

    https://github.com/CyanogenMod/andro...6d291a9daaa4c2
    JerryScript, mrg666 and BobZhome like this.
    11-16-2011 11:32 PM
  20. mrg666's Avatar
    These two commits broke the CM7 video camera, so revert if you want a working video cam. But BobZhome's camera is still the better choice.

    https://github.com/CyanogenMod/andro...0f201d293cbc8a

    https://github.com/CyanogenMod/andro...6d291a9daaa4c2
    I agree, I will stay on Bob's Camera source. I hope that is okay with you, Bob. Thanks to both of you.

    Did you see Koush's response to Jerry on Github for the error report?
    JerryScript and bigsupersquid like this.
    11-17-2011 08:19 AM
  21. JerryScript's Avatar
    Koush is a ******. There, I've said it. He didn't respond to request to have a bad manifest removed from his ROM Manager which resulted in the soft-bricking of hundreds of OVs (I wonder how many were returned for warranty?), even though many of us PAID for ROM Manager. And now he once again snubs his nose at us. I wish I could take back every cent I paid him, and remove every post I ever made recommending people donate to him for the recovery.

    I don't pay to be b@#$% slapped!
    11-17-2011 08:31 AM
  22. bigsupersquid's Avatar
    wow, that was some petty commenting on github.
    sorry, jerry and mrg.
    if those guys wanted to complain, they should have asked for more specific data about the breakage, rather than griping about blarf not jumping through their hoops to be allowed to contribute code. they've already made it clear they weren't interested in adding support for these phones.
    I wasn't going to say anything, but after reading those commit comments...
    11-17-2011 08:49 AM
  23. mrg666's Avatar
    wow, that was some petty commenting on github.
    sorry, jerry and mrg.
    if those guys wanted to complain, they should have asked for more specific data about the breakage, rather than griping about blarf not jumping through their hoops to be allowed to contribute code. they've already made it clear they weren't interested in adding support for these phones.
    I wasn't going to say anything, but after reading those commit comments...
    The response was defensive and immature. But, let's be fair with one thing. CM is a large and complex project. There will be some conditions (hoops) to be met in order to integrate another device. But, I think IHO is fine outside the CM. I know saying this is a little selfish since I build my ROM when I want. It could be easier for the users to download nightly builds. However, I am still building my ROM for the Nook Color although nightlies are available for it since my own build performs better, all the clutter cleaned up, and some persistent bugs are fixed.
    11-17-2011 09:16 AM
  24. JerryScript's Avatar
    I emailed defer, explained our frustrations, and he has offered suggestions towards inclusion into CM. I think there should be some discussion here about how everyone feels about taking this step. Someone would probably have to accept the responsibility of maintaining the thunderc branch.

    The one time I mentioned it to Blarf, he was non-commital about it. Seems there would be some major changes to the way Blarf set up IHO before it can be accepted by CM.

    I'm for attempting to get included before the CM9 release, if that's possible.
    Whyzor and mrg666 like this.
    11-17-2011 12:41 PM
  25. Whyzor's Avatar
    Ah, I see this all too often where I work. Processes are created (some reasonable, others too much work), people don't follow them, disputes happen. Not saying anyone's at fault, the comments started out pretty innocent. Hopefully whoever creates the ICS branch will add it to the main CM tree, if not for the simple reason that CM commits that break our phones will get more visibility.
    11-17-2011 12:48 PM
1,060 ... 89101112 ...
LINK TO POST COPIED TO CLIPBOARD