On Thursday, 27 November 2014 22:45:19 UTC+11, Christof Meerwald wrote: > On Wed, 26 Nov 2014 14:17:06 -0800 (PST), an wrote: > > On Wednesday, November 26, 2014 11:53:24 PM UTC+2, Christof Meerwald wrote: > >> On Sun, 23 Nov 2014 23:30:12 -0800 (PST), an wrote: > >> > Also check out this build by KonstaT: > >> > http://www.modaco.com/topic/373261-devrom511-caf-firefox-os-b2g-for-zte-open-c-kis-3/ > >> > I don't have the phone just yet but that's the update I will use when it > >> > comes. > >> Looks interesting, although I still don't fully understand what this > >> exactly is... > > It uses KK as base Android instead of JB and a more stable b2g branch (from > > what he says). KonstaT is still actively maintaining his work afaict. > > Ok, would that then also allow me to shallow flash Gecko and Gaia from > the nightly flame-kk builds or is that base system still not > compatible with the flame-kk one? > >
I'm currently running a horrifying mix of setups: gonk: original ZTE Open C Firefox gecko: http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-aurora-flame/b2g-34.0a2.en-US.android-arm.tar.gz gaia: http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g34_v2_1-flame-kk/gaia.zip (from a few days ago) That is, I flashed a flame-kk gaia build over the latest flame gecko build. Seems to be working well. Let me know if you have any success shallow-flashing a recent gecko or gaia over the CAF build. James. PS I originally followed the gaia instructions on the ZTE Open C page. Unfortunately, make reset-gaia wiped out my existing gaia before determining whether it could successfully build it (it couldn't), which left my phone unable to boot. Had to get into the boot-loader and adb push a valid gaia manually. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
