01-17-2013 12:07 AM
1,060 ... 1011121314 ...
tools
  1. BobZhome's Avatar
    So I may be behind the times in that I'm just working on compiling regular IHO, but as of the last sync with the IHO repos, I can't seem to compile the zip file anymore.

    I get multiple errors, but I'm working on them one at a time lol so first ones first.

    Code:
    packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:85: cannot find symbol
    symbol  : variable config_enableScreenAnimation
    location: class com.android.internal.R.bool
            if (getResources().getBoolean(com.android.internal.R.bool.config_enableScreenAnimation)) {
    I've tried googling this, and I can't find anything about config_enableScreenAnimation. I've found stuff about internal.R.bool, but everything I've found yields that config_enableScreenAnimation doesn't exist, at least in that package...

    However removing the code that relates to the Electron Beam control (the screen animation when you turn off/on the screen) fixes the error, but that would mean that there'd be no screen animation.
    Jerry is correct...CMParts is up to date and is looking for a symbol that is not in Frameworks/Base, because it is not up to date.
    11-20-2011 08:22 AM
  2. JerryScript's Avatar
    @BobZhome: Something that I'm confused about, hoping you might clear up a question about git?

    I do the following:

    cd frameworks/base
    git remote add upstream git://github.com/CyanogenMod/android_frameworks_base.git
    git pull upstream (should I rebase here?)

    My question is, once blarf does sync up with CM, I always get sync errors using repo sync. I manually fix it by deleting my local copies of the repos in question, then re-syncing. This lack of understanding about git is what has kept me from maintaining my local changes on github.

    Can you offer some steps that would better maintain all necessary commit histories without manually deleting local repos and re-syncing?
    11-20-2011 09:58 AM
  3. BobZhome's Avatar
    When you use pull, Git tries to automatically do your work for you. It is context sensitive, so Git will merge any pulled commits into the branch you are currently working in. One thing to keep in mind is that pull automatically merges the commits without letting you review them first. If you don’t closely manage your branches you may run into frequent conflicts.

    Normally I use: git fetch upstream
    And then I'll use: git merge upstream/gingerbread
    When you fetch, Git gathers any commits from the target branch that do not exist in your current branch and stores them in your local repo. However, it does not merge them with your current branch. This is particularly useful if you need to keep your repo up to date but are working on something that might break if you update your files. To integrate the commits into your master branch, you use merge. This combines the specified branches and prompts you if there are any conflicts.

    Every so often I do need to delete a local branch, that's normal with large updates.
    JerryScript likes this.
    11-20-2011 12:37 PM
  4. jdcnosse's Avatar
    Have you set up your local repo to pull in changes from CM? Blarf hasn't syncd IHO with CM for a couple of weeks, so you'll have to pull in changes yourself in the meantime. Using git pull with the URL to the CM repos in question should grab those changes. If you want to look at them before merging, then use git fetch instead, look at the diff, then rebase/merge as needed.
    Ahh, nope, that would probably fix it but I didn't know how to sync both IHO and CM, in the same folder. Not to mention I'm a git noob so all this repo & git stuff gets to be confusing lol

    Thanks though (I'd click thanks but I'm on my phone so there's no thanks button lol)
    11-20-2011 01:42 PM
  5. asadullah's Avatar
    So I been reading the cdma hero section ics thread on xda and one of the guys said that he synced with the master branch where as i used the "android-4.0.1_r1" branch. Is that why I'm getting errors? What has everyone else synced?
    Here's my setup fresh install ubuntu 11.10 (today) 64bit no other repos or branches (currently repo syncing hoping things change) Should I get the master branch? Is anyone else using ubuntu 11.10? who shot J.R ?

    Okay I just thought about it. I've built gingerbread and froyo from source on 11.04 but if anyone feels different please let me know.
    11-20-2011 02:49 PM
  6. bigsupersquid's Avatar
    I'm using android-4.0.1_r1 branch.
    debian squeeze, gcc 4.4
    I can get a complete compile for generic_armv5 and modded thunderc, but neither one outputs any binaries that will run on my phone (#@#$#&!@#) except for in the ICS ramdisk (init seems to work, parses init.rc and mounts MTD partitions and everything, but then can't run anything from /system according to dmesg.)
    I had the same problem with AOSP GB and CAF GB. Every now and then I get working binaries. I don't know what I'm fouling up. Never had any issues with working binaries on CM7.
    My repo synced night before last was able to build generic_armv5 without errors after patching in lupohirp's libaudio folder and some other fixes I've documented earlier in the thread here.
    But nothing built fresh except for init will run on the phone. After boot or from adb shell in recovery.
    I even tried an otapackage to make sure the permissions were set right in /system, didn't make a bit of difference. Partial boot, kernel works, init works, patched-in adbd and busybox from xionia cwma work, nothing else works.
    &%^$@&^*#!!!!
    11-20-2011 04:42 PM
  7. asadullah's Avatar
    @bigsupersquid LOL I'm glad I'm not the only one having problems here. From what I can tell it's my gcc version which I removed and reinstalled but still got issues have you checked the cdma hero sections they got alot of info (as well as people saying "great job, awesome, i wanna ride that devs *&^# " )


    P.S I know it doesn't got to be said but don't give up till it's done
    11-20-2011 05:25 PM
  8. bigsupersquid's Avatar
    WOOO!
    Dunno exactly what I did, but I have a boot to the android logo and logcat with an incomplete build pushed through adb!
    Of course it doesn't completely boot, since it's not all there yet (the build is only a couple hours in of the 5-9 hrs it takes my machine to make this pile!) but am I tickled pink right now.
    I'm watching like 3 different xda threads on building right now, the hero is one.
    I've picked fixes from all of them, some I'm still using, some I'm trying now, some I've discarded. Currently:
    build directory removed except for .repo, and repo synced again this afternoon.
    Lupohirp's libaudio, andy572's dalvik and armv6k, spl-inl.h and copybit.h from https://github.com/TeamICS/ICS_Fixes
    anything else I've forgotten dunno if the webrtc and armv6k-vfp stuff is working yet except I think it's gotten well past the dalvik.
    also
    export USE_CCACHE=1

    and something about using pipes instead of pages by Shelnutt2:
    export CFLAGS="$CFLAGS -pipe"
    export CXXFLAGS="$CXXFLAGS -pipe"

    also
    make clobber
    between failed build attempts

    right now the thing I've got working is a knock-off of the generic_armv5 I copied in build/target/product and /build/target/board, renamed as generic_armv6, the only change (other than renaming all the generic_armv5 as generic_armv6, filenames and in the files) is in /build/target/board/generic_armv6/BoardConfig.mk (added
    TARGET_ARCH_VARIANT := armv6k-vfp
    where it is
    TARGET_ARCH_VARIANT :=
    in the original)
    and that's the item I'm building right now which seems to be working out.

    choosecombo release generic_armv6 eng
    make PRODUCT-generic_armv6-eng


    edit: oooo, it's into libwebcore and still hasn't crashed yet. if that earlier stuff didn't fix the webrtc, I'll try this:
    https://github.com/mikegapinski/plat...xternal_webrtc

    edit again: webcore and webrtc compiled! build stopped with assembler errors at system/core/debuggerd/vfp.S
    used andy572's suggestion to comment out the crash code (most of that file) and now it's building again.
    asadullah and JerryScript like this.
    11-20-2011 06:44 PM
  9. asadullah's Avatar
    Okay so I'm not where your at yet but now we can collaborate that my machine can successfully compile ( takes about 5hrs where's jerryscript when you need him?) So from what I understand so far is that for some reason 11.10 has an issue with gcc 4.5 and above so you gotta downgrade get gcc 4.4 then replace the gcc in /usr/bin. So what I'm gonna do if I can is sleep and give a write up about it in another post or this one.

    Errors I got
    Code:
    /usr/include/linux/errno.h:4:23: fatal error: asm/errno.h: No such file or directory
    e:unable to locate package cc
    <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by default] <built-in>:0:0: note: this is the location of the previous definition
    Here's my complete terminal history since I reinstalled ubuntu 11.10
    Code:
     1  cd Desktop
        2  sh firstboot
        3  sudo apt-get install lib32readline-gplv2-dev
        4  lsb-release
        5  lsb_release
        6  sh installsdk
        7  sudo add-apt-repository ppa:danielrichter2007/grub-customizer
        8  sudo apt-get update
        9  sudo apt-get install grub-customizer
       10  android
       11  sudo apt-get install compizconfig-settings-manager
       12  gcc -version
       13  gcc -v
       14  sudo gedit hosts
       15  cd icecream
       16  repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
       17  repo sync -j16
       18  curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
       19  chmod a+x ~/bin/repo
       20  repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
       21  repo sync -j16
       22  exit
       23  lspci
       24  lspci -v -s 00:02.0
       25  sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
       26  sudo apt-get install git-core gnupg flex bison gperf build-essential   zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs   x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev   libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown   libxml2-utils
       27  cd ~/android/icecream
       28  . build/envsetup.sh
       29  lunch
       30  make -j4
       31  make Launcher2
       32  sudo apt-get install GCC-4.4.5
       33  sudo apt-get install gcc-4.4.5
       34  sudo apt-get install gcc-4.4
       35  gcc -v
       36  sudo apt-get remove gcc-4.6
       37  sudo apt-get install gcc-4.4
       38  exit
       39  gcc -v
       40  sudo apt-get install gcc-4.4
       41  exit
       42  gcc -v
       43  exit
       44  cd ~/android/icecream
       45  . build/envsetup.sh
       46  lunch full-eng
       47  make -j4
       48  sudo apt-get install gcc-4.1
       49  ls -al /usr/bin
       50  sudo apt-get install g++
       51  apt-get install gcc-4.1 g++-4.1
       52  sudo apt-get install gcc-4.1 g++-4.1
       53  sudo apt-get install gcc-4.4 g++-4.4
       54  sudo apt-get remove gcc-4.6
       55  sudo apt-get install gcc-4.4 g++-4.4
       56  gcc -v
       57  make -j4
       58  make clean
       59  make -j4
       60  gcc -v
       61  sudo apt-get install gcc-4.4-multilib
       62  gcc -v
       63  make clean
       64  make -j4
       65  exit
       66  cd usr/bin
       67  exit
       68  gksu nautilus
       69  gcc -v
       70  cd ~/anroid/icecream
       71  cd ~/android/icecream
       72  . build/envysetup.sh
       73  ls
       74  . build/envsetup.sh
       75  lunch full-eng
       76  make -j4
       77  sudo apt-get install cc
       78  make clean
       79  make -j4
       80  exit
       81  make
       82  gcc --version
       83  sudo apt-get install gcc-4.4-multilib
       84  sudo apt-get install gcc-4.4 g++-4.4
       85  bash =
       86  bash --help
       87  sudo apt-get install git-core gnupg flex bison gperf build-essential   zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs   x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev   libgl1-mesa-dev g++-4.4multilib mingw32 tofrodos python-markdown   libxml2-utils
       88  sudo apt-get install git-core gnupg flex bison gperf build-essential   zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs   x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev   libgl1-mesa-dev g++-4.4multilib mingw32 tofrodos python-markdown   libxml2-utils lib32readline-gplv2-dev
       89  sudo apt-get install git-core gnupg flex bison gperf build-essential   zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs   x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev   libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown   libxml2-utils lib32readline-gplv2-dev
       90  sudo apt-get install git-core gnupg flex bison gperf build-essential   zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs   x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev   libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown   libxml2-utils 
       91  sudo apt-get install git-core gnupg flex bison gperf build-essential   zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs   x11proto-core-dev libx11-dev lib32z-dev   libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown   libxml2-utils 
       92  sudo apt-get install git-core gnupg flex bison gperf build-essential   zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs   x11proto-core-dev libx11-dev lib32z-dev   libgl1-mesa-dev g++-4.4-multilib mingw32 tofrodos python-markdown   libxml2-utils 
       93  make -j4
       94  make clean
       95  sudo make clean
       96  make -j4
       97  exit
       98  cd ~/android/icecream
       99  make clean
      100  . build/envsetup.sh
      101  lunch 1
      102  make -j4
      103  sudo make -j4
      104  sudo apt-get install cygwin
      105  sudo apt-get install cpp
      106  bash
      107  exit
      108  cd ~/android/icecream
      109  . build/envsetup.sh
      110  lunch 1
      111  make -j4
      112  gksu nautilus
      113  make clean
      114  make -j4
      115  gcc -version
      116  gcc -v
      117  make clean
      118  make -j4
      119  make clean
      120  make -j4
      121  lunch
      122  make clean
      123  make -j4
      124  sudo apt-get install gcc-multilib
      125  make clean
      126  make -j4
      127  history
    JerryScript and bigsupersquid like this.
    11-20-2011 06:54 PM
  10. JerryScript's Avatar
    I spent the day watching football, you guys missed some good games.

    I'm torn, which do I do first, work on the IHO commit to CM7.2, or work on the ICS build?!?

    Luckily I have tomorrow free for most of the day, so of course that means I won't be sleeping much tonite! You guys are making some great progress, gonna start digging in now and see if I can help.
    asadullah likes this.
    11-20-2011 10:40 PM
  11. asadullah's Avatar
    @jerryscript good luck whatever you do (ICS) I gotta work in the morn but no school this week and four day weekend coming up thursday
    11-20-2011 11:02 PM
  12. pbailey212's Avatar
    I spent the day watching football, you guys missed some good games.

    I'm torn, which do I do first, work on the IHO commit to CM7.2, or work on the ICS build?!?

    Luckily I have tomorrow free for most of the day, so of course that means I won't be sleeping much tonite! You guys are making some great progress, gonna start digging in now and see if I can help.
    Did you watch my packers get another W? You should do a new backside with a current cm repo, then continue on your ics journey, the sooner you guys get it figured out, the sooner we can all quit seeing "I can't wait for ics" posts everywhere. If I wasn't so stupid/short on time I would love to help, I am always down for trying experements for you guys though
    11-20-2011 11:24 PM
  13. JerryScript's Avatar
    You're right, no matter how much I want to dive into it, the simple fact is I won't be able to get a working build of ics till other people work out issues I don't have the knowledge to even find (porting various libraries, etc). I'll bring BACKside up to CM7.2, then start diving into ics deeper.

    @asadullah & bigsupersquid: Thanks again for sharing what you've done so far, can't wait to dig into it!

    @packersbailey212: AR makes BF look like a distant memory, glad to see that!

    Go Cowboys!
    Spiral_ouT#AC likes this.
    11-21-2011 02:14 AM
  14. jdcnosse's Avatar
    @Someone who knows lol

    So when I am syncing the CM repo, after adding the CM repo to git remote, do I have to use git fetch/git merge for every folder or is it just a one time command?

    eg. my "build" is at ~/android/iho so is it just one "git fetch" then "git merge," or do I do it to every folder inside iho (so ~/android/iho/android, ~/android/iho/build, etc)
    11-21-2011 08:55 AM
  15. bigsupersquid's Avatar
    @jdcnosse: sorry, I'm fairly clueless about git and repo...

    re:ics
    bah. generic boots to logo and logcat, crashes at entropy service died.
    if I don't format /cache when installing, boot loads the entropy service ok and crashes at the next step, power manager.
    bit of logcat at the crash point, if anyone knows enough of what's up to interpret it for me I'd love to hear it.
    Code:
    I/SystemServer( 1453): Entered the Android system server!
    I/SystemServer( 1453): Entropy Service
    I/SystemServer( 1453): Power Manager
    F/libc    ( 1453): Fatal signal 7 (SIGBUS) at 0x00000000 (code=128)
    I/DEBUG   ( 1375): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    I/DEBUG   ( 1375): Build fingerprint: 'unknown'
    I/DEBUG   ( 1375): pid: 1453, tid: 1466  >>> system_server <<<
    I/DEBUG   ( 1375): signal 7 (SIGBUS), code 128 (?), fault addr 00000000
    I/DEBUG   ( 1375):  r0 41058e68  r1 45ab1e95  r2 0000005d  r3 4080accb
    I/DEBUG   ( 1375):  r4 00ff0000  r5 0000ff00  r6 00000000  r7 00000000
    I/DEBUG   ( 1375):  r8 46b04bdc  r9 46a04c84  10 46a04c70  fp 46b04bf4
    I/DEBUG   ( 1375):  ip 40874fec  sp 46b04b78  lr 401c50c5  pc 401c4ada  cpsr 80000030
    I/DEBUG   ( 1375):  d0  4040000040000000  d1  3ff0000000000000
    I/DEBUG   ( 1375):  d2  bebbbc6c1a570a20  d3  3f1155e54e7e8408
    I/DEBUG   ( 1375):  d4  bfb1be5a93a83e1d  d5  4000000000000000
    I/DEBUG   ( 1375):  d6  4ad4ecd000000000  d7  000000634e265902
    I/DEBUG   ( 1375):  d8  0000000000000000  d9  0000000000000000
    I/DEBUG   ( 1375):  d10 0000000000000000  d11 0000000000000000
    I/DEBUG   ( 1375):  d12 0000000000000000  d13 0000000000000000
    I/DEBUG   ( 1375):  d14 0000000000000000  d15 0000000000000000
    I/DEBUG   ( 1375):  scr 80000012
    I/DEBUG   ( 1375): 
    I/DEBUG   ( 1375):          #00  pc 00016ada  /system/lib/libnativehelper.so
    I/DEBUG   ( 1375):          #01  pc 000170c0  /system/lib/libnativehelper.so
    I/DEBUG   ( 1375):          #02  pc 0001eeb0  /system/lib/libdvm.so (dvmPlatformInvoke)
    I/DEBUG   ( 1375):          #03  pc 0005940c  /system/lib/libdvm.so (_Z16dvmCallJNIMethodPKjP6JValuePK6MethodP6Thread)
    I/DEBUG   ( 1375):          #04  pc 0004ccba  /system/lib/libdvm.so (_Z21dvmCheckCallJNIMethodPKjP6JValuePK6MethodP6Thread)
    I/DEBUG   ( 1375):          #05  pc 00030ccc  /system/lib/libdvm.so
    I/DEBUG   ( 1375):          #06  pc 000345b4  /system/lib/libdvm.so (_Z12dvmInterpretP6ThreadPK6MethodP6JValue)
    I/DEBUG   ( 1375):          #07  pc 0006c558  /system/lib/libdvm.so (_Z14dvmCallMethodVP6ThreadPK6MethodP6ObjectbP6JValueSt9__va_list)
    I/DEBUG   ( 1375):          #08  pc 0006c576  /system/lib/libdvm.so (_Z13dvmCallMethodP6ThreadPK6MethodP6ObjectP6JValuez)
    I/DEBUG   ( 1375):          #09  pc 000601ae  /system/lib/libdvm.so
    I/DEBUG   ( 1375):          #10  pc 00012e14  /system/lib/libc.so (__thread_entry)
    I/DEBUG   ( 1375):          #11  pc 0001295c  /system/lib/libc.so (pthread_create)
    I/DEBUG   ( 1375): 
    I/DEBUG   ( 1375): code around pc:
    I/DEBUG   ( 1375): 401c4ab8 881bd504 0a19021d 80014329 bdf0b009 
    I/DEBUG   ( 1375): 401c4ac8 b085b5f0 24ff25ff 26009201 0424022d 
    I/DEBUG   ( 1375): 401c4ad8 c908e00d 061f3601 433a0e1a 402f1c1f 
    I/DEBUG   ( 1375): 401c4ae8 433a023f 0a1f4023 433b1c13 9a01c008 
    I/DEBUG   ( 1375): 401c4af8 d1ee4296 bdf0b005 b087b5f0 24ff25ff 
    I/DEBUG   ( 1375): 
    I/DEBUG   ( 1375): code around lr:
    I/DEBUG   ( 1375): 401c50a4 00b326bb 220058d6 60a047b0 68a0ac03 
    I/DEBUG   ( 1375): 401c50b4 d0052800 19c000bf 9a0d1c29 fd02f7ff 
    I/DEBUG   ( 1375): 401c50c4 f7f61c20 e007fac5 26d36802 950000b3 
    I/DEBUG   ( 1375): 401c50d4 1c3a58d4 47a09b0d bdf0b007 b087b5f0 
    I/DEBUG   ( 1375): 401c50e4 aa0e1c15 78131c19 2b009f0c ac03d01e 
    I/DEBUG   ( 1375): 
    I/DEBUG   ( 1375): stack:
    I/DEBUG   ( 1375):     46b04b38  41058e68  
    I/DEBUG   ( 1375):     46b04b3c  8b219541  
    I/DEBUG   ( 1375):     46b04b40  05300005  
    I/DEBUG   ( 1375):     46b04b44  001a1a80  
    I/DEBUG   ( 1375):     46b04b48  00000000  
    I/DEBUG   ( 1375):     46b04b4c  41058e68  
    I/DEBUG   ( 1375):     46b04b50  05300005  
    I/DEBUG   ( 1375):     46b04b54  4080accb  /system/lib/libdvm.so
    I/DEBUG   ( 1375):     46b04b58  408549c9  /system/lib/libdvm.so
    I/DEBUG   ( 1375):     46b04b5c  41058e68  
    I/DEBUG   ( 1375):     46b04b60  05300005  
    I/DEBUG   ( 1375):     46b04b64  00000000  
    I/DEBUG   ( 1375):     46b04b68  69686142  
    I/DEBUG   ( 1375):     46b04b6c  00000000  
    I/DEBUG   ( 1375):     46b04b70  df0027ad  
    I/DEBUG   ( 1375):     46b04b74  00000000  
    I/DEBUG   ( 1375): #00 46b04b78  4086ac02  /system/lib/libdvm.so
    I/DEBUG   ( 1375):     46b04b7c  0000005d  
    I/DEBUG   ( 1375):     46b04b80  4201ed01  
    I/DEBUG   ( 1375):     46b04b84  4001c83d  /system/lib/libc.so
    I/DEBUG   ( 1375):     46b04b88  00000318  
    I/DEBUG   ( 1375):     46b04b8c  46b04bac  
    I/DEBUG   ( 1375):     46b04b90  45ab1e95  
    I/DEBUG   ( 1375):     46b04b94  4080ac41  /system/lib/libdvm.so
    I/DEBUG   ( 1375):     46b04b98  00000000  
    I/DEBUG   ( 1375):     46b04b9c  401c50c5  /system/lib/libnativehelper.so
    I/DEBUG   ( 1375): #01 46b04ba0  46a04e08  
    I/DEBUG   ( 1375):     46b04ba4  46a04df4  
    I/DEBUG   ( 1375):     46b04ba8  46b04bf4  
    I/DEBUG   ( 1375):     46b04bac  001a1a80  
    I/DEBUG   ( 1375):     46b04bb0  05300005  
    I/DEBUG   ( 1375):     46b04bb4  41058e68  
    I/DEBUG   ( 1375):     46b04bb8  00000004  
    I/DEBUG   ( 1375):     46b04bbc  41fc0ea0  
    I/DEBUG   ( 1375):     46b04bc0  401c507d  /system/lib/libnativehelper.so
    I/DEBUG   ( 1375):     46b04bc4  00000000  
    I/DEBUG   ( 1375):     46b04bc8  46a04c98  
    I/DEBUG   ( 1375):     46b04bcc  407e0eb4  /system/lib/libdvm.so
    edit: dang, its a dalvik error, and looks like andy is having problems with his dalvik fix now, too. maybe I'll try armv5te again with the armv5-webrtc fix and see if that will boot/run like this attempt did. I'm a little frustrated with partial booting, but it's still a lot cooler than 'system/bin/sh not found'

    since my last 4 tries at building generic_armv5 wouldn't boot, but basically the exact same thing with TARGET_ARCH_VARIANT := armv6k-vfp would, I've added TARGET_ARCH_VARIANT := armv5te-vfp into build/target/board/generic_armv5/BoardConfig.mk to see if lacking that was what was causing my binaries to malfunction. here goes!

    final edit:
    this thread's getting a bit mixed up between IHO and ICS, IMHO!
    I'm going to start a new thread specifically for building ICS, to get around that.
    JerryScript and BobZhome like this.
    11-21-2011 10:18 AM
  16. JerryScript's Avatar
    @Someone who knows lol

    So when I am syncing the CM repo, after adding the CM repo to git remote, do I have to use git fetch/git merge for every folder or is it just a one time command?

    eg. my "build" is at ~/android/iho so is it just one "git fetch" then "git merge," or do I do it to every folder inside iho (so ~/android/iho/android, ~/android/iho/build, etc)
    It's a bit confusing, I know.

    Here's how I do it, someone better at git might provide a better method. I'm using a sort of brute force approach, which means if there's a merge conflict, you have to manually fix it with this method. (you probably have to manually fix merge conflicts with any method)

    1- Repo init and repo sync with IHO
    2- cd frameworks/base (repeat with vendor/lge/thunderc and device/lge/thunderc)
    3- Each of the project directories is a git repository of it's own, so we can pull/fetch/merge/commit inside them
    4- Once in each project's folder you need to sync with CM use the following command:
    git pull git://github.com/CyanogenMod/android_frameworks_base.git
    (you may need to add the -b gingerbread, depends on how you set up your repo/git)
    5- git commit -a -m "Sync with CM"
    6- Repeat with the other folders IHO has forked from CM
    (note- I wouldn't sync dalvik till you have a working build)

    You can use git status and git log in each project folder to determine what point your current files are at.
    11-21-2011 12:46 PM
  17. jdcnosse's Avatar
    It's a bit confusing, I know.

    Here's how I do it, someone better at git might provide a better method. I'm using a sort of brute force approach, which means if there's a merge conflict, you have to manually fix it with this method. (you probably have to manually fix merge conflicts with any method)

    1- Repo init and repo sync with IHO
    2- cd frameworks/base (repeat with vendor/lge/thunderc and device/lge/thunderc)
    3- Each of the project directories is a git repository of it's own, so we can pull/fetch/merge/commit inside them
    4- Once in each project's folder you need to sync with CM use the following command:
    git pull git://github.com/CyanogenMod/android_frameworks_base.git
    (you may need to add the -b gingerbread, depends on how you set up your repo/git)
    5- git commit -a -m "Sync with CM"
    6- Repeat with the other folders IHO has forked from CM
    (note- I wouldn't sync dalvik till you have a working build)

    You can use git status and git log in each project folder to determine what point your current files are at.

    I think the most confusing for me is that repo is based off git...yet you can have repo and git set up in the same directory for two different things...

    that and all the different git commands. It's like we're back before I was born! (1988)

    EDIT: When you say "repeat with vendor/lge/thunderc and device/lge/thunderc" which cyanogenmod repo am I syncing these folders with? I see frameworks/base, dalvik, and vendor/cyanogen have all been forked from the main cyanogenmod repos.

    EDIT2: Well I sorta got it working with frameworks/base, but there's apparently a lot of conflicts, so git pull won't work. lol Guess I gotta use git fetch...
    11-21-2011 09:13 PM
  18. JerryScript's Avatar
    You are syncing with the ones that match the tree, vendor_lge_thunderc == vendor/lge/thunderc, android_vendor_cyanogen == vendor/cyanogen, android_device_lge_thunderc == device/lge/thunderc, etc. So for example, you cd into vendor/lge/thunderc and type
    git pull git://github.com/CyanogenMod/vendor_lge_thunderc.git

    Use git status often to see what files have been changed. If the files have >>>>>>head sections added to them, compare the file to what you want it to be (look in the github repository), fix it, then use git add, and once all files are fixed, use git commit -a -m "Fix merge conflict". Once this is done, it is part of your local repository, and will not show up under a repo diff.
    jdcnosse likes this.
    11-22-2011 09:30 AM
  19. bigsupersquid's Avatar
    You are syncing with the ones that match the tree, vendor_lge_thunderc == vendor/lge/thunderc, android_vendor_cyanogen == vendor/cyanogen, android_device_lge_thunderc == device/lge/thunderc, etc. So for example, you cd into vendor/lge/thunderc and type
    git pull git://github.com/CyanogenMod/vendor_lge_thunderc.git

    Use git status often to see what files have been changed. If the files have >>>>>>head sections added to them, compare the file to what you want it to be (look in the github repository), fix it, then use git add, and once all files are fixed, use git commit -a -m "Fix merge conflict". Once this is done, it is part of your local repository, and will not show up under a repo diff.
    shouldn't the thunderc stuff come from
    git pull git://github.com/inferiorhumanorgans/vendor_lge_thunderc.git and device_lge_thunderc.git?
    or maybe your (JerryScript's) or BobZhome's github?
    11-22-2011 10:07 AM
  20. konspiracy's Avatar
    Hey guys what was the fix for the latest cmparts error?
    It was mentioned a couple times in this thread but I cant figure out how to solve it.
    Nevermind I have it sorted out I think.
    Also how come with some of my other builds I would have to pull the proprietary files from the phone?
    Is this because our phones never received the proper files for gingerbread?

    Update..... Okay I have my first biuld without errors.... It was very fast though, I do have a 6 core phenom running at 3.7ghz though. I will flash and see whats up.
    11-22-2011 10:41 AM
  21. JerryScript's Avatar
    shouldn't the thunderc stuff come from
    git pull git://github.com/inferiorhumanorgans/vendor_lge_thunderc.git and device_lge_thunderc.git?
    or maybe your (JerryScript's) or BobZhome's github?
    I was referring to how I pull in changes from CM. This is after a repo sync with IHO.

    I pull in changes from CM's folders, delete what I don't want to keep, then commit to my local repo. This is an example of why using git fetch and then git merge is preferable to some.
    11-22-2011 12:14 PM
  22. JerryScript's Avatar
    Hey guys what was the fix for the latest cmparts error?
    It was mentioned a couple times in this thread but I cant figure out how to solve it.
    Nevermind I have it sorted out I think.
    Also how come with some of my other builds I would have to pull the proprietary files from the phone?
    Is this because our phones never received the proper files for gingerbread?

    Update..... Okay I have my first biuld without errors.... It was very fast though, I do have a 6 core phenom running at 3.7ghz though. I will flash and see whats up.
    It's on page 23, the omap linker in pathmap.mk

    The proprietary files are those files we don't have source code for. They are pulled directly from a stock phone ( which makes their use with ics tricky at best )
    11-22-2011 12:20 PM
  23. konspiracy's Avatar
    It's on page 23, the omap linker in pathmap.mk

    The proprietary files are those files we don't have source code for. They are pulled directly from a stock phone ( which makes their use with ics tricky at best )
    So will we ever be able to utilize the gpu acceleration in ICS?
    I know our phones have a dedicated gpu is why I ask.

    Yay my first build booted up!!!!
    I have to see if it will work with dark tremor i think I borked my launcher pro app.

    Edit: Is there a command I can use to see how long it takes to compile this? I think it took me like under 40 min. to build.
    11-22-2011 12:36 PM
  24. JerryScript's Avatar
    So will we ever be able to utilize the gpu acceleration in ICS?
    I know our phones have a dedicated gpu is why I ask.

    Yay my first build booted up!!!!
    I have to see if it will work with dark tremor i think I borked my launcher pro app.

    Edit: Is there a command I can use to see how long it takes to compile this? I think it took me like under 40 min. to build.
    Glad to see you got it going! Looking forward to seeing your ice-cream-ginger port.

    Takes me between 45min-1hour, about 20 if just doing an incremental build. I don't know of any timer for builds, you could write a script that would do it pretty easily though.
    11-22-2011 12:47 PM
  25. konspiracy's Avatar
    Glad to see you got it going! Looking forward to seeing your ice-cream-ginger port.

    Takes me between 45min-1hour, about 20 if just doing an incremental build. I don't know of any timer for builds, you could write a script that would do it pretty easily though.
    Im not gonna even attempt to do an ics build untill I understand what people are currently trying. I do understand that they have to compile for armv6 and not arm7. Everything after that is in another language.

    Edit: also when I git pull the vendor files from cyanogen should it be downloading files? I recieved a list of file changes but it was very fast.
    Also what do I need to git pull from to make a 7.2 build?

    Also would it be frowned upon to remove cmstats? I mean it uses like 10 to 20 mb of ram on average.
    11-22-2011 12:56 PM
1,060 ... 1011121314 ...
LINK TO POST COPIED TO CLIPBOARD