01-17-2013 12:07 AM
1,060 ... 910111213 ...
tools
  1. bigsupersquid'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.
    most likely blarf went with what actually worked rather than making it fit the cm standards. I suspect partly the "if it ain't broke, don't fix it" philosophy, which I fully agree with.
    anyone handling the maintainer position would really be in for a lot of work, I bet.
    I'm much more interested in what changes would be necessary for inclusion, it's possible they'd help the device folder fit/work better with aosp... iho device_lge_thunderc really doesn't align well at all with the device folder format as that seems to be set up in aosp or CAF (which is similar but different)
    11-17-2011 02:08 PM
  2. mrg666'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.
    Whoever takes the lead, I am ready to help. Blarf's work is an excellent base to start with.
    11-17-2011 02:15 PM
  3. JerryScript's Avatar
    Yeah, apparently the only way to get help from the CM dev team is to use irc. Seems a project as large as CM would benefit from a path to inclusion being laid out in writing, rather than going and begging for help in a chat room.
    bigsupersquid likes this.
    11-17-2011 02:21 PM
  4. Whyzor's Avatar
    Yeah, apparently the only way to get help from the CM dev team is to use irc. Seems a project as large as CM would benefit from a path to inclusion being laid out in writing, rather than going and begging for help in a chat room.
    hackers aren't exactly known to be good at documenting things
    11-17-2011 02:27 PM
  5. bigsupersquid's Avatar
    not only hackers! google completely killed the device porting section of their online docs as 'outdated' and never bothered to revive or update it yet. kandroid is the best source I've found for those lost docs.

    irc sucks, unless you like to chat.
    its main benefit is speed of response I think.

    new development for cm would benefit from standards in writing, but the cm maintainers themselves probably wouldn't see a lot of benefit from good documentation of requirements except for improved submissions for inclusion.
    11-17-2011 02:31 PM
  6. asadullah's Avatar
    Couple questions. Has anyone successfully built the generic ics source yet? Is cyanogen the only thing being worked on?

    I
    11-17-2011 06:29 PM
  7. bigsupersquid's Avatar
    generic_armv5 builds to a point and crashes with assembler errors. armv6-vfp fouls the dalvik build instead, and doesn't get as far as generic_armv5.
    plain generic now defaults to armv7
    it's a big fight to get armv6-vfp all the way into the new dalvik, looks like they changed variable names and stuff. I gave up for now...
    I'm right now trying to build just libdvm for armv5te-vfp and build everything else for armv6-vfp, we'll see how that goes.

    edit:
    no dice trying to split it up, changing TARGET_ARCH_VARIANT and TARGET_CPU_ABI after dalvik is completely built still causes spazzes in dalvik about armv6. I'm going back to poking at armv5te-vfp.
    JerryScript likes this.
    11-17-2011 06:57 PM
  8. asadullah's Avatar
    I'm resyncing the source I wasn't able to compile generic twice. May have something to do with upgrading from 11.04 to 11.10 which I recently did. Or other things cm7 is cool bit I really don't want to wait two months for it even upgraded my ram to 8 gigs (all she can take)
    11-17-2011 07:59 PM
  9. bigsupersquid's Avatar
    dunno about ubuntu version, I run debian sqeeze and rarely update anything. I'm maxed at 2GB ram on my 1.6GHz fujitsu laptop. Works way better than my old dell desktop @2GHz with 512MB ram, about 5x as fast. Only about 5 hrs to compile IHO with my newer toy

    edit: I'm still getting new stuff on re-sync.
    11-17-2011 09:19 PM
  10. JerryScript's Avatar
    You could look on craigslist and find something faster very cheap. An IHO build on my 3.2ghz system (2.7 oc'd) with 2gig ram completes in about 45 minutes, incremental builds only take about 15 minutes (building a package, then the whole project after it's been built previously). I can't imagine waiting 5 hours for a build to complete, that would drive me crazy trying to debug!

    JB said in the release announcement that the push was so large we could expect to have incomplete syncs for days. Not sure if that's the issue causing sync to grab more files each time, or if they are already pushing new stuff out.
    11-18-2011 12:34 AM
  11. JerryScript's Avatar
    Ok, I just spent an hour waiting in the #cyanogenmod-dev irc, kinda wonder if they made me wait to make me stew a bit. I paced my questions out at least 5 minutes between so as to not **** anyone off, and tried rephrasing them as well, since it seems as if we need to tiptoe around a few egos.

    Here's the chat:
    Code:
    *** Topic is Welcome to #CyanogenMod-Dev IRC - See: http://goo.gl/4yOnc :: General CyanogenMod/Android Development Discussion | korg repos are now available on cyanogenmod github:  http://kan.gd/105q 
    *** Channel mode is +cnrt 
    *** Nushio has quit (Ping timeout: 248 seconds) 
    *** TomTom has joined #cyanogenmod-dev 
    *** firelord42 has quit (Quit: Night all!!!!) 
    <JerryScript> I'm looking for some help preparing a repo's device folder for a push to CM. 
    <JerryScript> The repo is inferiorhumanorgans, for the thunderc board on the Optimus line of phones. 
    <JerryScript> We currently support 5 phone models with over 4 thousand users for the past few months, and have 98% of functionality, only headsets issues remain. 
     -note--10 minutes
    <JerryScript> I was told by Koush to come to this chat room and ask for help, is anyone available tonite? 
    -note--15 minutes
    <JerryScript> Can anyone here offer advice on preparing a device folder for a push to CM7.2? 
    *** tophyr has joined #cyanogenmod-dev
    -note--25 minutes
    <JerryScript> Could someone offer some advice on preparing my device folder, or perhaps a link to a roadmap to getting a device accepted into CM? 
    *** MongooseHelix has quit (Ping timeout: 240 seconds) 
    -note--30 minutes
    <JerryScript> What are the requirements for a device folder to be accepted into CM? 
    *** Kaik541 has joined #cyanogenmod-dev 
    *** ChanServ sets mode +v on Kaik541 
    *** Hashcode has quit (Quit: Leaving) 
    -note--40 minutes
    <JerryScript> How do you properly prepare a device tree for acceptance into CM? 
    <Kaik541> JerryScript: virgin sacrifice 
    <JerryScript> lol, koush sent me here to ask for help on this matter 
    <Kaik541> oh, then wait for someone to give a real answer 
    <JerryScript> no prob, I've been waiting for 45 minutes, I've got some time to wait 
    *** sduvick has joined #cyanogenmod-dev 
    *** sduvick has joined #cyanogenmod-dev 
    <sduvick> hey guys, interesting/annoying error in trying to boot cm: 
    <sduvick>  bionic/linker/linker.c:1280| ERROR:  2615 cannot locate '_ZN7android16CameraParameters3setEPKci'... 
    *** sduvick has quit (Ping timeout: 260 seconds) 
    -note--55 minutes
    <koush> JerryScript: send us a submission on gerrit 
    <koush> that has the repositories we need to fork 
    *** sduvick has joined #cyanogenmod-dev 
    *** skorgon has quit (Ping timeout: 248 seconds) 
    <JerryScript> Can do, but I was hoping to set it up more to CM liking before submission, just because it works for us doesn't mean it will for CM 
    -note--1 hour
    <optedoblivion> Hence gerrit 
    <optedoblivion> So we can see what you are doing and hackborn it 
    <Kaik541> JerryScript: once you put it on gerrit, everyone wlil slam you for your stupid mistakes until it's "CM approved" 
    <JerryScript> gotcha, just didn't think such a raw submission was appropriate, thanks for the info everyone 
    <jcsullins> JerryScript: yeah, can be a humbling experience 
    <optedoblivion> JerryScript: yeah you can reup a patch set to the same change id 
    <optedoblivion> which keeps a nice history 
    <Kaik541> make sure you add ricardo so he can tell you how best to unfux0r anything 
    <optedoblivion> and yadda yadda 
    <optedoblivion> what Kaik541 said 
    <JerryScript> I've no problem with that, I'm not even close to being in the CM teams league, just doing what I can to help 
    <optedoblivion> meh it's not about leagues br0 
    <optedoblivion> it's about helpin out 
    <JerryScript> thnx
    So the actual answer to my original query took a single line in irc chat, yet the same couldn't be offered elsewhere, hoops.

    If Blarf doesn't want to do the submission, then we need to decide which fork to submit, perhaps create a new one just for this purpose. And of course, as you could see from the chat room, we are going to have to keep our thick skins on!
    mrg666, mustafu and Whyzor like this.
    11-18-2011 03:04 AM
  12. bigsupersquid's Avatar
    a new fork with the best picks of all your stuff (bob's camera, etc) might be good...
    somebody's going to have to be patient, and thick-skinned is a good term too.

    I wonder if you were an adequate virgin sacrifice?
    maybe you're still being dressed and anointed before the real ceremony
    you did get an answer of sorts, anyway.
    11-18-2011 08:30 AM
  13. mrg666's Avatar
    CM people were asking if IHO was stable enough. Actually, IHO is more stable and complete than at least the official Nook Color build I have used/built. For this reason, I would prefer a new fork to submit to CM so that we can keep IHO as it is while the new fork is modified for CM merge which will create some minor problems for a while.

    The android_frameworks_base, android_dalvik, and android_system_bluetooth repos need to be linked to CM repo. There are only two tiny commits that differentiate IHO's frameworks_base from CM. The other repos are similar. We need to resolve those differences by submitting patches to CM. We could use preprocessor definitions in the patches to add those changes without affecting the other devices.

    Then, there are three other vendor and device repos that we need to make sure they integrate with the CM repo
    android_vendor_cyanogen
    vendor_lge_thunderc
    android_device_lge_thunderc

    We will also need to separate the proprietary files from the repo. Those other added to the local copy of the repo before building the ROM for the devices in CM.

    I think, correct if I am wrong, we can keep the kernel source separate and add the binaries in the repo as we do with IHO.

    These are my initial thoughts.

    Edit: let's not forget about the surfaceflinger and camera problems introduced by recent commits.
    11-18-2011 09:42 AM
  14. bigsupersquid's Avatar
    back around to ics, there's a good info thread here, at xda for the hero... also an armv6 (though different variant) and they've put how to workaround the webrtc assembly errors among other things.

    edit: there was some mention of errors with llvm over there, but so far my armv5te-vfp based build has gotten past that point without glitches (using a lightly modified device_lge_thunderc folder from iho and a patched-up device_lge_products folder roughly based on the iho android_vendor_cyanogen folder.). hopefully I won't have to wait until tomorrow morning to see the result...
    probably should've stuck with generic_armv5 to test the build, but why not just jump in with both feet before testing the water temperature?
    mrg666 likes this.
    11-18-2011 10:36 AM
  15. mustafu's Avatar
    The possibility of becoming official would be exciting for sure!
    11-18-2011 10:57 AM
  16. un1ocked's Avatar
    please share how to flash sprint stock firmware to my original OV

    using what tools? KDZ updater?
    i have stock sprint firmware, LS670ZVD_12.SD_12.P60675
    also stock virgin firmware, in case my OV bricked, the VM670ZV5_07.S5_07.P61007
    11-18-2011 01:46 PM
  17. pbailey212's Avatar
    please share how to flash sprint stock firmware to my original OV

    using what tools? KDZ updater?
    i have stock sprint firmware, LS670ZVD_12.SD_12.P60675
    also stock virgin firmware, in case my OV bricked, the VM670ZV5_07.S5_07.P61007
    Don't do it, its been tried and failed by the smartest of people in the community, best case scenerio, you will never have data again, worst case scenerio, you will be waiting at target at midnight to get your self a new $50 ov
    11-18-2011 01:54 PM
  18. bigsupersquid's Avatar
    please share how to flash sprint stock firmware to my original OV

    using what tools? KDZ updater?
    i have stock sprint firmware, LS670ZVD_12.SD_12.P60675
    also stock virgin firmware, in case my OV bricked, the VM670ZV5_07.S5_07.P61007
    the virgin 'firmware' is crap, unflashable crap.
    you will be permanently sprint-ified if you flash the os firmware.
    search the unbrick threads on the s forum if you're undeterred by the warnings.
    BTW, kp500-utils deleted my ESN and AKEY, so beware, use the LGNPST instead, it's cleaner.

    also, way off-topic for the thread, start a new one or resurrect a dead one on the same topic, please.
    11-18-2011 02:28 PM
  19. asadullah's Avatar
    Alright so I'm running Ubuntu 11.10 64 bit I repo synced and tried to do a straight generic build. Well after about ten minutes or so it would stop building on this error
    Code:
    <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by
    default]
    Of course I'm like wtf but I found an answer on google source to help fix the problem go into the folder
    ~/android/icecream/build/core/combo and open HOST_linux-x86.mk scroll down to line 56 and change it from this
    Code:
    HOST_GLOBAL_CFLAGS += -D_FORTIFY_SOURCE=0
    to this
    Code:
    HOST_GLOBAL_CFLAGS += -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0
    JerryScript likes this.
    11-18-2011 08:20 PM
  20. bigsupersquid's Avatar
    mine's gotten all the way into webkit now before crashing with a new error (google says it's related to the wrong cpu or something like that)
    /tmp/ccmbolln.s: Assembler messages:
    /tmp/ccmbolln.s:14060: Error: invalid immediate: 983040 is out of range
    /tmp/ccmbolln.s:14060: Error: value of 983040 too large for field of 2 bytes at 2046
    make: *** [out/target/product/thunderc/obj/STATIC_LIBRARIES/libjs_intermediates/Source/JavaScriptCore/jit/JIT.o] Error 1
    I haven't googled up any solution for that yet. So I'm still stalled out for now.
    But I haven't gotten many of the errors I've read about, like libaudio problems or that FORTIFY_SOURCE error, at all, which is odd... may be related to using debian instead of ubuntu.

    edit:
    sweet.
    disabling JIT moves the build on. Fix it later after getting a complete compile with whatever else it takes to be removed, like webrtc...
    In BoardConfig.mk, change the JIT stuff to:
    Code:
    WITH_JIT := false
    ENABLE_JSC_JIT := false
    #JS_ENGINE := v8
    edit again: there's one file, JIT.h or .cpp (I forget) that I had to comment out two lines to compile (66 and 67 if I remember right.) Figured it didn't matter too much since the JIT was supposed to be disabled anyway, but they're a major part of the jit functionality if I read the comment right.

    also had to include lupohirp's fix for libaudio from the xda p500 ics thread, it worked for me to finish a build after the other changes.
    JerryScript likes this.
    11-18-2011 11:20 PM
  21. bigsupersquid's Avatar
    so, it compiled completely, both generic_armv5 and my tweaked thunderc, but they both still had whatever glitch I've been getting with building aosp that makes the binaries not runnable. install into /system, permissions all look right with ls -al, won't run anything though, except init in ramdisk.
    (it's huge by the way, over 90 MB system.img)
    to check it out, I:
    add busybox from xionia cwma while booted into recovery for /system/bin/sh:
    mount system
    Code:
    cp -p /sbin/busybox /system/xbin/busybox
    rm /system/bin/sh
    ln -s /system/xbin/busybox /system/bin/sh
    and add adbd to /sbin in ramdisk
    then it boots to being recognized by adb, and can use busybox to examine dmesg and ps in the adb shell.
    nand mounted fine by init.
    no logcat.
    says 'init:cannot read /system/bin/installd' and etc. in dmesg after setting up devices and mtd.
    can use the recovery's busybox in /system, but other binaries say 'x: not found' even though 'busybox ls' shows them.
    and if it's building for the wrong chipset or something, why does init run?
    frustrating. I've gotten one generic aosp gingerbread build out of 10 to boot up with a good boot.img. none so far with the ics except for those abortive boots where it fails to run the /system binaries.

    I'm sure it's some kind of install or permissions error. I can adb push /system completely from gb or ics build folder while android is running on the phone, and run toolbox and such afterwards in adb shell, but a reboot doesn't work after that (and ICS stuff over CM7 causes all kinds of FCs in the running UI after the push, where GB doesn't; but no surprises there.)
    I've tried the recovery fix permissions function too, no dice.
    Wish I still had fastboot access, that seems to be an easy way around the permissions issue from what I've googled.
    Next will try 'make otapackage' and see if it installs that way. Ugh.
    found a better variant, make updatepackage. no, that just makes a userdata zip. bah humbug. back to the dangerous otapackage... either gotta fix build/core/Makefile to not include recovery or just remember to be careful and remove the recovery from the zip before flashing.
    otapackage was what I originally wiped out my first OV with, stupid install-recovery.sh
    JerryScript likes this.
    11-19-2011 09:07 PM
  22. jdcnosse'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.
    11-19-2011 09:58 PM
  23. bigsupersquid's Avatar
    I got weird build errors in odd places like that before when I synced at a bad time... I think CM7 stuff was being uploaded as I was downloading. A couple syncs later, the errors went away on their own...
    jdcnosse likes this.
    11-19-2011 10:16 PM
  24. jdcnosse's Avatar
    I got weird build errors in odd places like that before when I synced at a bad time... I think CM7 stuff was being uploaded as I was downloading. A couple syncs later, the errors went away on their own...
    That's probably it, because I'm also getting errors in the lockscreen that I didn't get before...
    11-19-2011 11:15 PM
  25. JerryScript'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.
    bigsupersquid likes this.
    11-20-2011 07:39 AM
1,060 ... 910111213 ...
LINK TO POST COPIED TO CLIPBOARD