Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062019-06-18T04:29:30ZReplicant
Redmine Replicant - Issue #1938 (New): Add the Offline Calendar app by defaulthttps://redmine.replicant.us/issues/19382019-06-18T04:29:30ZKurtis HannaKurtis@riseup.net
<p>By adding this app by default in the ROM we provide, users can create and use a calendar that isn't connected to an email account or "the cloud". <a class="external" href="https://f-droid.org/en/packages/org.sufficientlysecure.localcalendar/">https://f-droid.org/en/packages/org.sufficientlysecure.localcalendar/</a></p> Replicant - Feature #1844 (Resolved): Select libagl/llvmpipe per apphttps://redmine.replicant.us/issues/18442017-11-02T02:21:38ZJeremy Rand
<p>It would be useful to be able to select libagl or llvmpipe renderer on a per-app basis. This would allow apps that need llvmpipe to work, while apps that don't need llvmpipe can run faster with libagl.</p> Replicant - Issue #1786 (Feedback): Review the Chromium Webview build environmenthttps://redmine.replicant.us/issues/17862017-04-09T16:55:23ZWolfgang Wiedmeyerwreg@wiedmeyer.de
<p>In Android 6 (Marshmallow), the Webview is not built as part of an Android built. It is built in an Chromium build environment using the Chromium source code. The final apk file is committed to <a href="https://git.replicant.us/replicant/external_chromium-webview" class="external">external/chromium-webview</a>.</p>
<p>While this makes it possible to build the Webview based on the latest Chromium release including security fixes, the downside of this is that another huge and complex build environment has to be set up in order to build the Webview apk. The apk has to be copied and committed to the corresponding repo in the Replicant source tree. Then it gets automatically included in the build.</p>
<p>The build environment for the Chromium code needs to be thoroughly reviewed. All dependencies must be free software and the prebuilt binaries should be verifiable and the aim should be to build them from source, too. The build scripts download and set up a custom Android toolchain. Maybe this prebuilt toolchain can be replaced with the Replicant toolchain that is built from source.</p>
<p>I did an initial review. During the setup of the build environment, a license needs to be accepted that appears to be non-free. The license needs to be accepted because the build environment sets up the proprietary play services libraries. I verified that these non-free libraries are not used when building the Webview apk. The libraries were likely only included in the build environment setup because the same build environment is used for building Chrome which includes the libraries. I removed the scripts related to the play services in <a href="https://code.fossencdi.org/chromium_src.git/commit/?h=replicant-6.0&id=7f1f0f9f88dce6c9444c1692957af14adcc520f2" class="external">this commit</a>. The commit can be used as reference when preparing a new Webview version for <a class="issue tracker-3 status-3 priority-33 priority-high2" title="Issue: Update the webview apk (New)" href="https://redmine.replicant.us/issues/1780">#1780</a>.</p> Replicant - Issue #1780 (New): Update the webview apkhttps://redmine.replicant.us/issues/17802017-03-15T16:44:23ZWolfgang Wiedmeyerwreg@wiedmeyer.de
<p>Due to <a class="issue tracker-3 status-15 priority-33 priority-high2 closed child" title="Issue: Incomplete EGL implementation (Resolved)" href="https://redmine.replicant.us/issues/705">#705</a>, the webview apk in Replicant 6.0 cannot be updated. Currently, webview version 43.0.2357.134 is in use. It was released in July 2015 and has numerous security issues that were discovered since then.</p>
<p>Updating the webview apk would fix a lot of security issues and would ensure that websites can be visited securely using the browser shipped with Replicant or Lightning.</p>