Hey Armen.
The 'hamachi' build, in my experience, needs more supervision than
merely relying on the build scripts can provide. The build can,
depending on the compilation platform, silently skip fundamental steps.
The probability of getting broken images is high and the build scripts
do not do full backups before starting. So you will be failing a lot.
Rather than modernize the build system, Mozilla has decided to simply
abandon support for the phone. That's too bad because the phone is
actually a pretty good development platform, with a lot of users in this
country and revealing a host of issues related to low budget hardware. I
upgraded to Firefox 1.2 so that I could work with the Firefox Browser
App Manager while staying as close to the OS being sold on the street in
this country. However, I have also succeeded in getting a partially
functional boots of 1.3 and 1.4. I have never tried building more recent
builds so others will have to communicate their experiences with those.
To get good help for the collective wisdom on this list, you'll need to
provide a bit more detail on what you are doing, notably the compilation
OS on which you are working and the build you are attempting. It sounds
like you are trying to build the default, master branch of Firefox OS,
which I think is now version 2.1. Also, I presume, because you don't
say, that you are on Gnu/Linux, say Ubuntu 14.04, rather than Osx/Darwin.
First, if you need to recover from a broken build (because you don't
have backups of the original images) then you might want a source of the
four cannoical *droid images:
boot.img
system.img
userdata.img
recovery.img
although flashing the recovery image is only needed if you want a better
image than is provided by default. Also, I recommend you test the
boot.img files by sideloading them first to see if they boot: that is
boot into fastboot mode and then boot the image without flashing it: a
good kernel will get you to the second stage splash image.
The best source of pre-built images that I have worked with was:
http://elsimpicuitico.wordpress.com/firefoxos/
but note that even there I ended up having to work systematically
through the images to find one set that would work with all functions:
booting kernel, functioning desktop, working cellular and gps. So you
might have to download a few images to get things working.
Alternatively, there appear to be images, possibly more recent, here:
http://update.boot2gecko.org/hamachi/
but I have no experience with those. You'll need to learn to use the two
canonical *droid tools 'adb' and 'fastboot'.
I have found four different reactions to the images: the phone won't
boot (bad boot.img), the phone will boot but the desktop won't appear
(bad combo of gonk, gecko, gaia), the phone will boot and get to the
desktop but radio stuff won't work, and the whole thing works.
Getting a good boot.img was consistently the hardest thing for me. The
boot.img needs to be a good build, be able to accept the binary blobs
(which I suspect but am not sure are part of the system.img rather than
part of the root disk in the boot.img), and be compatible with the gecko
build in the system.img. This seems to be the hardest to get right.
Beware that, if you are on Mac OS X, the build system will download the
whole kernel source and then silently not build the kernel itself! Also,
I don't really know when the build scripts go all the way to building
image (.img) files and when they side step and flash the new filesystem
directly on the running phone using 'adb'. It's all silently mysterious.
Oh, and the Gonk layer seems to be evolving incompatibly between Firefox
OS versions with no warning or info that I have been able to find.
The builds of gecko will mostly let you know when they don't work and
Gaia always 'builds' mostly because it does not really 'build' but just
assembles the apps.
I can't help you with newer versions of Firefox OS for Hamachi since I
have not built them (working with 1.3 and 1.4 took too much time).
Version 1.2 works with the App Manager and is close to what the devices
come with originally so provides the best 'real world' development
platform if you want to write apps for users buying that phone.
Anyhow, keep at it, there is lots to learn. Google, in its infinite
wisdom, pulled its documentation on Android so there is little good
documentation of how things work. If you want to learn the build system,
you will have to learn the repo tool (which gets the sources and allows
developers to upload patches to several projects at once) and then the
android NDK Makefile build system, the best explanation for which is in
the O'Reilly book "Embedded Android" by Karim Yaghmour.
Good luck with all this,
~adrian
On 6/18/14, 6:47 PM, Armen Zambrano G. wrote:
Hello,
I've tried to update my Hamachi for the first time (I've updated a Keon
many times before), however, the phone starts with a screen showing me
"Index of app://communications.gaiamobile.org" web page (I think).
The folders and files have dates from 1969 and 1980.
The instructions I followed were to:
1) clone B2G
2) ./config.sh hamachi
3) ./repo sync -d
4) ./build.sh
5) ./flash.sh
Is there anything I should have done differently?
Thanks,
Armen
PS = I've been following steps from
https://developer.mozilla.org/en-US/Firefox_OS/Building
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
