Building code for nexus 5

apple.muncy · 4 Oct 2016, 09:56

@sagar.pradhan
OK, maybe not hopeless.

I'll review posts from 7 months ago and maybe later today I'll see what happens with "phablet-dev-bootstrap phablet " on a fast internet connection.

apple.muncy · 4 Oct 2016, 11:12

@sagar.pradhan
This is a bit like archeology. Digging up the past.

https://plus.google.com/107365438415018184209/posts/ZMdZEGi7sAf

apple.muncy · 5 Oct 2016, 13:56

@sagar.pradhan
I have been able to download and compiled with this after editing out the one of the double entries for strace: :

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

I'm not going to push it the the phone. It just pulls from Ubuntu/touch.

Above you said "Looks like all the rc builds are from branch 4.4.2 for Hammerhead." Are you basing that statement on what is found in /android/system/build.prop or somewhere else?

sagar.pradhan · 6 Oct 2016, 00:43

The 4.4.2 finding was from software version information on rc-build flashed on my phone.

apple.muncy · 6 Oct 2016, 01:03

@sagar.pradhan
OK.

I just went though major trouble putting rc-proposed on my Nexus 5.

From the build.prop file:
...
ro.build.id=KOT49H
ro.build.display.id=aosp_hammerhead-userdebug 4.4.2 KOT49H eng.mariogrip.20160308.153133 test-keys
ro.build.version.incremental=eng.mariogrip.20160308.153133
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=ti. 08. mars 15:31:40 +0100 2016
ro.build.date.utc=1457447500
ro.build.type=userdebug
ro.build.user=mariogrip
ro.build.host=mariogirp-laptop
...

Is that telling me that no change since march ?

sagar.pradhan · 6 Oct 2016, 01:39

@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

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

apple.muncy · 6 Oct 2016, 03:08

@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 : )

apple.muncy · 6 Oct 2016, 12:50

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.

apple.muncy · 9 Oct 2016, 10:18

@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.

apple.muncy · 15 Dec 2016, 01:37

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.

apple.muncy · 15 Dec 2016, 23:29

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....