Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062019-03-06T22:24:33ZReplicant
Redmine Replicant - Issue #1912 (Closed): f-droid: explain our new plan about how to get an fsdg complian...https://redmine.replicant.us/issues/19122019-03-06T22:24:33ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.orgReplicant - 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 - Issue #1853 (Closed): "Ecryption" typohttps://redmine.replicant.us/issues/18532017-12-19T10:54:21ZJeremy Rand
<p>The "Encrypt phone" dialog in Replicant 6.0 0003 states:</p>
<blockquote>
<p>Ecryption can fail sometimes</p>
</blockquote>
<p>"Ecryption" should be "Encryption".</p> Replicant - Issue #1827 (Resolved): Privacy issue with phone number lookup priovider. Was: WhiteP...https://redmine.replicant.us/issues/18272017-08-18T12:17:17ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<p>Hi, I noticed the following in my logs (i9300):<br /><pre>
08-18 09:05:20.935 8892 8923 V LookupProvider: Future called for FilterThread
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: People lookup failed
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: java.io.FileNotFoundException: http://whitepages.com/search/FindPerson?who=XX%20XX%20XX%20XX%20XX
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:238)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.LookupUtils.httpFetch(LookupUtils.java:61)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.LookupUtils.httpGet(LookupUtils.java:99)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.whitepages.WhitePagesApi.httpGet(WhitePagesApi.java:252)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.whitepages.WhitePagesApi.peopleLookup(WhitePagesApi.java:67)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.whitepages.WhitePagesPeopleLookup.lookup(WhitePagesPeopleLookup.java:45)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.LookupProvider.handleFilter(LookupProvider.java:313)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.LookupProvider.-wrap0(LookupProvider.java)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.LookupProvider$1.call(LookupProvider.java:171)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.LookupProvider$1.call(LookupProvider.java:170)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at com.android.dialer.lookup.LookupProvider$FutureCallable.call(LookupProvider.java:103)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
08-18 09:05:21.315 8892 8923 E WhitePagesPeopleLookup: at java.lang.Thread.run(Thread.java:818)
08-18 09:05:23.700 2356 2416 D lights : set_light_buttons: 1
08-18 09:05:23.890 2356 2440 D AudioService: Stream muted, skip playback
08-18 09:05:23.925 8892 8892 I SearchFragment: onItemClick: shortcutType=1
08-18 09:05:24.060 8892 8892 W Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
</pre><br />XX%20XX%20XX%20XX%20XX is a phone number I probably typed by hand in the dialer. I replaced the actual number with some X in the log for privacy reasons.</p>
<p>Denis.</p> Replicant - Issue #1801 (Resolved): Make Replicant be able to use external Wii dongles from the s...https://redmine.replicant.us/issues/18012017-05-19T09:42:15ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
Given that:
<ul>
<li>Android uses wpa_supplicant</li>
<li>Android probably talks to wpa_supplicant trough a control interface (ctrl_interface) in the wpa_supplicant configuration file.</li>
<li>wpa_supplicant can be started and controlled from shell scripts.</li>
<li>busybox can probably still be compiled for Android 6.0.</li>
<li>Busybox has a tiny version of udev called mdev, which can run scripts when a device is detected. It is probably very easy, with it, to run a script when an ath9k_htc compatible wifi card is detected.</li>
<li>As far as I understand, Android doesn't have a dev manager like udev, so using mdev would probably not conflict with other things.</li>
</ul>
<p>It may be possible to integrate external wifi support well enough to make it transparent for the user once the wifi dongle is plugged in.</p>
<p>Denis.</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>