[Dev-Only] CM10 status


  1. mantera

    mantera Well-Known Member

    Question: Does this boot? Obviously, I can't test... I expect that nothing is probably working. But just wondering if it actually boots.
  2. BSydz

    BSydz Well-Known Member Developer

    When I got it to build it said bad file in CWM, I'm sure I can play around with the updater script but haven't messed with it yet. Just got it to build a few hours ago and got sidetracked. If you happen to know what is making it say the zip is bad let me know and I'll try it.
  3. mantera

    mantera Well-Known Member

    That doesn't sound right. I wonder if it's just a bad copy on your sd card. Try recopying?
  4. BSydz

    BSydz Well-Known Member Developer

    Well, after I messed with the updater script it then gave me the "expected so many arguments" error. So I'm gonna just copy the update binary and edit the script to match CM9, I'll post back after I try.
  5. BSydz

    BSydz Well-Known Member Developer

    Ok, so I threw the zip in android kitchen to see if it was the kernel and this is what I got. Editing the update binary just threw the same argument error.



    Code (Text):

    Working folder found
    od: boot.img: Permission denied

    Android 'magic' header not found at start of boot.img
    Checking if it exists elsewhere ...
    od: boot.img: Permission denied
    Warning: Android header not found in boot.img (unsupported format)

    od: boot.img: Permission denied
    Error: kernel offset (page size) not found in boot.img!

    Press Enter to continue
     
    EDIT: So I looked at CM10 and CM9 in 7zip and under Host OS, the boot.img in CM9 is FAT and CM10 is Unix, dunno if that helps.
  6. rukin5197

    rukin5197 Well-Known Member

    I got to about the end of the build and it threw some random error at me. Seeing how BSydz got a build it must be a bad sync or something. I'm going to nuke and try again.
  7. BSydz

    BSydz Well-Known Member Developer

    I had to edit some files to get it to build, it didn't just build. I think I had to comment out something in, I think, 2 files in libhwcomposer cause it is no where in the rest of the code, but I can't remember now what else I had to do. I am still fighting with the HDMI right now. I'm fighting with qcom_ui.h error: 'external_display_type' does not name a type, but that code is how it came and built, and is not even edited, I think it is because I added external_display, cause I was getting that error with external_display but managed to work it out. If I build with -j16 it is the only error I have left that I can see. When I hit an error, I do that to see if another error is gonna pop up, so I can fix it while I'm editing. Apparently, I have been at this too long tonight, I gotta go to bed. Just did -j24, 4 times, to see if there would be another error and that is the only error I am getting. Maybe I just need some rest. Good luck guys.
  8. BSydz

    BSydz Well-Known Member Developer

    OK so it was the last error, kinda. :D I pulled an all nighter and figured it out, I think I know how to fix this but just incase I figure I'll post it. This is with GPS and HDMI included. Now I am running into this:
    Code (Text):
    target SharedLib: libcamera_client (out/target/product/triumph/obj/SHARED_LIBRARIES/libcamera_client_intermediates/LINKED/libcamera_client.so)
    target Executable: hdmid (out/target/product/triumph/obj/EXECUTABLES/hdmid_intermediates/LINKED/hdmid)
    /home/phenom/CM10-3/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/triumph/obj/EXECUTABLES/hdmid_intermediates/HDMIDaemon.o: in function android::HDMIDaemon::setResolution(int):frameworks/av/cmds/hdmid/HDMIDaemon.cpp:552: error: undefined reference to 'android::SurfaceComposerClient::enableHDMIOutput(int)'
    /home/phenom/CM10-3/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/triumph/obj/EXECUTABLES/hdmid_intermediates/HDMIDaemon.o: in function android::HDMIDaemon::processFrameworkCommand():frameworks/av/cmds/hdmid/HDMIDaemon.cpp:583: error: undefined reference to 'android::SurfaceComposerClient::enableHDMIOutput(int)'
    /home/phenom/CM10-3/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/triumph/obj/EXECUTABLES/hdmid_intermediates/HDMIDaemon.o: in function android::HDMIDaemon::processFrameworkCommand():frameworks/av/cmds/hdmid/HDMIDaemon.cpp:590: error: undefined reference to 'android::SurfaceComposerClient::setActionSafeWidthRatio(float)'
    /home/phenom/CM10-3/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/triumph/obj/EXECUTABLES/hdmid_intermediates/HDMIDaemon.o: in function android::HDMIDaemon::processFrameworkCommand():frameworks/av/cmds/hdmid/HDMIDaemon.cpp:596: error: undefined reference to 'android::SurfaceComposerClient::setActionSafeHeightRatio(float)'
    collect2: ld returned 1 exit status
    make: *** [out/target/product/triumph/obj/EXECUTABLES/hdmid_intermediates/LINKED/hdmid] Error 1
    make: *** Waiting for unfinished jobs....
    target Executable: bootanimation (out/target/product/triumph/obj/EXECUTABLES/bootanimation_intermediates/LINKED/bootanimation)
    target SharedLib: libjni_mosaic (out/target/product/triumph/obj/SHARED_LIBRARIES/libjni_mosaic_intermediates/LINKED/libjni_mosaic.so)
    target SharedLib: libhwui (out/target/product/triumph/obj/SHARED_LIBRARIES/libhwui_intermediates/LINKED/libhwui.so)
     
  9. mantera

    mantera Well-Known Member

    It turns out the upstream updates broke the build. I updated a header file again. resync and it should build all the way now.
  10. rukin5197

    rukin5197 Well-Known Member

    Thanks, but I'm still stuck on hwcomposer. I got a prebuilt from jmztaylor, thank god. I'm going to throw that in the build.

    According to jmz, Steve broke all 7x30 devices by merging in all his commits because he just can.
  11. BSydz

    BSydz Well-Known Member Developer

    If it is the same error I had just use these edits. That is what I was talking about commenting out, in my post above.

    hardware/qcom/display/libhwcomposer/hwc.cpp
    Code (Text):

    //#ifndef NO_HW_VSYNC
    //        case HWC_EVENT_VSYNC:
    //            if(ioctl(m->framebuffer->fd, MSMFB_OVERLAY_VSYNC_CTRL, &value) < 0)
    //                ret = -errno;
    //
    //            if(ctx->mExtDisplay->getExternalDisplay()) {
    //                ret = ctx->mExtDisplay->enableHDMIVsync(value);
    //            }
    //           break;
    //#endif
    hardware/qcom/display/libhwcomposer/hwc_external.cpp
    Code (Text):
    //#ifndef NO_HW_VSYNC
    //        case HWC_EVENT_VSYNC:
    //            if(ioctl(m->framebuffer->fd, MSMFB_OVERLAY_VSYNC_CTRL, &value) < 0)
    //                ret = -errno;
    //
    //            if(ctx->mExtDisplay->getExternalDisplay()) {
    //                ret = ctx->mExtDisplay->enableHDMIVsync(value);
    //            }
    //           break;
    //#endif
  12. mantera

    mantera Well-Known Member

    Did you update the device files? I just did a build as is and it built fine.
    rukin5197 likes this.
  13. rukin5197

    rukin5197 Well-Known Member

    Well, build server is down and I don't have a backup build on my local so I'm not able to make new changes.

    Let's see when I get it back.

    @BSydz, I think that was fixed due to a recent commit by mantera defining the TARGET_NO_HW_VSYNC := true
  14. mantera

    mantera Well-Known Member

    Or if you prefer to do what BSydz says, just do this commit:

    https://github.com/mantera/android_...mmit/1f11dc63d4386d817523eab95ac391278996e159

    I reverted it in the commits that I pushed up because it's not needed but this should work also. However, I think we do have hardware vsync capability in the mt so that's why I didn't want to just disable it.
  15. rukin5197

    rukin5197 Well-Known Member

  16. mantera

    mantera Well-Known Member

    No, it was broken before that. My original fix was to set it to true so that the build would skip that section of code. Once I figured out which header file contained the define that was causing the hwcomposer variable to be undefined, I reverted it back out. I left it in there before pushing just so I had something to remind me that it was there.
  17. rukin5197

    rukin5197 Well-Known Member

    I accidentally said broken, I meant to either say fixed or it was broken before.

    EDIT: Got a build, thanks to mantera. Let's see how this baby goes.

    format() expects 5 args, got 4
    E:Error in /tmp/sideload/package.zip
    (Status 7)


    So obviously it's asking for 5 args, I don't necessarily know how to change the args. But I can change it after the zip.
  18. rukin5197

    rukin5197 Well-Known Member

    Okay, got it to flash, yet no go. It goes past M logo and stops at a black screen. Adb recognizes the device but shows no logcat. Just stops as soon as it starts.

    Seeing how there was no errors during the build, it's hard to stay what exactly the problem is, but it's going to be hard without a logcat.

    BUT, we are moving closer.
  19. jhonka232

    jhonka232 Well-Known Member

    Try a KMSG?
  20. rukin5197

    rukin5197 Well-Known Member

    You mean dmsg? But I guess I could grab a last_kmsg too. Thanks for the suggestion.
  21. jhonka232

    jhonka232 Well-Known Member

    Yeah lol either or...the more info the better I guess.

    But I meant adb shell cat /proc/kmsg
    rukin5197 likes this.
  22. mantera

    mantera Well-Known Member

    Ok, I think I got the zip file fixed. resync and try again and see if the new zip file will flash and boot.
  23. BSydz

    BSydz Well-Known Member Developer

    It flashes fine but it is a blank backlit screen. Which version kernel is this? Also Is this kernel in your git? Just want to try some stuff with the kernel, I want to try to build it with the system. I have an ICS kernel I was working on, maybe I can compare the 2 and see if anything is missing. Thanks for your work, you are a champ.

    EDIT: If it is the 2.3.65 kernel then I know why it wont boot.
  24. BSydz

    BSydz Well-Known Member Developer

    OK, so I finally managed to get it to build with HDMI and GPS enabled in the build. The device files just need to be updated and reworked. Still no boot but figured I'd put it out there.
    SumGuy and rukin5197 like this.
  25. rukin5197

    rukin5197 Well-Known Member

Loading...

Share This Page