Comment 28 for bug 1532899

I took a stab at reproducing the fix Pat mentioned above on my Aquarius E5. Long story short, it didn't work for me. Listing the steps below. If anyone sees anything obviously amiss in my fix-attempt, please let me know.

Steps I Took:
1.) Enable developer mode on my phone.
2.) Download nuntium from the github repo located here onto my laptop: https://github.com/ubuntu-phonedations/nuntium I noticed there was also a bzr repo located here (bzr branch lp:nuntium), but the code there hadn't been touched since 2014. Not sure if I chose the right one.
3.) Install "go version go1.6.2 linux/amd64" on my desktop.
4.) Use uname -a to check the architecture on my phone (it's reported as armv7l)
4.) cd nuntium/cmd/nuntium.
5.) Cross-compile nuntium on my desktop, for my phone: GOOS=linux GOARCH=arm go build. The architecture I specified with go build here isn't exactly the same as what was specified by uname above (arm vs armv7l). Not sure if that matters.
6.) Use adb shell, and sudo mount -o remount,rw / so that I can manipulate files on the phone filesystem.
7.) On the phone, move the existing nuntium binary in /usr/bin to /usr/bin/nuntium.bak
8.) Copy in the newly compiled nuntium (nuntium/cmd/nuntium/nuntium) from my desktop to my phone (/usr/bin/nuntium).
9.) Check that permissions and ownership matches up between the new and the old nuntium.
10.) Exit adb, turn my phone off and on again.
11.) Get some friends to start a group message. Still see missing/dropped messages.

Are there any other binaries I should be copying over? Did I grab the right project source? Are there any config files I needed to have tweaked before building with golang 1.6.2?

Going to try looking into the logs, but would love a sanity check on my fix-attempt in the meantime if anyone can set me straight.