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 - Feature #1737 (Rejected): Tips for unlock deviceshttps://redmine.replicant.us/issues/17372016-07-18T18:16:37ZAnonymous
<p>Numerous websites are offering services to unlock the device. It is necessary to <a href="https://www.safeunlockcode.com" class="external">secure safe phone unlocking</a> to avoid any inconvenient result. In addition, some mobile phone can be unlocked for free; however, other needs the expertise of professional. Once the phone carrier gets locked, you can’t use your phone on another network. However, the process of unlocking is easier than ever before. However, an unlocking phone isn’t a catwalk where every person can handle it easily. When you stuck, it is better to pay and get the desired code. It’s pretty simple, cost-effective and time-effective.</p> Replicant - Issue #1725 (Closed): reboot after installing 0004 on Samsung Galaxy S I9000https://redmine.replicant.us/issues/17252016-06-29T00:20:09ZFil Lupinfillupin@protonmail.com
<p>After following instructions of page <a class="external" href="http://redmine.replicant.us/projects/replicant/wiki/GalaxySI9000Installation">http://redmine.replicant.us/projects/replicant/wiki/GalaxySI9000Installation</a> if I follow steps 7 to 9, my phone reboots again and again on recovery mode.<br />To stop it, I just jump from step 7 to 10 and it fixes this, rebooting on replicant.</p>
<p>By the way, step 7 is called 8.</p> Replicant - Issue #1713 (Closed): build error with I9300 and 4.2 0004https://redmine.replicant.us/issues/17132016-06-20T05:25:17ZFil Lupinfillupin@protonmail.com
<p>Hi, I tried yesterday to build replicant-4.2 on my xubuntu, but building failed with attached output.<br />Do you have any idea what's the problem?</p> Replicant - Issue #1689 (Rejected): Blueooth required by leading bone conduction headsetshttps://redmine.replicant.us/issues/16892016-05-03T17:05:51ZDavid Hedlunddavidh@gnu.org
<p>Some speakers, like bone conduction headsets by Aftershokz (aftershokz.com) reduces the risk for traffic incidents. (read more at <a class="external" href="http://www.bikeshophub.com/blog/2015/07/21/bone-conduction-headphones-safe-legal-or-reckless/">http://www.bikeshophub.com/blog/2015/07/21/bone-conduction-headphones-safe-legal-or-reckless/</a>)</p>
<p>However, this bone conduction headset manufacturer require bluetooth for all of their products, so I cannot use them with Replicant for the moment.</p>
<p>Can you please put this into consideration when you decide to add bluetooth support to Repliant, because this matters.</p>
<p>Thanks.</p> Replicant - Issue #1683 (Closed): All Replicant versions from 4.0.3 to 4.4.4 are vulnerable to th...https://redmine.replicant.us/issues/16832016-04-26T21:17:26Zinge gnueingegnue@riseup.net
<p><a class="external" href="https://www.bluecoat.com/security-blog/2016-04-25/android-exploit-delivers-dogspectus-ransomware">https://www.bluecoat.com/security-blog/2016-04-25/android-exploit-delivers-dogspectus-ransomware</a></p>
<p>"Android device in a lab environment was hit with the ransomware when an advertisement containing hostile Javascript loaded from a Web page."</p> Replicant - Issue #1677 (Closed): Cannot use the camera even if SD card is insertedhttps://redmine.replicant.us/issues/16772016-04-11T12:17:49ZFrancesco Turcofturco@fastmail.fm
<p>I'm using Replicant 4.2 0004 with a Samsung Galaxy S2 I9100 phone. I can't use the camera anymore because I get the following error message:</p>
<blockquote>
<p>Insert an SD card before using the camera.</p>
</blockquote>
<p>I get this error both if I insert a microSD 32GB card and if I don't.</p>
<p>This is the second time I flash Replicant on my phone. When I first flashed it I didn't experience this error.</p>
<p>My knowledge of Android/Replicant/smartphones is still very limited. I may have made some mistake.</p> Replicant - Issue #1623 (Rejected): Check extensively if f-droid repositories still respects the ...https://redmine.replicant.us/issues/16232016-02-04T13:18:44ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<p>The guidelines are here: <a class="external" href="https://www.gnu.org/distros/free-system-distribution-guidelines.html">https://www.gnu.org/distros/free-system-distribution-guidelines.html</a></p>
<p>While I didn't find a smoking gun yet, the following page raises some concern:<br /><a class="external" href="https://f-droid.org/wiki/page/Antifeatures">https://f-droid.org/wiki/page/Antifeatures</a></p>
<p>To check:</p>
<p>1) What, practically speaking, each anti-feature really is.<br /> For instance the description of the advertizing anti-feature says that no applications is known to have it,<br /> but the list of application with that anti-feature is not empty.<br /> We should check with upstream and fix the descriptions if we can.<br />2) Look if Replicant is affected<br /> For instance Firefox exist in f-droid but it's not possible to run on Replicant.<br /> Still, Firefox should not be possible to install on Replicant because it can suggest non-free add ons.<br />3) List and check well known suspicious applications such as firefox.<br />4) List and check emulators, Parabola has a good reference on it here:<br /> <a class="external" href="https://wiki.parabola.nu/Emulator_licensing_issues">https://wiki.parabola.nu/Emulator_licensing_issues</a></p>
<p>If no issues are to be found, Documentation should be made more clear.</p>
<p>If issues are to be found, F-droid will have to be fixed upstream, not to show any application with anti-features to Replicant users.<br />We should also look which implementations would satisfy the guidelines requirements:</p>
<p><del>> Should the filter be made automatic and not possible to disable.<br /></del>> Can the filter be a setting, and be enabled by default on Replicant.<br />-> Can upstream simply remove applications with anti-features?<br />Having F-droid fixed upstream is desirable not to have to maintain a fork.</p> Replicant - Issue #1617 (Rejected): Check extensively if f-droid repositories still respects the ...https://redmine.replicant.us/issues/16172016-02-04T13:17:26ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<p>The guidelines are here: <a class="external" href="https://www.gnu.org/distros/free-system-distribution-guidelines.html">https://www.gnu.org/distros/free-system-distribution-guidelines.html</a></p>
<p>While I didn't find a smoking gun yet, the following page raises some concern:<br /><a class="external" href="https://f-droid.org/wiki/page/Antifeatures">https://f-droid.org/wiki/page/Antifeatures</a></p>
<p>To check:</p>
<p>1) What, practically speaking, each anti-feature really is.<br /> For instance the description of the advertizing anti-feature says that no applications is known to have it,<br /> but the list of application with that anti-feature is not empty.<br /> We should check with upstream and fix the descriptions if we can.<br />2) Look if Replicant is affected<br /> For instance Firefox exist in f-droid but it's not possible to run on Replicant.<br /> Still, Firefox should not be possible to install on Replicant because it can suggest non-free add ons.<br />3) List and check well known suspicious applications such as firefox.<br />4) List and check emulators, Parabola has a good reference on it here:<br /> <a class="external" href="https://wiki.parabola.nu/Emulator_licensing_issues">https://wiki.parabola.nu/Emulator_licensing_issues</a></p>
<p>If no issues are to be found, Documentation should be made more clear.</p>
<p>If issues are to be found, F-droid will have to be fixed upstream, not to show any application with anti-features to Replicant users.<br />We should also look which implementations would satisfy the guidelines requirements:<br /><del>> Should the filter be made automatic and not possible to disable.<br /></del>> Can the filter be a setting, and be enabled by default on Replicant.<br />-> Can upstream simply remove applications with anti-features?<br />Having F-droid fixed upstream is desirable not to have to maintain a fork.</p> Replicant - Issue #1611 (Rejected): repo don't buildhttps://redmine.replicant.us/issues/16112016-02-01T16:59:32ZIgor Kubinski
<p>source build/envsetup.sh<br />lunch replicant_i9100-userdebug<br />make bacon</p>
<p>make: *** No rule to make target `vendor/replicant/prebuilt/common/apps/FDroid.apk', needed by `/mnt/repli/replicant-4.2/out/target/product/i9100/system/app/FDroid.apk'. Stop.</p>
<ol>
<li>export<br />declare -x ANDROID_BUILD_PATHS="/mnt/repli/replicant-4.2/out/host/linux-x86/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin:/mnt/repli/repli<br />cant-4.2/prebuilts/gcc/linux-x86/mips/mipsel-linux-android-4.6/bin:/mnt/repli/replicant-4.2/development/emulator/qtools:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-li<br />nux-androideabi-4.6/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin:/mnt/repli/replicant-4.2/development/scripts:" <br />declare -x ANDROID_BUILD_TOP="/mnt/repli/replicant-4.2" <br />declare -x ANDROID_DEV_SCRIPTS="/mnt/repli/replicant-4.2/development/scripts" <br />declare -x ANDROID_EABI_TOOLCHAIN="/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin" <br />declare -x ANDROID_HOST_OUT="/mnt/repli/replicant-4.2/out/host/linux-x86" <br />declare -x ANDROID_JAVA_TOOLCHAIN="/usr/lib/jvm/java-6-sun/bin" <br />declare -x ANDROID_PRE_BUILD_PATHS="/usr/lib/jvm/java-6-sun/bin:" <br />declare -x ANDROID_PRODUCT_OUT="/mnt/repli/replicant-4.2/out/target/product/i9100" <br />declare -x ANDROID_PROMPT_PREFIX="[arm-replicant_i9100-userdebug]" <br />declare -x ANDROID_QTOOLS="/mnt/repli/replicant-4.2/development/emulator/qtools" <br />declare -x ANDROID_TOOLCHAIN="/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin" <br />declare -x ARM_EABI_TOOLCHAIN="/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin" <br />declare -x BUILD_ENV_SEQUENCE_NUMBER="10" <br />declare -x CM_BUILD="i9100" <br />declare -x HOME="/home/guest" <br />declare -x JAVA_HOME="/usr/lib/jvm/java-6-sun" <br />declare -x OPROFILE_EVENTS_DIR="/mnt/repli/replicant-4.2/external/oprofile/events" <br />declare -x OUT="/mnt/repli/replicant-4.2/out/target/product/i9100" <br />declare -x PATH="/usr/lib/jvm/java-6-sun/bin:/mnt/repli/replicant-4.2/out/host/linux-x86/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/mips/mipsel-linux-android-4.6/bin:/mnt/repli/replicant-4.2/development/emulator/qtools:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin:/mnt/repli/replicant-4.2/development/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" <br />declare -x TARGET_BUILD_APPS="" <br />declare -x TARGET_BUILD_TYPE="release" <br />declare -x TARGET_BUILD_VARIANT="userdebug" <br />declare -x TARGET_PRODUCT="replicant_i9100"</li>
</ol>
<p>There is no git entry for fdroid in default.xml</p>