Building code for nexus 5

sagar.pradhan

Hello,

I'm new to Ubuntu touch development. I am trying to build code for Nexus 5/Hammerhead.

The lunch command gives below options:

lunch

You're building on Linux

Lunch menu... pick a combo:

aosp_arm64-eng 14. cm_castor-userdebug 27. cm_i9500-userdebug 40. cm_sirius-userdebug 53. cm_trltexx-userdebug
aosp_arm-eng 15. cm_castor_windy-userdebug 28. cm_jactivelte-userdebug 41. cm_superior-userdebug 54. cm_v500-userdebug
aosp_mips64-eng 16. cm_dlx-userdebug 29. cm_jem-userdebug 42. cm_t6spr-userdebug 55. cm_ville-userdebug
aosp_mips-eng 17. cm_e975-userdebug 30. cm_ls980-userdebug 43. cm_t6vzw-userdebug 56. cm_xt907-userdebug
aosp_shamu-eng 18. cm_e980-userdebug 31. cm_lt03wifi-userdebug 44. cm_taoshan-userdebug 57. cm_xt925-userdebug
aosp_shamu-user 19. cm_evita-userdebug 32. cm_m7vzw-userdebug 45. cm_tate-userdebug 58. cm_xt926-userdebug
aosp_shamu-userdebug 20. cm_g620_a2-userdebug 33. cm_mb886-userdebug 46. cm_tf300t-userdebug 59. cm_z3c-userdebug
aosp_x86_64-eng 21. cm_grouper-userdebug 34. cm_obake-userdebug 47. cm_tf701t-userdebug 60. cm_z3dual-userdebug
aosp_x86-eng 22. cm_hltespr-userdebug 35. cm_picassowifi-userdebug 48. cm_tilapia-userdebug 61. cm_z3-userdebug
cm_amami-userdebug 23. cm_hltetmo-userdebug 36. cm_rendang-userdebug 49. cm_togari_gpe-userdebug
cm_bacon-eng 24. cm_hlte-userdebug 37. cm_s3ve3g-userdebug 50. cm_togari-userdebug
cm_bacon-user 25. cm_honami-userdebug 38. cm_scorpion-userdebug 51. cm_trltespr-userdebug
cm_bacon-userdebug 26. cm_i777-userdebug 39. cm_scorpion_windy-userdebug 52. cm_trltetmo-userdebug

Which one of these to choose? Is this correct way to build code for nexus 5?

I have used instructions from Wiki for ubports.

Regards,
Sagar

apple.muncy

Number 2 because Nexus 5 has ARM v7 32bit CPU.

sagar.pradhan

@apple.muncy , Thank you for your reply.

From the description, option 2 looks like a generic ARM32 build. Will it have required BSP for hammerhead/Nexus 5?

apple.muncy

@sagar.pradhan
So I've been wondering why the choice presented do not match the build description I find in my Nexus 5 ?

ro.build.description=aosp_hammerhead-userdebug 4.4.2 KOT49H eng.mariogrip.20160308.153133 test-keys

Are you fallowing ubports build set up instructions or from Ubuntu?

And by the way, I have NOT set up to do builds myself.

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 ?