Building code for nexus 5

sagar.pradhan

I'm following ubports instructions:

mkdir phablet && cd phablet/
repo init -u https://github.com/ubports/android -b ubp-5.1

repo sync -j10

. build/envsetup.sh

I will try it again, may be I may have missed something. Thank you.

apple.muncy

@sagar.pradhan,
OK, so i'm trying to do this also,

It seems to me that when I do:

repo sync -j10

it does not complete successfully with a great many fetch errors,

And no build/envsetup.sh

I'm thinking these instructions have gone stale.

apple.muncy

@sagar.pradhan

When I do a:
:~/phablet$ repo status

I get a large number of:
project abi/cpp/
missing (run "repo sync")

project bionic/
missing (run "repo sync")

project device/moto/shamu/
missing (run "repo sync")
...

So I'm running "repo sync -f"
To force repo to continue even after a failure then I'll look for a pattern in the failures. Looks like it will take all day.

sagar.pradhan

@apple-muncy I tried it again several times but no success. Looks like indeed those instructions have gone stale.

@mariogrip - can you help us out here?

apple.muncy

@sagar.pradhan
I'm not giving up yet.
I've updated the version of repo I'm using and removed all that was in ~/phablet
Now in the middle of a fresh sync.

apple.muncy

@sagar.pradhan
After trying the Ubuntu version "phablet-dev-bootstrap" and having it fall over I dug around and found this bug that claims it's the severs that become unresponsive. It might be why repo sync is failing too.

https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1610650

apple.muncy

@sagar.pradhan
So I've caught up to you, at least as far as you have reported.
I get the same output as you from lunch, well, I think you must have truncated it but no mind.

By the way, did you have to do an extra install to get lunch? Or did I just overlook where in the instructions it got installed?

So if something is stale about these instructions it would be the "-b udp-5.1"

I must look more at the commit history of https://github.com/ubports/android

sagar.pradhan

@apple-muncy : I think "lunch" is part of code downloaded from repo. Executing build/envsetup.sh adds it to the path.

sagar.pradhan

@apple-muncy : I'm planning on trying master branch today. Will let you know how it goes. Did you try it yet?

sagar.pradhan

@apple-muncy : You are right about -b udp-5.1. Looks like all the rc builds are from branch 4.4.2 for Hammerhead.

I should try below command:

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

Will let you know how it goes.

apple.muncy

@sagar.pradhan
No, that is hopelessly messed up. And/or requires a source tree, perhaps as done per https://developer.ubuntu.com/en/phone/devices/porting-new-device/

Notice the fetch line in default.xml
...
<remote name="phablet"
fetch="../../../"
review="code-review.phablet.ubuntu.com" />
....

So:
Time out : ) @mariogrip When you get a chance, how to build stable for Nexus 5, please?

apple.muncy

@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

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

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

apple.muncy

@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

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

apple.muncy

@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

@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

@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

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

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