Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062020-11-17T00:43:38ZReplicant
Redmine Replicant infrastructure - Issue #2173 (New): Setup onion serviceshttps://redmine.replicant.us/issues/21732020-11-17T00:43:38Zdl luddllud@riseup.net
<p><a href="https://2019.www.torproject.org/docs/onion-services.html.en" class="external">Onion services</a> allow Tor users to access resources such as websites without ever leaving the Tor network, i.e. without having their traffic exposed to the clearnet and routed through an exit node. This has several privacy and security advantages.</p>
<p>Replicant should have onion services for all it's services: <a href="https://replicant.us" class="external">website</a>, <a href="https://redmine.replicant.us" class="external">Redmine</a>, <a href="https://ftp.osuosl.org/pub/replicant/" class="external">FTP</a> and <a href="https://git.replicant.us/" class="external">git</a> .</p> Replicant - Feature #2105 (New): Investigate custom kernels for fixes or improvements on: audio, ...https://redmine.replicant.us/issues/21052020-08-06T14:54:12Zdl luddllud@riseup.net
<p>Up until Replicant 6 (inclusive), the kernel used on the Exynos 4412 devices has been the CyanogenMod (later LineageOs) maintained <a href="https://git.replicant.us/replicant/kernel_samsung_smdk4412/" class="external">smdk4412 kernel</a>. As of Replicant 10 we have transitioned to an upstream kernel, which now has <a href="https://blog.forkwhiletrue.me/pages/midas-mainline/" class="external">support for Exynos 4412 based devices</a>.<br />The upstream support may be incomplete in some areas, for which we may wish to look into smdk4412 as a source of fixes or improvements. Besides smdk4412, there are other community kernels, which may contain valuable patches:</p>
<ul>
<li>Perseus<br /><a class="external" href="https://github.com/AndreiLux/Perseus-S3">https://github.com/AndreiLux/Perseus-S3</a><br /><a class="external" href="https://forum.xda-developers.com/galaxy-s3/orig-development/kernel-perseus-t1691401">https://forum.xda-developers.com/galaxy-s3/orig-development/kernel-perseus-t1691401</a></li>
</ul>
<ul>
<li>Siyah Kernel<br /><a class="external" href="https://github.com/gokhanmoral/siyahkernel-sgs3">https://github.com/gokhanmoral/siyahkernel-sgs3</a><br /><a class="external" href="https://forum.xda-developers.com/galaxy-s3/orig-development/kernel-siyahkernel-s3-v1-9-1-t1709686">https://forum.xda-developers.com/galaxy-s3/orig-development/kernel-siyahkernel-s3-v1-9-1-t1709686</a></li>
</ul>
<ul>
<li>Googy Max2 Kernel<br /><a class="external" href="https://github.com/googyanas/Googy-Max2-Kernel">https://github.com/googyanas/Googy-Max2-Kernel</a><br /><a class="external" href="https://forum.xda-developers.com/galaxy-s3/orig-development/28-04-googy-max2-kernel-2-3-1-cm-camera-t2517875">https://forum.xda-developers.com/galaxy-s3/orig-development/28-04-googy-max2-kernel-2-3-1-cm-camera-t2517875</a></li>
</ul> Replicant - Feature #2099 (New): Separate screen lock and boot passwordshttps://redmine.replicant.us/issues/20992020-07-26T19:31:21Zdl luddllud@riseup.net
On Replicant 6 you can set different passwords for the screen lock and boot. Such can be done with commands such as:
<ul>
<li><code>vdc cryptfs enablecrypto inplace password MyLongPassword</code></li>
<li><code>vdc cryptfs enablecrypto wipe password MyLongPassword</code></li>
</ul>
<p>Or with an app such as <a href="https://f-droid.org/en/packages/cz.eutopia.snooperstopper/" class="external">SnooperStopper</a>, which uses <code>vdc cryptfs</code> underneath.</p>
<p>This allows for a great compromise between security and usability. You can set a simple PIN for the screen lock, and a long alphanumeric password for boot which is your actual encryption key.</p>
<p>Unfortunately it seems that <code>vdc cryptfs</code> no longer works on recent Android versions (I tested with Lineage 16). This probably stems from the fact that Android now relies on a Trusted Execution Environment (TEE) to (securely?) derive an encryption key out of the user's lock screen PIN and then store it.</p>
Replicant 10 will be unable to use a TEE for several different reasons:
<ul>
<li>Old devices have SoCs that do not support a TEE.</li>
<li>There may be no free software TEE implementation available for the target device.</li>
<li>Even if a free software TEE is available, the device's bootloader is locked and cannot load it.<br />For further details check <a class="wiki-page" href="https://redmine.replicant.us/projects/replicant/wiki/Upstream#Gatekeeper-HAL-backend">Gatekeeper HAL backend</a>.</li>
</ul>
<p>As such, finding a way to have a separate boot password/encryption key on Replicant 10 seems to be a must. Otherwise users will be faced with a dilemma:<br />a) Use a simple PIN and be exposed to bruteforce attacks.<br />b) Use a long password and take some long minutes to unlock the phone everytime they need it.</p> Replicant - Feature #2098 (New): Support SIM network unlockhttps://redmine.replicant.us/issues/20982020-07-26T18:49:50Zdl luddllud@riseup.net
<p><a class="wiki-page" href="https://redmine.replicant.us/projects/replicant/wiki/Libsamsung-RIL">libsamsung-RIL</a> lacks support for <code>RIL_REQUEST_ENTER_NETWORK_DEPERSONALIZATION</code>, which appears to be the RIL request/response responsible for handling the network unlock procedure.</p>
<p>As detailed on issues like <a class="issue tracker-3 status-27 priority-27 priority-high3 closed" title="Issue: My SIM is locked and still doesn't work after unlocking it on lineageos (Closed)" href="https://redmine.replicant.us/issues/1840">#1840</a>, a valid "SIM network unlock PIN" is rejected by Replicant with the error "SIM network unlock unsuccessful" because of this missing feature.</p> Replicant - Issue #2097 (New): Check if mainline Linux has blobs for our targetshttps://redmine.replicant.us/issues/20972020-07-23T14:18:34Zdl luddllud@riseup.net
<p>Check if torvalds/master Linux kernel includes blobs for our target devices (GT-I9300 and GT-I9305 so far). If so, we should change upstream to <a href="https://www.fsfla.org/ikiwiki/selibre/linux-libre/" class="external">linux-libre</a>.</p> Upstreaming patches - Feature #2073 (New): PIT file editor: extend Heimdall with reverse of print...https://redmine.replicant.us/issues/20732020-07-07T10:15:34Zdl luddllud@riseup.net
<p>PIT (Partition Information Table) files contain the partition layout for Samsung phones and tablets. They can be used by flashing tools such as <a href="https://gitlab.com/BenjaminDobell/Heimdall" class="external">Heimdall</a> to repartition the device.</p>
<p>So far, Replicant did not require any device to be repartitioned, and rather sticked with the stock partition table. However, repartitioning may be needed in the near future, due to issues like <a class="issue tracker-9 status-3 priority-21 priority-default" title="Feature: Remove UMS partition (New)" href="https://redmine.replicant.us/issues/1873">#1873</a>.</p>
<p>Unfortunately, there is no free software tool available to edit PIT files. There is only a proprietary tool dubbed <a href="https://forum.xda-developers.com/showthread.php?t=1916936" class="external">PIT Magic</a>.</p>
<p>Heimdall includes a sub-module, called <a href="https://gitlab.com/BenjaminDobell/Heimdall/-/tree/master/libpit" class="external">libpit</a> that can read a PIT file and print the contents in a human readable format. This can be used through Heimdall's <code>print-pit</code> command.<br />This existing feature could be leveraged to create the reverse command, say <code>build-pit</code>, that grabs the human readable text format and generates the corresponding binary PIT.</p>
<p>Due to modularity and separation of concerns, I would rather have both these commands (<code>print-pit</code> and <code>build-pit</code>) in a separate tool. Heimdall should only do flashing ("do one thing, do it right").<br />The only advantage I see on adding this to Heimdall, is that Heimdall is already packaged in several GNU/Linux distros. Users could easily access this new feature once a new version is released. However this isn't much relevant, as editing PIT files is not something end-users are going to do. The PIT file must be crafted according to needs of the Android distribution, and thus is a task for Replicant maintainers.</p> Replicant - Issue #1943 (New): Tune media player for software renderinghttps://redmine.replicant.us/issues/19432019-07-22T20:22:26Zdl luddllud@riseup.net
<p>Android 9 Media Player Service includes tweaks to compensate for the poor rendering performance on the emulator. For instance: <a href="https://github.com/LineageOS/android_frameworks_av/blob/4d5b74c4715223a882661bfd2c2ca564a7331f8a/media/libmediaplayerservice/MediaPlayerService.cpp#L1652" class="external">MediaPlayerService.cpp:152</a><br /><pre><code class="c syntaxhl"><span class="n">mMinBufferCount</span> <span class="o">=</span> <span class="mi">12</span><span class="p">;</span> <span class="c1">// to prevent systematic buffer underrun for emulator</span>
</code></pre></p>
<p>We may want to re-use these on Replicant devices that run on software rendering.</p> Replicant - Feature #1017 (New): Sim ToolKit (STK) support is missinghttps://redmine.replicant.us/issues/10172014-10-30T16:19:39Zdl luddllud@riseup.net
<p>According to the <a class="wiki-page" href="https://redmine.replicant.us/projects/replicant/wiki/Samsung-RIL">Samsung-RIL</a> wiki page STK (Sim Toolkit) commands are either missing or disabled.</p>
<p>Without them one cannot use devices like the "magic" dual-SIM adapters, which could be a great way to circumvent the lack of Replicant support for a dual-SIM phone.</p> Replicant - Issue #1011 (In Progress): USSD codes don't workhttps://redmine.replicant.us/issues/10112014-10-30T16:13:11Zdl luddllud@riseup.net
<p>As reported on bug <a class="issue tracker-3 status-27 priority-27 priority-high3 closed" title="Issue: USSD codes don't work (Closed)" href="https://redmine.replicant.us/issues/32">#32</a> USSD codes aren't working on Replicant 4.2. I get:<br /><code>Connection problem or invalid MMI code.</code></p>