Le 22/04/2014 06:12, Joseph P Reilly a écrit : > > > Preface: Personally I think ZTE are to be applauded for their efforts > with firefox os. Yes, they have > had underwhelming support for the Open but just the fact that they > decided to gamble on firefox os is > awesome in my book. You've got to figure that the market for the Open > is small so I wouldn't expect > quick updates from ZTE anyway (they are probably not making much, if > any money on firefox os right now). > Also ZTE are the only people that have sold a firefox phone in the USA > in volume, so again I applaud them. > I'm not an emerging market but I am an early adopter who has been > ignored by LG, Alcatel, etc and geeksphone > doesn't count since they put out such a limited run of phones and > their only current firefox os phone is Atom > powered (no thank you geeksphone). I paid $70 USD for my unit (2nd > batch ZTE sold on ebay) and I think even > if it doesn't get a stable update beyond 1.3 it was well worth the > money to be able to tinker around with firefox os. > We can probably build the franken-roms you asked about if we don't get > official updates anyway.
Thanks for this positivity, this is good to read ! And thanks for sharing too ! Some comments below: > > My process: > 0. flash the official ZTE 1.1 update via SD card and enable remote > debugging. > > 1. Set up the build environment following the MDN documents. > https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites > > > 2. Set up adb/fastboot by putting them in /usr/bin and modifying a > udev rule (it also talks about > this step at the end of the MDN docs as I'm sure you've seen). I usually just do a symbolic link in my ~/bin, which is in my path. > 3. Fetch the code and configure the build with my device (attach > device). I however use Mike Rowehl's site > about 1.2 as a guide to configure the build modifying his command to > "BRANCH=v1.3 VARIANT=user ./config.sh inari". I think you don't need VARIANT= here, it's needed for building only. But I'm not sure because I put it in .userconfig so it's probably always here. > > 4. I built 1.3 again using Mikes blog as a guide modifying his > commands to "BRANCH=v1.3 VARIANT=user ./build.sh" You can put the VARIANT part in a file .userconfig. The BRANCH part is unnecessary because it's been configured by config.sh. > > > On 04/21/2014 06:19 PM, Roland Lindner wrote: >> first of all, let me say thank you, this group is awesome! >> i nuked my VM and started from scratch, checking and rechecking every >> step. >> guess what, my machine is currently building v1.3 for inari..... >> looks good, previously it failed pretty early in the process. >> i still get a huge amount of warnings, but it seems there are no errors. >> good so far. >> >> i hope i can flash and use 1.3 on the ZTE Open now. >> i also hope we (that is the ZTE Open owners) will be able to upgrade >> to 2.0 when it comes around, but from what i understood that will >> need some involvement from ZTE to make this happen? >> >> since modules can be built separately - does that mean one can build >> a "Frankenstein" FXOS? (eg- i'd like to have a newer browser module >> for example) >> that would be an ok interim solution if we cannot build newer >> versions if it works... >> >> thanks a bunch and i would love to see some commitment towards the >> ZTE Open going forward. >> >> cheers Roland >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
