Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062016-03-06T19:25:05ZReplicant
Redmine Replicant - Issue #1659 (In Progress): The device pages don't warn about proprietary (and likely ...https://redmine.replicant.us/issues/16592016-03-06T19:25:05ZPaul Kocialkowskipaulk@replicant.us
<p>Most of the devices currently supported by Replicant (except the GTA04) support TrustZone, which is likely used on most devices. It is likely the reason why manufacturers enforce signed bootloaders while allowing unsigned kernels to run.</p>
<p>TrustZone TEE runs in parallel to and with greater privileges than the regular operating system (Replicant). Since it is proprietary and stored with/loaded by the (signed) bootloader, it is a great threat to both freedom and privacy/security. TrustZone is often used to allow decoding DRM contents without any possibility for the user</p>
However, since little is known about TrustZone TEE implementations (and exactly how it's loaded, how it's contacted), we should do some research about:
<ul>
<li>Whether there are TrustZone bindings in the kernel (e.g. related to DRM decoding).</li>
<li>How the (signed) bootloaders load the TrustZone TEE image and where it is stored. If not part of the bootloader image, knowing whether it is signed would be crucial.</li>
</ul>
<p>Looking at some documentation and known free implementations for that could help (ARM's reference trusted firmware). Some platforms and devices come with more documentation about TrustZone (e.g. i.MX53 and USB armory, Tegra X1).</p> Replicant - Issue #1599 (Closed): No access to repohttps://redmine.replicant.us/issues/15992016-01-09T15:21:09ZAlexandre Roumiantsevran@mail.wplus.net
<p>fatal: unable to connect to git.replicant.us:<br />git.replicant.us[0: 18.4.89.63]: errno=Connection refused</p> Replicant - Feature #1563 (Rejected): Generic advises on second hand buyinghttps://redmine.replicant.us/issues/15632015-12-11T14:13:34ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
Since many of the devices Replicant support are now old, we might advise buyers to:
<ul>
<li>Buy from Replicant friendly shops</li>
<li>Advises them on issues when not buying from such shops (Like batteries issues). discontinued official batteries:
<ul>
<li>Samsung Galaxy S (<a class="issue tracker-3 status-27 priority-27 priority-high3 closed" title="Issue: Samsung do not sell Galaxy S standard batteries any more (Closed)" href="https://redmine.replicant.us/issues/1413">#1413</a>, <a class="issue tracker-3 status-27 priority-27 priority-high3 closed" title="Issue: Samsung Galaxy S standard batteries discontinued (Closed)" href="https://redmine.replicant.us/issues/1425">#1425</a>)</li>
<li>Galaxy Note (N7000) (<a class="issue tracker-3 status-27 priority-27 priority-high3 closed" title="Issue: Samsung Note standard batteries discontinued (Closed)" href="https://redmine.replicant.us/issues/1431">#1431</a>, <a class="issue tracker-3 status-27 priority-27 priority-high3 closed" title="Issue: Samsung Note standard batteries discontinued (Closed)" href="https://redmine.replicant.us/issues/1437">#1437</a>)</li>
</ul></li>
</ul>
<p>The (duplicated) bugreports mentioned a way to check if new batteries can still be bought easily: <a class="external" href="http://www.samsung.com/us/mobile/cell-phones-accessories/batteries-battery-doors">http://www.samsung.com/us/mobile/cell-phones-accessories/batteries-battery-doors</a> and mentioned the risk of third party batteries with <a class="external" href="http://www.howtogeek.com/172680/danger-why-you-shouldnt-buy-cheap-third-party-batteries-for-laptops-or-smartphones/">http://www.howtogeek.com/172680/danger-why-you-shouldnt-buy-cheap-third-party-batteries-for-laptops-or-smartphones/</a></p>
<p>However batteries, even if stored properly have a limited life expectancy. As a result, at some point official batteries will be useless since they all will be broken. Only unofficial remakes will be possible at that point.</p> Replicant - Issue #957 (Closed): NFC on I9300 does not require libpn544_fw.so if patch is revertedhttps://redmine.replicant.us/issues/9572014-08-05T12:25:21ZSimon Josefssonsimon@josefsson.org
<p>I looked into why NFC on I9300 required libpn544_fw.so in Replicant but not in CyanogenMod. I found this commit:</p>
<p><a class="external" href="https://www.gitorious.org/replicant/external_libnfc-nxp/commit/85af7251179c3cf53c785e9a055942d3ab6462c1">https://www.gitorious.org/replicant/external_libnfc-nxp/commit/85af7251179c3cf53c785e9a055942d3ab6462c1</a></p>
<p>It changes a soft-fail to a hard-fail when the file is missing. Reverting this makes everything work for me. Why was the patch added?</p>
<p>For background and debug messages see <a class="external" href="http://blog.josefsson.org/2014/08/05/replicant-4-2-0002-and-nfc-on-i9300/">http://blog.josefsson.org/2014/08/05/replicant-4-2-0002-and-nfc-on-i9300/</a></p>
<p>If it is needed on some other platform, please consider making it soft-fail for I9300 devices.</p> Replicant - Issue #951 (Closed): Preferred Network Offload leaks known SSIDshttps://redmine.replicant.us/issues/9512014-07-17T14:37:39ZPaul Kocialkowskipaulk@replicant.us
<p>EFF article about the issue: <a class="external" href="https://www.eff.org/deeplinks/2014/07/your-android-device-telling-world-where-youve-been">https://www.eff.org/deeplinks/2014/07/your-android-device-telling-world-where-youve-been</a><br />XDA-Developers thread: <a class="external" href="http://forum.xda-developers.com/showthread.php?t=2780902">http://forum.xda-developers.com/showthread.php?t=2780902</a><br />Patch at OmniROM: <a class="external" href="https://gerrit.omnirom.org/#/c/7971/">https://gerrit.omnirom.org/#/c/7971/</a></p> Replicant - Issue #645 (Rejected): search tool crasheshttps://redmine.replicant.us/issues/6452013-09-05T15:54:05ZJ Wallanderwallander@no-log.org
<p>nexus s, replicant 4.0/0004</p>
steps to reproduce :
<ul>
<li>invoke the search tool with the search soft key (magnifying glass symbol, on the bottom of the screen)</li>
<li>within the search tool, click on the arrow under the magnifying glass ( top left of the screen)</li>
<li>click on the wheel symbol (settings)</li>
<li>seach tool dies , a message pop pup says : "unfortunately , search has stopped."</li>
</ul> Replicant - Issue #531 (Closed): error during restoring data from the recovery for Galaxy S (GT-I...https://redmine.replicant.us/issues/5312013-05-20T00:12:45ZIvan Zakharyaschevimz@altlinux.org
<p>I'm using the recovery.img for Galaxy S (GT-I9000) from <a class="external" href="http://redmine.replicant.us/projects/replicant/wiki/ReplicantImages">http://redmine.replicant.us/projects/replicant/wiki/ReplicantImages</a> (the last one, from 2013-04-06), on two such devices.</p>
<p>I've created a backup on one of them, copied the clockworkmod/ directory to the other one, and want to restore it there.</p>
<p>But an error happens when restoring data. The log is attached.</p>
<p>(My main system is CyanogenMod 10.)</p>
<p>Of course, it'd be nice if the error got fixed, so that the restore process succeeds.</p>
<p>As a prerequisite to fixing this error, it'd be helpful, if the error message was more informative: what went wrong.</p>
<p>Also, I could try to figure out what is wrong and debug the restore process myself, but for this, a prerequisite is for me to be able to study the source code of the restore program and to run it under tracing/debugging tool (the first simplest thing would be for me to run it under strace, in an emulator of Android perhaps). Since the Replicant project is known to pay special attention to being free software, I'm expecting to have the freedom to study the source code and to debug. But unfortunately, this is not very clear how to do: the page where I've got the recovery.img from (<a class="external" href="http://redmine.replicant.us/projects/replicant/wiki/ReplicantImages">http://redmine.replicant.us/projects/replicant/wiki/ReplicantImages</a>) doesn't point me to the source code of the image, and doesn't explain how I can peek inside the image on another system for studying it. This is hindering us exploiting the benefits of the freedoms of free software.</p>
<p>Well, some additional information, so that you perhaps are able to think about a reason for the error:</p>
<p>the backup I've made on the same device before can be restored without such an error. So, I'm attaching the 2 data backups (without the blobs) -- to be able to compare them. I've also extracted the list of filenames from the 2 backups (with cut) to diff them.</p>
<p>BTW, the process seems to interrupt around the files xt.*, uid.*, uid_tag.* from system/netstats/ . Does this give you a clue about what can be wrong?</p>
<p>I'm struggling to restore that backup. If you give an advice how to overcome the error, I'd be grateful.</p> Replicant - Feature #417 (Closed): Show screen with hang-up button by default during callhttps://redmine.replicant.us/issues/4172013-03-03T18:58:01ZMatt Kraaikraai@ftbfs.org
<p>If I dial a number, bring the phone to my ear, wait for a while (e.g., for the ringing to stop and the call to go to voice mail), and then take the phone away from my ear, the phone displays the list of recent calls. I think it should display the screen containing the hang-up button instead. In order to get to the screen that contains the hang-up button now, I press the Home icon, the Phone icon, and then select "Return to call in progress."</p> Replicant - Issue #141 (Closed): Automatic date & time setting doesn't workhttps://redmine.replicant.us/issues/1412012-04-11T13:18:47ZAnonymous
<p>When I enable automatic setting of the date & time via Menu -> Settings -> Date & time -> Automatic, neither the date nor time is automatically set to the correct value.</p> Replicant - Issue #29 (Closed): Unable to attach file to tickethttps://redmine.replicant.us/issues/292011-09-17T22:56:46ZMatt Kraaikraai@ftbfs.org
<p>When I tried to attach a patch to a ticket, it failed with the following error:</p>
<p>Oops…<br />Trac detected an internal error:<br />OSError: [Errno 13] Permission denied: '/var/lib/trac/sites/replicant/attachments/ticket'<br />There was an internal error in Trac. It is recommended that you inform your local Trac administrator and give him all the information he needs to reproduce the issue.</p>
<p>To that end, you could a ticket.</p>
<p>The action that triggered the error was:</p>
<p>POST: /attachment/ticket/28<br /><a class="wiki-page new" href="https://redmine.replicant.us/projects/replicant/wiki/TracGuide">TracGuide</a> — The Trac User and Administration Guide</p>