Changelog of the latest version (replicant-6.0-beta-0001 from 27.1.17)¶

llvmpipe has more complete EGL support than the Android software renderer, so more apps work with it, like Firefox-based browser or more recent webviews. Unfortunately, llvmpipe is still too slow to be the default renderer, but I made it possible to switch back and forth between llvmpipe and the Android software renderer. ADB and root over ADB needs to be enabled in the developer settings.

Some SIM cards are not recognized. If you want to help debugging this, do the following: Run adb logcat -d -b radio > replicant_radio_log.txt after the device booted. Install CyanogenMod 13.0 and capture the same log. The output of adb shell dmesg after CyanogenMod has booted could be helpful, too. You can send the logs in a PM as they can contain personal information.

Only the Galaxy S2 and S3 are supported. If you want to help getting other Replicant devices supported: Add the missing device repositories and try to merge the changes from CyanogenMod. If the device is not supported on the CyanogenMod 13.0 branch, you will have to look at forks that took up the development. Merging with an older branch could also be sufficient to get basic functionality working.

Newer webviews can't be used because they don't work with the software rendering Webview version 43.0.2357.134 is currently in use. It was released in July 2015. This can be fixed by making llvmpipe fast enough so it can be used as the default software renderer. Currently, the Android software renderer is the default.

There are still prebuilt binaries in the source tree I got rid of a lot of prebuilt binaries to make the build more trustworthy and to ensure that all tools are properly built from source with free software, but there are still a few left. The gcc-arm-linux-androideabi toolchain needs to be bootstrapped with proper 1st and 2nd stage compilers so it doesn't rely on the sysroot from the NDK. In general, there are still some prebuilt binaries from the NDK, SDK and other places in use, but nearly all of them shouldn't run on the host, but only on the Replicant device.

Please note that the build might even be broken on this branch and there are no git tags on this branch which pin the source code to certain versions.

Then download the source code:

repo sync

The F-Droid binary is downloaded separately. The download script will check if the signature of the F-Droid binary comes from the F-Droid release signing key. You can retrieve the current signing key with the command gpg --recv-key 7A029E54DD5DCE7A. Run the download script to get F-Droid:

./vendor/replicant/get-prebuilts

Before you can build the ROM in the regular way, you need to run a build script that takes care of building the toolchain:

./vendor/replicant/build-toolchain

In order to prevent strange errors, I recommend running the script in a newly opened shell, in which you haven't already run one of the commands like . build/envsetup.sh, lunch or make that change the environment.

Then you can run the regular build commands to create a Replicant 6.0 zip and recovery:

I also added a script that signs your build, takes care of generating the necessary keys and puts everything in the out/dist directory. Using this script, it is possible to rely on your own keys and not on the test keys which are not recommended to use because the private test keys are publicly available. Building from source and flashing the default image that is signed with the test keys basically disables all the security measures in Android that are based on signing keys. The script also makes it possible to use password-encrypted private keys. The images below are signed with my keys using this script. You can run the script the following way:

./vendor/replicant/sign-build i9100

And finally you can flash the recovery in the download mode and sideload the zip in recovery mode:

If you have already built Replicant at some point and now you are getting build errors: Run make clobber and retry in a newly opened shell.If make fails, it may be necessary that run mka org.cyanogenmod.platform-res.

Add my key to your GPG keyringYou can retrieve it from the keyserver of your choice (gpg --recv-key 5816A24C10757FC4).Alternatively, you can download it from here: https://wiedmeyer.de/keys/ww.ascand import it with gpg --armor --import path/to/5816A24C10757FC4.ascThe key should have the following fingerprint: 0F30 D1A0 2F73 F70A 6FEE 048E 5816 A24C 1075 7FC4

You need to flash the new recovery first before you can flash the zip to your device. A full wipe is also necessary. Updating your ADB installation might help if you have problems with ADB.See the wiki for more details.

CONGRATULATIONS on this achievement and thanks a lot for all your efforts.

I successfully installed R6.0 on a S2 today. I haven't tried it yet with SIM card and wifi, but these are the next steps.

For now I have (at least) one issue: Under 'storage' I have 'Internal storage', sdcard0 and sdcard1. More or less by mistake I had my sdcard1 formatted as internal storage. The problem is that my sdcard0 is claimed to be corrupted and when I try to format it I get this error message: . The "55" number goes up one for each try (I haven't tried 55 times though!).

I had this error message both before and after farmatting sdcard1 as internal storage.

I had the same problem as Jacob Bahn. I ended up having to downgrade to Replicant 4.2 0004 to fix it. Replicant 4.2 0004 is able to format the "SD card", rendering it usabe but blank, but Replicant 6.0 fails every time that I try to have it format the "SD card". The error message is "command '13 9 volume partition disk: 179_0 public' failed with '400 15 Command failed'". Like Jacob, I'm unable to use the camera because of this.

Also of note, Replicant 6.0's recovery isn't able to read ext4 SD cards. I had to wipe my SD card and format it to even install Replicant 6.0. Replicant 4.2 0004's revovery, on the other hand, can read ext4 SD cards perfectly.

On the S2: Due to the mentioned memory problem, I can't take pictures with the standard camera app. Apparently it won't even start up, if it doesn't have access to memory. And it seems that memory location cannot be changed to e.g. external sdcard.

I downloaded another camera app from f-droid which stats up and let's me take pictures, only it's not saved. There is a configuration menu in which I can change memory location. Unfortunatly not to external sdcard and with the internal: Same issue.

One interesting thing though: I opposition to R6.0 on S3 and R4.2 on S2 I can use the front camera (but of course with no access to memory)

You can't access the front camera on the GT-i9100 (SII) on Replicant 4.2 0004? Strange; I can. I've never had a use for the front camera, but I've seen that it works on my device.

I had that same problem with the GT-i9100 (SII) with a camera application from F-Droid. Open Camera didn't complain about the lack of storage, so I thought that I'd found a workaround. Instead, I took a bunch of photographs, expected them to be there, and after it was too late to retake them, I found that they hadn't been saved.

..don't know if this is the right place to ask..Also.. I know that this is not at all a priority, but I'm going to give my unwanted advice anyway :)

Due to the developing of the RepWifi application (alpha is coming soon!), I'm working quite a lot with the terminal app in Replicant 6, these days..While it is functioning without any particular issue, I found out that the default terminal in Replicant 6 is very limited, and lacks all the features that made the "Terminal Emulator" app so easy and painless to use, such as basic key bindings that help writing numerous long commands less stressful.

I think I'm going to install Terminal Emulator via the apk anyway, but I just wanted to ask if it would be possible to switch to "Terminal Emulator" app as the default terminal in future releases of Replicant 6.0..Is there any non-trivial work to be done to include it as the default app?If not, I suggest using it, as I find it way more powerful and complete.

For now I have (at least) one issue: Under 'storage' I have 'Internal storage', sdcard0 and sdcard1. More or less by mistake I had my sdcard1 formatted as internal storage. The problem is that my sdcard0 is claimed to be corrupted and when I try to format it I get this error message: . The "55" number goes up one for each try (I haven't tried 55 times though!).

You could try the updated images. They should include some file system checks that run as part of the installation. If the issue persists, you could try the following:

Install LineageOS and check if the issue is there, too.

Do some research (e.g. enter the error message into your favorite search engine) and report back if some of the solutions that turn up work.

While it is functioning without any particular issue, I found out that the default terminal in Replicant 6 is very limited, and lacks all the features that made the "Terminal Emulator" app so easy and painless to use, such as basic key bindings that help writing numerous long commands less stressful.

Indeed, it's quite a minimal terminal app.

I think I'm going to install Terminal Emulator via the apk anyway, but I just wanted to ask if it would be possible to switch to "Terminal Emulator" app as the default terminal in future releases of Replicant 6.0..Is there any non-trivial work to be done to include it as the default app?If not, I suggest using it, as I find it way more powerful and complete.

The internal terminal app is coupled to the settings and I think one of the reasons is the possibility to enable/disable it depending on certain user profiles. So it's probably some work to get rid of it. I prefer to build the default apps in Replicant from source. Currently, only the F-Droid app is downloaded and not built from source. Adding the Terminal Emulator would add another app that is downloaded and where we'd have to keep up with version changes. Given all of this, I'd like to keep it as it is for now. As you wrote, it's trivial to install the Terminal Emulator from F-Droid. But what we could do is to set up a wiki page with recommended apps that "enhance the Replicant experience" or are otherwise particular useful to Replicant users and list apps like the Terminal Emulator there.

The internal terminal app is coupled to the settings and I think one of the reasons is the possibility to enable/disable it depending on certain user profiles. So it's probably some work to get rid of it. I prefer to build the default apps in Replicant from source. Currently, only the F-Droid app is downloaded and not built from source. Adding the Terminal Emulator would add another app that is downloaded and where we'd have to keep up with version changes. Given all of this, I'd like to keep it as it is for now. As you wrote, it's trivial to install the Terminal Emulator from F-Droid. But what we could do is to set up a wiki page with recommended apps that "enhance the Replicant experience" or are otherwise particular useful to Replicant users and list apps like the Terminal Emulator there.

All that makes sense, indeed!I strongly agree with avoiding other pre-built apps.Thanks for explaining!

i have installed Replicant 6.0 on my Samsung Galaxy S2 (GT-I9100) with the Recovery from CWM (CWM-KitKatCompatible-i9100.tar).The Superuser Apps from F-Droid can be installed, but do not work properly as it should be.There is no Apps list in Superuser App, for management and more.I have installed the Superuser App from "Superuser Version 1.0.3.0".(Link: https://f-droid.org/repository/browse/?fdfilter=superuser&fdid=com.koushikdutta.superuser)

But it did not work fine, i get the message: "The Superuser binary (su) must be updated. Pleae choose an installation method.Recovery mode installation is recommended for HTC devices".I choose the "Recovery" method, after reboot the Superuser binary (su) is not upated.

If i start the App "Lil' Debi", it displays a message: "Status: Lil' Debi needs root access install Superuser, GET SUPERUSER...".I get the message without the Superuser App from Version 1.0.3.3 and with Root Access (Apps and ADB) too.But with the App from "Superuser Version 1.0.3.0" the message is not displayed.Both Superuser Apps did not work right on my Samsung Galaxy S2 (GT-I9100).

What can i do to get the App Superuser on the Replicant 6.0 running, please?

I don't know what the "Superuser App" is really all about, but I guess it's just a workaround for phones that are not "rooted" (correct me if I'm wrong).That said, I don't see why you would ever need such an app in Replicant, as it already comes with "su" command built in, which makes it possible to run applications that need root privileges.

What you're maybe missing, is that you need to explicitly enable root for applications. Go to:

Settings > Developer options > Root access

and select the option that suits you best. I suggest you give root access to "Apps only".You could later enable it for ADB if you really need it in the future.