Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Building code for nexus 5

    Porting
    nexus 5
    2
    26
    8291
    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.
    • S
      sagar.pradhan last edited by

      @apple-muncy
      Not sure about that. Today I received r233 rc-proposed update and although device image part is 20160603 but Ubuntu image part is 20161005.
      So probably Ubuntu image part matters!

      On removing double entries for strace in default.xml and doing below:

      repo init -u https://github.com/ubports/android -b 4.4.2
      repo sync -j10 -f

      I'm getting all sorts of errors saying repo not found:
      fatal: repository 'https://github.com/aosp/platform/external/safe-iop/' not found
      fatal: repository 'https://github.com/aosp/platform/external/libppp/' not found
      fatal: repository 'https://github.com/aosp/platform/prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/' not found
      fatal: repository 'https://github.com/aosp/device/generic/common/' not found
      fatal: repository 'https://github.com/aosp/platform/system/security/' not found
      fatal: repository 'https://github.com/aosp/platform/hardware/qcom/camera/' not found
      fatal: repository 'https://github.com/aosp/device/generic/armv7-a-neon/' not found
      fatal: repository 'https://github.com/aosp/platform/external/e2fsprogs/' not found
      fatal: repository 'https://github.com/aosp/platform/external/webrtc/' not found
      fatal: repository 'https://github.com/aosp/platform/build/' not found

      Did you get these too? Can you list exact steps on what you did?

      A 2 Replies Last reply Reply Quote 0
      • A
        apple.muncy @sagar.pradhan last edited by

        @sagar.pradhan
        Yes, but I used the instructions found on https://developer.ubuntu.com/en/phone/devices/porting-new-device/

        and the command
        $phablet-dev-bootstrap phablet

        that is a python script coded with:
        ....
        repo = {
        'aosp':
        'https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git',
        }

        repo_branch = 'phablet-4.4.2_r1'
        valid_vendors = ('mako', 'flo', 'deb', 'manta', 'hammerhead', 'generic')
        vendor_blobs = 'lp:~phablet-team/phablet-tools/aosp-vendor-4.4.2'
        ..

        It pulls down a manifest.xml all most exactly like the one from
        https://github.com/ubports/android -b 4.4.2

        But of course it knows nothing about ubports.

        So at this point I'm wondering what code is generating the systems we install from http://system-image.ubports.com ? Without some information from Marius, I think we would be recreating the wheel.

        So I'm going to sleep on it : )

        1 Reply Last reply Reply Quote 0
        • A
          apple.muncy last edited by

          Later today I will do a fork of GitHub.com/ubports/android to my GitHub account and add what I think needs to be in it to build for hammerhead.

          I see there is already moto.shamu there. I'll try building that since I have a Nexus 6.

          1 Reply Last reply Reply Quote 0
          • A
            apple.muncy @sagar.pradhan last edited by

            @sagar.pradhan
            So I have applied a commit to https://github.com/applemuncy/android that is my first approximation on how to build hammerhead.

            As of now it fails to build.

            1 Reply Last reply Reply Quote 0
            • A
              apple.muncy last edited by

              Today was kind of a milestone. The first time building other peoples code contributions and ideas, scopes displays correctly.

              In anticipation of helping in the porting of FP2 I did a fresh repo with standard Ubports instructions
              Plus the a local manifest as shown here: instructuons

              But more specifically a local default.xml manifest for N5

              ~/phablet/.repo/local_manifests/hammerhead.xml

              <manifest>
              
              <!-- Lge -->
                <project path="device/lge/hammerhead" name="android_device_lge_hammerhead"   remote="ubp" />
                <project path="kernel/lge/hammerhead" name="android_kernel_lge_hammerhead"   remote="ubp" />
              
                <!--  Comment this next line out if it is included somewhere else. -->
                <project path="device/qcom/common" name="android_device_qcom_common" remote="cm" />
               <!--   -->
              
                <project path="vendor/lge"   name="proprietary_vendor_lge" remote="them" />
              
              </manifest>
              

              Then after make finishes successfully..... oops.
              There will be an error about missing make rules for live wall paper.
              Try running this script :

              ~/phablet/device/lge/hammerhead/setup-makefiles.sh
              

              or edit directly file

              ~/phablet/vender/lge/hammerhead/hammerhead_vendor.mk
              

              to:

              # Copyright (C) 2014 The CyanogenMod Project
              #
              # Licensed under the Apache License, Version 2.0 (the "License");
              # you may not use this file except in compliance with the License.
              # You may obtain a copy of the License at
              #
              #      http://www.apache.org/licenses/LICENSE-2.0
              #
              # Unless required by applicable law or agreed to in writing, software
              # distributed under the License is distributed on an "AS IS" BASIS,
              # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
              # See the License for the specific language governing permissions and
              # limitations under the License.
              
              # This file is generated by device/lge/hammerhead/setup-makefiles.sh
              
              # Live wallpaper packages
              PRODUCT_PACKAGES := \
              #    LiveWallpapers \
              #    LiveWallpapersPicker \
              #    MagicSmokeWallpapers \
              #    VisualizationWallpapers \
                  librs_jni
              
              # Publish that we support the live wallpaper feature.
              #PRODUCT_COPY_FILES := \
              #    packages/wallpapers/LivePicker/android.software.live_wallpaper.xml:/system/etc/permissions/android.software.live_wallpaper.xml
              
              # Pick up overlay for features that depend on non-open-source files
              DEVICE_PACKAGE_OVERLAYS := vendor/lge/hammerhead/overlay
              
              # Apps
              PRODUCT_PACKAGES += \
                  qcrilmsgtunnel \
                  shutdownlistener \
                  TimeService \
                  UpdateSetting
              
              $(call inherit-product, vendor/lge/hammerhead/hammerhead-vendor-blobs.mk)
              

              Then grab a rootfs

              I hacked my version of rootstock-toouch-install to handle installing all to the phone.

              1 Reply Last reply Reply Quote 0
              • A
                apple.muncy last edited by

                So I'm using this as a notebook to keep track and also share progress.

                Today I tried out the rootfs of 9-20-2016 has the display corruption.
                So backing off to 7-28-2016 works fine as far as the display goes.

                Now to do some testing on it I need to set the rootfs writable to be able to install more packages but I struggle to remember the utility to do it with.

                To be continued....

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