LG devices had some QC configuration files after we submitted some bugs. Same with the other devices as they were configured by the manufacturer.
Flame and Aries are not configured by manufacturers. They have to be configured by us or the end user. On Tue, Jan 12, 2016 at 12:10 PM, Adam Farden <[email protected]> wrote: > I've used timekeep on LG devices and many more, it works very well. > > On Tue, Jan 12, 2016 at 6:32 PM, Alexandre Lissy <[email protected]> > wrote: > >> Le 12/01/2016 18:02, [email protected] a écrit : >> > Le mardi 12 janvier 2016 10:36:54 UTC+1, Julien Wajsberg a écrit : >> >> >> >> I think we can define Gonk in a "negative" way: Gonk is basically >> >> everything that's not Gecko and Gaia ;) >> > >> > So, where are Gecko/Gaia files located? Just kidding ;-) >> > >> >> Note: the problem is not only that it's closed source, but also that >> >> we're not allowed to redistribute. Only the right owner has the right >> to >> >> redistibute these bits. This can be different for other devices too. >> (So >> >> far, we distribute full images for some Nexus devices, see >> >> https://firefoxos.mozilla.community/devices/). >> > >> > Alexandre (in a previous post) and you made it clear to me. In fact, I >> didn't get the "not redistributed" part right. To me, "not redistributed" >> was meaning "not redistributed at all". Now Alexandre and you made it clear >> that it was to be understood as "not redistributed by Mozilla". Hence the >> confusion. Thank you guys for clarifying this point. >> > >> >> Good question :D >> >> >> >> I'd say it depends on the blobs. (you're happy now, are you ?) >> > >> > Yep. Always happy ;-) >> > >> >> For example I remember we had (have ?) issues with bluetooth or the GPS >> >> functionality or keeping the time between reboots (yes, this also uses >> a >> >> binary blob). >> > >> > That's interesting. By chance, do you remember how this problem was >> solved? >> > >> > Indeed, I've just upgraded my KK-based Firefox OS 2.0 Fire E device >> (using some kind of shallow flash) to Firefox OS 2.1 using Flame KK >> device's v2.1 Gecko/Gaia components from Mozilla FTP [1]. And now, my Fire >> E device is also failing to keep time between reboots or when switched back >> on. But I didn't update any Gonk file (I promise ;-)). Furthermore, both >> Fire E and Flame device's KK base images rely upon the same Android >> 4.4.2_r2 KVT49L build. So, I don't think the problem comes from Gonk in the >> end. It seems to solely come from updated file(s) in Gecko/Gaia. Unless >> Flame device is also failing to keep time ;-) >> >> That's probably because the QC time XPCOM is missing from your device. >> >> That should be something within /system/b2g/distribution/bundles/ >> >> You might try to push that back to your device but there is a risk it >> will not work because it's not compatible with your new Gecko. >> >> You can try to make use of timekeep that we are using on Sony devices >> (and that was brought by Sony Open Devices project). >> >> > >> > Émeric >> > >> > >> > [1] >> http://ftp.mozilla.org/pub/b2g/nightly/2015/07/2015-07-24-00-12-07-mozilla-b2g34_v2_1-flame-kk/ >> > _______________________________________________ >> > dev-fxos mailing list >> > [email protected] >> > https://lists.mozilla.org/listinfo/dev-fxos >> > >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-fxos >> > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
