UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Building an image

    Scheduled Pinned Locked Moved Support
    6 Posts 3 Posters 502 Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • W Offline
        wdehoog
        last edited by

        I am trying to fix some issues for my opo and therefore need to build an image.
        There are two documented methods I am aware of:

        • http://docs.ubports.com/en/latest/porting/ubp-5.1.html
        • https://github.com/ubports/device-builds

        For me both do not work. The 'device-builds' one does not work at all. Building fails with various errors.

        The 'docs' one builds and I can flash the boot.img and update the system.img and the phone boots etc.. However the camera stops working.

        While cheking why the camera stopped working I noticed the system.img installed by the UBports Installer contains different files the the one I have built. So it seems there is yet another way to build an image.

        So is there another 'howto' for building an image? Or do the before mentioned descriptions need a little bit of tweeking?

        LakotaubpL 1 Reply Last reply Reply Quote 1
        • LakotaubpL Offline
          Lakotaubp @wdehoog
          last edited by

          @wdehoog Just moved as it's more of a fit in support rather than porting. Thanks.

          1 Reply Last reply Reply Quote 0
          • flohackF Offline
            flohack
            last edited by

            You need to first checkout an Android tree from this xml: https://github.com/ubports/android - there are explanations on the internet how to do this.
            Then after that has finished, you move https://github.com/ubports/device-builds/blob/master/devices.xml into the .repo/local_manifests folder and repo sync again.
            Then hopefully you can call

            . build/envsetup
            

            and finally

            lunch
            

            which will present you with a menu for all devices from previous xml, OPO should be included.
            Select bacon_userdebug, and try this build.
            DO NOT USE HALIUM DOCS! Current OPO is on classic port.

            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

            1 Reply Last reply Reply Quote 0
            • W Offline
              wdehoog
              last edited by

              @Flohack thanks.

              I followed http://docs.ubports.com/en/latest/porting/ubp-5.1.html so ended up with the same settings as the files you point me to.
              Still I think this is not what is currently being build on the ubports server and installed by the official installer.

              For example branch ubp-5.1 of http://github.com/ubports/android_device_oneplus_bacon-1 has init_wlan_bt.sh in '/' of the android rootfs while on the installer image it is located in '/etc'. As I cannot find any branch that contains this file in '/etc' the ubports build server probably uses another repo. Which one?

              In my locally built /system/lib/hw/ there is camera.vendor.bacon.so and in the installer one there is camera.msm8974.so. The other lib files are present but seem to differ in contents.
              The files you point to use The Muppets cm-12.1 which contains camera.vendor.bacon.so not the camera.msm8974.so.
              So the ubports build server probably uses another repo or branch. Which one?

              To be able to continue fixing issues I now have to update the installers system.img (mount loop etc.) and reflash that.

              1 Reply Last reply Reply Quote 0
              • flohackF Offline
                flohack
                last edited by

                Can you see your commit https://github.com/ubports/android_device_oneplus_bacon-1/commit/00b3ab188126980340dafcbd5c084525758232bb in todays nightly? Then it must be that branch thats being used πŸ˜‰

                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                W 1 Reply Last reply Reply Quote 0
                • W Offline
                  wdehoog @flohack
                  last edited by

                  @Flohack thanks a lot for helping me open my eyes.

                  I still don't understand the difference in vendor files but android_device_oneplus_bacon-1 seems indeed to be used for building the images.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post