How about, for the sake of sanity, rename any upgrade path for this device to "zte_open"? Everything else is just technical details, really. I mean zte open has been a total failure from the user/developer perspective maybe it's time for some sanity. This is no criticism towards someone in particular but having the docs specify that if you want to build for zte open you must choose inari and now having some guy explain that the builds for inari (which actually work on the phone) have some "defect" because the "real" code name is ikura either make him look like an idiot or Mozilla, and I tend to believe it's not him.
Comments like "I know it's confusing, but that's what it is" while they may work within a corporate environment don't go particularly well with the real world, where people actually pay a really high price for a really low end device just because it's labeled a "developer/open" device which it is not. So, the phone is garbage (as hardware), the kernel&all is proprietary and the OS building components are not exactly sure because we deal with conflicting "code" names. Call me I'm insane... On Friday, January 3, 2014 7:55:17 PM UTC+2, Gabriele Svelto wrote: > Hi Daniel, > > > > > I'm still looking for some documentation on how to create update.zip > > file. > > > Has anyone been able to do that? > > > > besides the bug mentioned by Alexandre we have the existing > > functionality documented here: > > > > https://wiki.mozilla.org/B2G/Updating > > > > Gabriele _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
