Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062018-10-13T22:04:48ZReplicant
Redmine Replicant - Issue #1899 (New): complete website information about supported devicehttps://redmine.replicant.us/issues/18992018-10-13T22:04:48ZFil Lupinfillupin@protonmail.com
<p>It seems several pages on website describes different status for the same devices.<br />Make the information given on these pages consistent would help making Replicant clearer for visitors.</p>
<p>Here are the pages where I found information which could be to update:</p>
<p>- Check page <a class="external" href="https://www.replicant.us/freedom-privacy-security-issues.php#recommendations">https://www.replicant.us/freedom-privacy-security-issues.php#recommendations</a> into "Choosing the best Replicant-supported device" if it is still up-to-date.</p>
<pre><code>In particular, it is written that GTA04 should be the prefered choice, it also is written that it is not fully supported but work is in progress. Since last date mentionned in this page is 2015, a last update date mention would help to understand if a support for GTA04 has been a project but is not anymore to wait, or if it is still in progress.</code></pre>
<p>- Supported devices page <a class="external" href="https://www.replicant.us/supported-devices.php">https://www.replicant.us/supported-devices.php</a> which include as <b>maintained devices</b>:</p>
<ul>
<li>Nexus S (I902x)</li>
<li>Galaxy S (I9000)</li>
<li>Galaxy S 2 (I9100)</li>
<li>Galaxy Note (N7000)</li>
<li>Galaxy Nexus (I9250)</li>
<li>Galaxy S 3 (I9300)</li>
<li>Galaxy Note (N7100)</li>
<li>Galaxy Tab 2 7.0 (P31xx)</li>
<li>Galaxy Tab 2 10.1 (P51xx)</li>
</ul>
<pre><code>and following uncompleted devices:</code></pre>
<ul>
<li>GTA04</li>
<li>Galaxy S 3 4G (I9305)</li>
</ul>
<pre><code>and following unmaintained devices:</code></pre>
<ul>
<li>Dream/Magic</li>
<li>Nexus One</li>
</ul>
Since 12 devices are noted now supported by Replicant 6, I think the supported devices' list should be updated. A more clear information could be given by a tab giving the status for Replicant 4.2 and Replicant 6 for each device (supported/uncomplete/unmaintained).<br /> From Replicant 6.0 0001 (<a class="external" href="https://ftp.osuosl.org/pub/replicant/images/replicant-6.0/0001/metadata/changelog.txt">https://ftp.osuosl.org/pub/replicant/images/replicant-6.0/0001/metadata/changelog.txt</a>) and 0002 (<a class="external" href="https://ftp.osuosl.org/pub/replicant/images/replicant-6.0/0002/metadata/changelog.txt">https://ftp.osuosl.org/pub/replicant/images/replicant-6.0/0002/metadata/changelog.txt</a>) changelog, I understand Replicant 6 is supported for following devices:
<ul>
<li>Galaxy S 2 (I9100)</li>
<li>Galaxy S 3 (I9300)</li>
<li>Galaxy Note 2 (N7100)</li>
<li>Galaxy S 3 4G (I9305)</li>
<li>Galaxy Note (N7000)</li>
<li>Galaxy Nexus (I9250)</li>
<li>Galaxy Tab 2 7.0 (P31xx)</li>
<li>Galaxy Tab 2 10.1 (P51xx)</li>
<li>Galaxy Note 8.0 (N5100 and N5110)</li>
</ul>
<pre><code>which makes 9 devices available for Replicant 6.</code></pre>
<p>- on wiki page <a class="external" href="https://redmine.replicant.us/projects/replicant/wiki/ReplicantStatus">https://redmine.replicant.us/projects/replicant/wiki/ReplicantStatus</a> with a detail status.<br /> Since this list include the same devices that former one, it seems to me these lists are not depending on interpretation so I do not understand the sens of the answer of Fil Bergamo in <a class="external" href="https://redmine.replicant.us/boards/27/topics/14642?r=14847#message-14847">https://redmine.replicant.us/boards/27/topics/14642?r=14847#message-14847</a></p>
<p>However, it seems to me only one page would assure that no inconsistency remains between website pages in the future.</p> Replicant - Issue #1883 (Closed): no device available through adbhttps://redmine.replicant.us/issues/18832018-06-21T23:30:26ZFil Lupinfillupin@protonmail.com
<p>Hi,<br />related to <a class="external" href="https://redmine.replicant.us/boards/9/topics/14343">https://redmine.replicant.us/boards/9/topics/14343</a> I do not succeed into accessing my device through adb.</p>
<p>I tried <a class="external" href="https://redmine.replicant.us/projects/replicant/wiki/ADB">https://redmine.replicant.us/projects/replicant/wiki/ADB</a> but it does not work.<br />I also tried to unplug the usb cable, restart the OS, kill/restart the server, unactivate/activate debug mode, nothing works.</p>
<p>Do you have any idea how I could access the device through adb?<br />This is step 1 for any backup procedure. :s</p>
<p>Thank you</p> Replicant - Issue #1876 (Closed): error when signinf build for i9100https://redmine.replicant.us/issues/18762018-04-03T14:00:50ZFil Lupinfillupin@protonmail.com
<p>Hi,<br />following instructions on the page <a class="external" href="https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100Build">https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100Build</a><br />I got this output when trying to sign the build ofr i9100:</p>
<pre><code class="text syntaxhl">$ ./vendor/replicant/sign-build i9100
rewriting BOOT/RAMDISK/default.prop:
replace: ro.bootimage.build.fingerprint=replicant_i9100:6.0.1/MOI10E/eng.debian.20180101.161037:userdebug/test-keys
with: ro.bootimage.build.fingerprint=replicant_i9100:6.0.1/MOI10E/eng.debian.20180101.161037:userdebug/release-keys
rewriting RECOVERY/RAMDISK/default.prop:
replace: ro.bootimage.build.fingerprint=replicant_i9100:6.0.1/MOI10E/eng.debian.20180101.161037:userdebug/test-keys
with: ro.bootimage.build.fingerprint=replicant_i9100:6.0.1/MOI10E/eng.debian.20180101.161037:userdebug/release-keys
replace: ro.build.display.id=replicant_i9100-userdebug 6.0.1 MOI10E eng.debian.20180101.161037 test-keys
with: ro.build.display.id=replicant_i9100-userdebug 6.0.1 MOI10E eng.debian.20180101.161037
replace: ro.build.tags=test-keys
with: ro.build.tags=release-keys
signing: org.cyanogenmod.platform-res.apk (/home/debian/replicant/replicant-6.0/vendor/replicant-security/platform)
java.io.FileNotFoundException: /home/debian/replicant/replicant-6.0/vendor/replicant-security/platform.x509.pem (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at com.android.signapk.SignApk.readPublicKey(SignApk.java:160)
at com.android.signapk.SignApk.main(SignApk.java:908)
()
ERROR: signapk.jar failed: return code 1
()
</code></pre>
<p>How could I solve this issue?</p>
<p>Thank you.</p>
<p>For information, this issue follow a former issue (<a class="external" href="https://redmine.replicant.us/issues/1857">https://redmine.replicant.us/issues/1857</a>) which is now solved since the script is now foundable.</p> Replicant - Issue #1865 (Closed): Galaxy S 2 (I9100) compass calibration : replicant restarthttps://redmine.replicant.us/issues/18652018-01-16T20:33:09ZFil Lupinfillupin@protonmail.com
<p>Hello,<br />on my replicant 4.2, I tried to follow steps described on page <a class="external" href="https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100CompassCalibration">https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100CompassCalibration</a> to calibrate compass.<br />I first ran adb root, and when launching first step "adb shell stop zygote", replicant restart and stay on replicant logo. I have then to stop the device (long press on off) and start it again.</p>
<p>Moreover, there is no file /data/misc/akfs.txt which is removed on step 2.</p>
<p>These steps seemed to have been written for replicant 4.2, so is there something else to do?</p> Replicant - Issue #1864 (Closed): after installation of replicant 4.2, sdcard is invisiblehttps://redmine.replicant.us/issues/18642018-01-16T16:44:56ZFil Lupinfillupin@protonmail.com
<p>Hi,<br />after installing Replicant 4.2 on my i9100, my sdcard is not visible.<br />Formerly, I installed Replicant 6 with an encrypted partition and did not unencrypted this partition. Then I did not succeed into accessing SDcard from recovery. Perhaps is it linked (see <a class="external" href="https://redmine.replicant.us/boards/3/topics/14711">https://redmine.replicant.us/boards/3/topics/14711</a>).</p>
<p>However, since android seems not to encrypt sdcard, it should not.</p>
<p>Currently, I do not have some crash si I'm not sure that adb logcat would be useful bute here are some informations I gathered:</p>
<pre><code class="text syntaxhl">root@android:/ # ls -la /dev/block/vold/
brw------- root root 179, 0 2018-01-16 00:17 179:0
brw------- root root 179, 1 2018-01-16 00:17 179:1
brw------- root root 179, 2 2018-01-16 00:17 179:2
brw------- root root 179, 3 2018-01-16 00:17 179:3
brw------- root root 179, 4 2018-01-16 00:17 179:4
brw------- root root 179, 5 2018-01-16 00:17 179:5
brw------- root root 179, 6 2018-01-16 00:17 179:6
brw------- root root 179, 7 2018-01-16 00:17 179:7
brw------- root root 259, 0 2018-01-16 00:17 259:0
brw------- root root 259, 1 2018-01-16 00:17 259:1
brw------- root root 259, 2 2018-01-16 00:17 259:2
brw------- root root 259, 3 2018-01-16 00:17 259:3
brw------- root root 259, 4 2018-01-16 00:17 259:4
</code></pre>
<pre><code class="text syntaxhl">1|root@android:/ # df
Filesystem Size Used Free Blksize
/dev 395.5M 48K 395.5M 4096
/mnt/secure 395.5M 0K 395.5M 4096
/mnt/asec 395.5M 0K 395.5M 4096
/mnt/obb 395.5M 0K 395.5M 4096
/mnt/fuse 395.5M 0K 395.5M 4096
/system 503.9M 242.5M 261.4M 4096
/cache 98.4M 54.9M 43.5M 4096
/efs 19.7M 8.1M 11.5M 4096
/data 2G 342M 1.6G 4096
/preload 503.9M 96.1M 407.8M 4096
</code></pre>
<pre><code class="text syntaxhl">root@android:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p12 /preload ext4 ro,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
</code></pre>
<pre><code class="text syntaxhl">root@android:/ # echo $EXTERNAL_STORAGE
/storage/sdcard0
</code></pre>
<pre><code class="text syntaxhl">root@android:/ # cat fstab.smdk4210
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 ro,nosuid,nodev,noatime wait
</code></pre>
<p>Thank you for your help.</p> Replicant - Issue #1862 (Closed): incompatibility between recovery 4.2 build and recovery 6 buildhttps://redmine.replicant.us/issues/18622018-01-10T13:55:37ZFil Lupinfillupin@protonmail.com
<p>Hello,<br />linked to thread <a class="external" href="https://redmine.replicant.us/boards/3/topics/14711?r=14730">https://redmine.replicant.us/boards/3/topics/14711?r=14730</a>, I have a problem on my GT-I9100 (Galaxy S2):</p>
<ul>
<li>When installing the recovery builded for Replicant 6, I can install Replicant 6 through adb sideload or through an image installed on sdcard.</li>
<li>when installing the recovery builded for Replicant 4.2, it is impossible to mount /emmc and /sdcard, neither can I use adb sideload.</li>
</ul>
<p>To solve this, it seems to me I need insights of replicant 4.2 and 6 experts (Paul and Wolfgang?).</p>
<p>I am stucked without any phone since now 45 days, I desperatly need some help.</p> Replicant - Issue #1857 (Closed): sign-build script absenthttps://redmine.replicant.us/issues/18572017-12-30T00:05:28ZFil Lupinfillupin@protonmail.com
<p>Signing image is not possible since script is not found anywhere in the repo.</p>
<pre><code class="text syntaxhl">./vendor/replicant/sign-build i9100
</code></pre>
<p>This seems to not depend on the device.<br />Do you know where we can find this script?</p> Replicant - Issue #1838 (New): Replicant 6 not responsivehttps://redmine.replicant.us/issues/18382017-09-30T11:01:54ZFil Lupinfillupin@protonmail.com
<p>I install Replicant 6 and noticed that it is not responsive. For instance, when opening some apps (Contacts, Silence, Amaze...) it took up to 6 seconds. <br />It is very annoying since Replicant keep memory of the click so when opening an app and then touching the screen, after the 6 seconds delay for opening the app, it applies the click (it can call a contacts for instance).<br />It seems the display is slow but the rest is OK since commands are launched before the effect displayed.</p>
<p>I exchanged on the Replicant 6 User Experience thread [[<a class="external" href="https://redmine.replicant.us/boards/9/topics/14234?r=14515#message-14515">https://redmine.replicant.us/boards/9/topics/14234?r=14515#message-14515</a>]] with Xan VFR which give me some idea of tests.</p>
<p>When it took 6 seconds to open Contacts and I close Contacts app (Home button pushed during a few seconds), then I can reopen Contacts instantaneously.<br />I also noticed that the 6 seconds delay does not occur after opening an app for the second time: it seems to occur after some delay, of after a number of opening. I did not succeed to understand this process.</p>
<p>A trivial solution is so to close each app before using it but it does not seem a good one.</p> Replicant - Issue #1826 (Closed): cannot find zipfile directoryhttps://redmine.replicant.us/issues/18262017-08-14T20:17:15ZFil Lupinfillupin@protonmail.com
<p>Hello,<br />when trying to download the replicant 4.2 sources according to <a class="external" href="https://redmine.replicant.us/projects/replicant/wiki/ReplicantSourceCode#DownloadingUpdating-the-source-code">https://redmine.replicant.us/projects/replicant/wiki/ReplicantSourceCode#DownloadingUpdating-the-source-code</a> I launched <br /><pre>
vendor/replicant/get-prebuilts
</pre></p>
<p>and got the following output:<br /><pre>
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4672k 100 4672k 0 0 1699k 0 0:00:02 0:00:02 --:--:-- 1699k
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 229 100 229 0 0 458 0 --:--:-- --:--:-- --:--:-- 459
Archive: vendor/replicant/prebuilt/common/apps/TerminalEmulator.apk
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of vendor/replicant/prebuilt/common/apps/TerminalEmulator.apk or
vendor/replicant/prebuilt/common/apps/TerminalEmulator.apk.zip, and cannot find vendor/replicant/prebuilt/common/apps/TerminalEmulator.apk.ZIP, period.
</pre><br />and indeed, here is the content of vendor/replicant/prebuilt/common/apps/ directory:<br /><pre>
$ ls vendor/replicant/prebuilt/common/apps/
FDroid.apk TerminalEmulator.apk
</pre></p>
<p>Is it possible the wiki is documented for replicant 6 and failed for replicant 4.2?<br />Do you know what</p> Replicant - Issue #1817 (Feedback): loose root access and developer optionshttps://redmine.replicant.us/issues/18172017-06-28T06:01:45ZFil Lupinfillupin@protonmail.com
<p>Hello,<br />I installed replicant 6 a few days ago on my i9300.</p>
<p>I remember having accessed to several options which disappeared, for instance, when accessing Settings/developer option, I currently got "developer options are not available for this user" message while I remember getting a complete menu.</p>
<p>I also can't configured my phone to access it as a USB keystick. I simply can't find the option I used a few days ago.<br />I can't access to Settings/User option, it does not open.</p>
<p>In Settings/About phone, when clicking 7 times on Kernel version, I got a "Device Id is not available on this build" and SELinux is defined to enforcing (it seems to me it was different after installation but I am not sure).<br />However I am sure I had these rights after installation since I got adb access and USB keystick access to transfer files.<br />I can not access to my phone with adb, I do not know if this is linked.</p>
<p>Could it be my device which has been "unrooted" during process? I had to flash modem image back when I had EFS problem.<br />I have access to recovery and download mode.<br />At least, I need to access my phone as USB keystick to save backup and install the phone again. <br />Do you know how to do that?</p>
<p>Thank you for your help.</p>