Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062019-06-22T18:58:42ZReplicant
Redmine Replicant - Feature #1939 (Rejected): PinePhone Pine64 https://redmine.replicant.us/issues/19392019-06-22T18:58:42ZSkoll RC
<p>Hi all,</p>
<p>Is this phone <a class="external" href="https://www.pine64.org/pinephone/">https://www.pine64.org/pinephone/</a> a good candidate for Replicant? <br />Many linux distros and ubports seems to be compatible with it. It seems to have a USB modem and many free drivers/firmwares</p> Replicant - Issue #1179 (Closed): project external/google contains analytics and market related s...https://redmine.replicant.us/issues/11792015-01-15T12:11:24ZRobert Schultzl.rsh2@hotmail.co.uk
<p>In the manifest's default.xml contains <project path="external/google" name="CyanogenMod/android_external_google" />. This folder contains jar files from play, gcm, admob, market_licensing etc. Just wondering if this is removable to make it clean and lean! Or perhaps it does not matter?<br />Great work!</p> Replicant - Issue #1101 (Closed): add tracking and privacy filters to the browser directlyhttps://redmine.replicant.us/issues/11012014-11-25T16:54:19ZRobert Schultzl.rsh2@hotmail.co.uk
<p>This is related to the android browser. I was wondering if you could add a block list to src/com/android/browser/Tab.java to avoid tracking. Please see the attached patch.</p>
<p>I must admit I am not a professional programmer, so apologies if it looks terrible. I adapted it from MIT license code <a class="external" href="http://git.io/Z0wgnQ">http://git.io/Z0wgnQ</a> (where the list of domains are loaded from XML array from src/res/xml). Perhaps you can make this better!</p>
<p>This block list can also be obtained from disconnect addon blacklist <a class="external" href="http://git.io/zUuHHA">http://git.io/zUuHHA</a>. It is sure that this list may block some websites from loading. There may be a menu item or tickbox added to temporarily bye pass blocking in advanced settings (if needed).</p>
<p>Many thanks for your great work!</p> Replicant - Issue #993 (Closed): SIM card isn't fully usable when SIM lock is engagedhttps://redmine.replicant.us/issues/9932014-10-14T15:10:09ZRichard "Cylus" Palmerc@cyl.us
<p>When the SIM card is locked, the device is only partially able to access it, even after entering the SIM PIN. Specifically, SIM lock cannot be disabled, SIM PIN cannot be changed, and the voicemail number on the SIM card cannot be read.</p>
<p>The updated Samsung RIL might have already fixed this, so I apologize for reporting this if it is no longer an issue.</p> Replicant - Issue #789 (Rejected): Consider including repo manifest -r output with distributed im...https://redmine.replicant.us/issues/7892014-01-05T17:02:41ZRiku Saikkonenrjs@netti.fi
<p>The Replicant build directories contain a git_versions.txt file containing git commit IDs from subprojects. (For example, <a class="external" href="http://ftp.osuosl.org/pub/replicant/sdk/replicant-4.0/0001/infos/git_versions.txt">http://ftp.osuosl.org/pub/replicant/sdk/replicant-4.0/0001/infos/git_versions.txt</a> .) However, there doesn't seem to be a way to use this file automatically, for example to rebuild an image using the same versions of software than in the distributed image. It appears that the build instructions in e.g. <a class="wiki-page" href="https://redmine.replicant.us/projects/replicant/wiki/SDKBuild">SDKBuild</a> produce a current version of most software in the image, and not the versions that Replicant distributes. (Because the Replicant manifest default.xml does not contain exact revision information for most of the subprojects.)</p>
<p>However, the repo tool appears to be able to generate a manifest containing the commit IDs: repo manifest -r -o mymanifest.xml</p>
<p>I assume that if this generated manifest was included in, e.g., the replicant/manifest repository as, say, sdk_4.0_0001.xml, then one could view the sources and/or rebuild this exact version of the SDK with: repo init -u git://gitorious.org/replicant/manifest.git -m sdk_4.0_0001.xml<br />(probably also with repo sync -m sdk_4.0_0001.xml, from what I understand of "repo help sync")</p>
<p>There is also a "smart tag" option in repo (repo sync -t), which seems to be designed for fetching a particular version (a "known good build" is the example the help uses), but it seems to require setting up something called a "manifest server" on the network that would respond to these kinds of queries. Storing manifests containing commit IDs in files seems to be a much simpler approach.</p>
<p>Another approach would of course be for Replicant to distribute the source code of each image along with the binaries, but the files are rather huge. (repo init + repo sync of replicant-4.0 takes about 21 gigabytes on disk right now. Although I guess you could distribute only the then-current version and not the revision history: a .tar.gz of everything except the .repo subdirectory is "only" 2.5 gigabytes, and I assume that it (or a shallow clone, repo init --depth=1) would be enough for rebuilding.)</p>
<p>(Disclaimer: I did not have time to test that the repo init/sync stuff actually works, but the generated manifest looked correct. Sorry for not testing properly, but I thought it would be better to write this bug report quickly, as I heard you may be producing new images in the near future, and it is difficult to create this versioned manifest afterwards if you modify or re-sync the build directory...)</p> Replicant - Issue #765 (Rejected): Low-SAR smartphoneshttps://redmine.replicant.us/issues/7652013-12-24T00:40:57ZAnonymous
<p>I would love to read "Replicant is a fully free Android distribution running on several devices, ESPECIALLY LOW-RADIATION SMARTPHONES." (See <a class="external" href="https://en.wikipedia.org/wiki/List_of_major_low-radiation_smartphones_with_FCC_approval">https://en.wikipedia.org/wiki/List_of_major_low-radiation_smartphones_with_FCC_approval</a>)</p> Replicant - Issue #669 (Rejected): Installation instructions lack explicit hints about proprietar...https://redmine.replicant.us/issues/6692013-10-12T12:38:19ZDaniel Kuleszdaniel.ina1@googlemail.com
<p>New users to replicant might start just installing the distribution on their phones by downloading the latest image and flashing it by following the installation instructions. They end up with a system, where hitting the "on" button for wifi would just do nothing, giving no feedback to the user why it does not work and no hints how this can be overcome. Novices might get the impression that there is an awful bug in replicant and the functionality is simply broken.</p>
<p>Also, there is no explicit hint that these things (like wifi, blueooth for the nexus s) will NOT WORK unless the proprietary firmware files are flashed. Unfortunately, after flashing replicant the firmware files are gone, so users would either have to download them somewhere else, extract them from the official factory images (where available) or first flash back to the previous distruction, pull them from there via adb (instructions for this are only anecdotal!) and then flash replicant again and install these firmware files.</p>
<p>I would highly suggest to place an explicit hint in the installation guides, so users wishing to have a "useable" device will now that they need to extract these firmwares beforehand plus maybe some hints on how to do that.</p> Replicant - Issue #369 (Rejected): Not able to turn ON Wi-Fi Direct after power ON/OFF the device.https://redmine.replicant.us/issues/3692013-01-04T09:56:30ZAnonymous
<p>Line 3002: 01-02 10:43:51.691 1940 1940 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 3002: 01-02 10:43:51.691 1940 1940 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 3607: 01-02 10:43:55.345 1940 1940 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 3765: 01-02 10:43:56.035 1940 1940 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 3766: 01-02 10:43:56.035 1940 1940 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 3767: 01-02 10:43:56.035 1940 1940 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 5230: 01-02 10:44:11.851 2445 2445 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 5230: 01-02 10:44:11.851 2445 2445 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 5266: 01-02 10:44:13.112 2445 2445 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 5280: 01-02 10:44:13.382 2445 2445 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 5281: 01-02 10:44:13.382 2445 2445 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 5282: 01-02 10:44:13.382 2445 2445 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 6540: 01-02 10:44:32.071 2929 2929 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6540: 01-02 10:44:32.071 2929 2929 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6541: 01-02 10:44:32.721 2929 2929 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 6542: 01-02 10:44:32.901 2929 2929 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 6543: 01-02 10:44:32.901 2929 2929 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 6544: 01-02 10:44:32.901 2929 2929 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 6720: 01-02 10:44:52.150 2941 2941 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6720: 01-02 10:44:52.150 2941 2941 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6721: 01-02 10:44:52.811 2941 2941 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 6722: 01-02 10:44:52.971 2941 2941 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 6723: 01-02 10:44:52.971 2941 2941 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 6724: 01-02 10:44:52.971 2941 2941 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 6884: 01-02 10:45:12.190 2947 2947 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6884: 01-02 10:45:12.190 2947 2947 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6885: 01-02 10:45:12.870 2947 2947 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 6886: 01-02 10:45:13.041 2947 2947 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 6887: 01-02 10:45:13.041 2947 2947 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 6888: 01-02 10:45:13.041 2947 2947 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 17114: [init.svc.wpa_supplicant]: [stopped]<br />Line 37698: Proc wpa_supplicant:</p> Replicant - Issue #273 (Closed): Keylogger on browser when typing URLhttps://redmine.replicant.us/issues/2732012-10-21T16:02:04ZPaul Kocialkowskipaulk@replicant.us
<p>It seems that every key typed in the URL field on the browser is sent to Google (which returns search suggestions).<br />We should check if it's also the case on the keyboard when suggestions are enabled.</p> Replicant - Issue #28 (Closed): Errors performing "repo sync" of replicant-2.3 branchhttps://redmine.replicant.us/issues/282011-09-17T22:51:58ZMatt Kraaikraai@ftbfs.org
<p>When I try to perform "repo sync" of the replicant-2.3 branch, I encounter a couple of errors:</p>
<ul>
<li>the replicant/android_hardware_ril repository does not exist and</li>
<li>the master revision does not exist in the <a class="wiki-page new" href="https://redmine.replicant.us/projects/replicant/wiki/CyanogenMod">CyanogenMod</a>/themes-platform-vendor-tmobile-apps-ThemeChooser repository.</li>
</ul>
<p>I've fixed the first problem by substituting replicant/ril for replicant/android_hardware_ril and fixed the second by using the gingerbread revision instead of the master one. A patch making this changes is attached.</p>