Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062018-12-31T11:28:03ZReplicant
Redmine Replicant - Feature #1903 (Resolved): Implement a lookup settings reset when Dialer app is first runhttps://redmine.replicant.us/issues/19032018-12-31T11:28:03ZFil Bergamofil.bergamo@riseup.net
<p>This is related to issue <a class="issue tracker-3 status-15 priority-21 priority-default closed" title="Issue: Privacy issue with phone number lookup priovider. Was: WhitePagesPeopleLookup privacy leaks? (Resolved)" href="https://redmine.replicant.us/issues/1827">#1827</a>, that is solved in the new release of Replicant 6.0.<br />To solve the issue in already-installed environments, the Dialer app should be patched to do the following when it is run for the first time after a system upgrade:</p>
<p>- Reset all settings regarding lookup anti-features to "Disabled" <br />- Keep track of the one-time-change in the shared settings SQLite database<br />- Leave settings unchanged during subsequent runs, to allow users to adjust them as they wish.</p> Replicant - Issue #1898 (Resolved): Add Galaxy Note 8.0 tablet n51xx to website's "Supported Devi...https://redmine.replicant.us/issues/18982018-10-10T20:42:19ZFil Bergamofil.bergamo@riseup.net
<p>As user gufo gufo noticed <a href="https://redmine.replicant.us/boards/39/topics/13996?r=15021#message-15021" class="external">on a forum post</a> the website page regarding <a href="https://replicant.us/supported-devices.php" class="external">supported devices</a> is missing Galaxy Note 8.0 tablet that is supported in facts.</p>
<p>All that is needed is a patch for <a class="external" href="https://git.replicant.us/replicant/website/tree/supported-devices.php">https://git.replicant.us/replicant/website/tree/supported-devices.php</a></p> Replicant - Feature #1895 (Closed): Implement a self-update system for RepWifihttps://redmine.replicant.us/issues/18952018-09-26T17:38:05ZFil Bergamofil.bergamo@riseup.net
<p>As reported in Issue <a class="issue tracker-9 status-3 priority-39 priority-highest child" title="Feature: Make f-droid be FSDG compliant again to be able to include it again in Replicant (New)" href="https://redmine.replicant.us/issues/1878">#1878</a>, a discussion is open on the opportunity to stop bundling F-Droid into Replicant, until we find a way to make it FSDG-compliant.</p>
<p>If we end up removing F-Droid from official Replicant releases, then RepWifi should integrate a way of updating itself.</p> Replicant - Issue #1867 (Resolved): Download app not working when on USB network or RepWifi conne...https://redmine.replicant.us/issues/18672018-01-20T20:35:40ZFil Bergamofil.bergamo@riseup.net
<p>When no SIM is present, or mobile data are turned off, the Download app is pausing as soon as any download starts, and it never resumes.<br />This is almost certainly related to Issue <a class="issue tracker-3 status-15 priority-21 priority-default closed behind-schedule" title="Issue: WiFi connection established via RepWifi not correctly reported by the Android Framework to user-s... (Resolved)" href="https://redmine.replicant.us/issues/1792">#1792</a>.</p>
<p>While <a class="issue tracker-3 status-15 priority-21 priority-default closed behind-schedule" title="Issue: WiFi connection established via RepWifi not correctly reported by the Android Framework to user-s... (Resolved)" href="https://redmine.replicant.us/issues/1792">#1792</a> was solved by patching the application framework, I suppose the Download app calls a different function in the framework and not the one that got patched. This could be a possible reason why the issue is not solved for it, while it is solved for other "regular" apps.</p>
<p>I will investigate and probably find a solution.</p> Replicant - Feature #1806 (New): modem shell enable/disable script: verify with measurements thro...https://redmine.replicant.us/issues/18062017-05-20T19:26:14ZFil Bergamofil.bergamo@riseup.net
<p>In order to implement what's required in <a class="issue tracker-9 status-3 priority-21 priority-default parent" title="Feature: Implement setting that allows to permanently disable the modem (New)" href="https://redmine.replicant.us/issues/1779">#1779</a>, some docs are needed about how to achieve modem disabling under the hood.</p> Replicant - Issue #1792 (Resolved): WiFi connection established via RepWifi not correctly reporte...https://redmine.replicant.us/issues/17922017-04-12T20:44:28ZFil Bergamofil.bergamo@riseup.net
<p>It is a suggested best practice for Android apps to check for the connectivity status of the device before performing any network-related task.<br />To do so, the Android Framework exposes some methods that apps can use to retrieve the available network connections, and their status.</p>
<p>When a WiFi connection is established via RepWifi app, although perfectly working (ping, dns resolution, web browsing), the framework still presents the WiFi connection as disabled or disconnected to the user-space apps.<br />This misleads apps that rely on this mechanism, so that they prevent the user from doing network-related tasks.</p>
<p>E.g. F-Droid prevents the user from updating the repos while connected to WiFi via RepWifi app, because it detects the WiFi connection as inactive.</p>
<p>A possible solution is to modify the designated system service in the Android Framework that reports the connection status to client apps.<br />Some research has already been done in this field.<br />A promising approach seems to properly modify the class "com.android.ConnectivityService.java" to read the ip routing tables, and detect the route established by RepWifi, and if present, modify the status of the corresponding "NetworkInfo" instance returned to calling applications.</p> Replicant - Issue #1791 (New): [RepWifiApp] Instable interface wlan0 on i9100https://redmine.replicant.us/issues/17912017-04-12T19:54:36ZFil Bergamofil.bergamo@riseup.net
<p>Conditions:<br /> - device: I9100<br /> - battery level below 80%<br /> - using RepWifi App to connect to a WiFi access point, via an external dongle (ath9k_htc)</p>
<p>Behaviour:<br />The "wlan0" interface assigned to the external dongle gets removed while interacting with the WiFi access point, causing the connection process to abort. The user needs to physically unplug and re-plug the dongle to get the interface appear again in the list returned by <pre>ip link</pre></p>
<p>The issue is almost totally absent at full battery level, raising the suspect that it could somehow have something to do with the dongle not receiving enough current. Issues with current drawing were present even on Replicant 4.2 on the i9100.</p>
<p>When using the scripts from the "Terminal Emulator" app or from the built-in terminal, the issue is much less frequent.<br />This could be related to the app being graphically more demanding than the bare terminal, and as such, being more CPU-intensive, such that it draws more current, preventing the dongle to get enough power, especially when charge is low.</p>
<p>A possible solution could come from looking at the source code of the built-in terminal app, to see how it manages to call shell commands, and see if using the same method in RepWifi App solves the issue (currently RepWifi launches "su" as a process and fills its standard input with commands via pipes).</p>