> > > 2) Is Google still contributing back to the free software version of > > > Android, or have Google's versions drifted to far from the free software > > > base? > > > > Google has been releasing the free versions of Android through AOSP > > based on their internal code, not the other way round. As long as Google > > keeps doing it, a free recent version of Android exists. Note that they > > stopped maintaining useful utilities as those get replaced by their > > proprietary counterparts. > > Luckily the offering via F-Droid is decent, as I've been able to replace > most applications on my own Android phones with free software.
This is true, but there are still fundamental system apps that are missing, such as the a Gallery app that would have a modern look but wouldn't rely on unimplemented graphics acceleration calls. > Is it feasible for Replicant (or any project) to keep up with Android > developments if no modifications can be pushed upstream? Well, it's far from an ideal situation, but what I do is that I basically take a snaphsot of CyanogenMod at one point (from a stable release as much as possible) and add Replicant changes upon it. The process has to be started over for each version, sadly. > > > 3) How would you compare Ubuntu Touch with Replicant OS? I consider the > > > plain GNU/Linux kernel in Ubuntu Touch to be a benefit as it prevents > > > segregation of development efforts. Replicant seems to be more free, > > > although I'm weary about driver blobs. > > > > Ubuntu Touch uses all the same proprietary blobs as CyanogenMod, despite > > being based on GNU/Linux. This is also true for FirefoxOS (minus the > > GNU/Linux part). On the other hand, Replicant is a fully free system. > > But would these OS's be able to take the free drivers from Replicant to > offer a free implementation for Replicant-supported devices? This is true, they could indeed do that, but they have apparently shown no intention of doing so. As far as I know, they're fine with the blobs on a moral level. It looks like they have spent a lot of effort in making the blobs integrate well with their systems, too. > Considering the number of 'missing' and 'missing without non-free > firmwares' regarding device support, usability can be questioned. Then > again I'd first have to experience the current state of development to > make and judgment. All supported devices should be usable for daily use, meaning that the basic features are there. Of course, some features are missing in the free world. For considerations about that, see: http://www.replicant.us/about.php#missing-hardware-features http://www.replicant.us/about.php#shipping-proprietary-components > > > 4) I guess getting drivers to work would be most important to forward > > > free software on devices. But as has happend with the Vivaldi Tablet > > > (Spark KDE Tablet) I'm weary that after the reverse-engineering efforts, > > > upstream electronic change requiring development to start all over > > > again. Is there a strategic guide for selecting targets based on say > > > manufacturers or architectures? (I might be able to use my electrical > > > engineering background for reverse-engineering if I find the time, but > > > I'd rather contribute for the long-run). > > > > This is especially something to take in account when manufacturing a > > device. Currently, many chips good chips have been available in large > > quantities for a long time and widely-spread devices are never too hard > > to find. > > > > Of course, we should avoid working on chips that have a very limited > > time span, but we haven't had any problem with that before since > > Replicant mostly supports popular mainstream devices that were produced > > in millions. > > Is there say a list of currently available (cellphone) chips offering > being supportive of free software? I'm working on something like this, I'll be ready to announce it soon-ish (weeks/months from now, probably not years). > I get the sense that despite best intentions, the Fairphone project is > in the dark regarding hardware issues related to free software. I cannot say this is true. We have been in touch with them ever since the very beginning and they didn't seriously take our suggestions in account. I have explicitly told them what platforms are good and what traps to avoid. In the end, they still produced an average Android device, using a platform we clearly told them is bad for freedom. I suppose they just don't care enough about software freedom to really do something about it. Of course, the fact that they rely on a third party designer for creating their devices doesn't help the situation and kinda ties their hands. -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security. Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Replicant mailing list Replicant@lists.osuosl.org http://lists.osuosl.org/mailman/listinfo/replicant
