treble_experimentations

Pros of Magisk

• More comprehensive root solution with modules ecosystem
• Active development and frequent updates
• Larger user base and community support

Cons of Magisk

• Primarily focused on rooting and system modifications
• May not be suitable for all devices or custom ROM scenarios
• Potentially higher risk of security vulnerabilities due to root access

Code Comparison

Magisk (init.cpp):

static int magisk_proxy_main(int argc, char *argv[]) {
    setup_klog();
    LOGI(NAME_WITH_VER(Magisk) " init proxy started\n");
    rust::init_proxy_main();
    return 1;
}

Treble_experimentations (build-dakkar.sh):

if [ "$CLEAN" == "true" ]; then
    make clean
fi

. build/envsetup.sh
lunch "$LUNCH_CHOICE"
make $MAKEJ otapackage

While both projects aim to enhance Android functionality, Magisk focuses on providing root access and system-level modifications, whereas Treble_experimentations is geared towards custom ROM development and Project Treble compatibility. Magisk offers a more user-friendly approach for system modifications, while Treble_experimentations provides tools for ROM developers to create GSI (Generic System Image) builds.

Pros of GmsCore

• Provides a privacy-focused alternative to Google Play Services
• Lightweight implementation of core Google services
• Allows using Google-dependent apps without full Google ecosystem

Cons of GmsCore

• May not support all Google Play Services features
• Requires more setup and configuration than stock Android
• Potential compatibility issues with some apps

Code Comparison

GmsCore:

public class GmsCore extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        // Initialize microG services
    }
}

Treble_experimentations:

#!/system/bin/sh
# Apply Treble-specific patches
mount -o rw,remount /system
# Apply system modifications

The code snippets highlight the different focus areas:

• GmsCore centers on providing a Google services alternative
• Treble_experimentations focuses on system-level modifications for Project Treble compatibility

GmsCore is a specialized project for replacing Google services, while Treble_experimentations is broader in scope, aiming to improve Android device compatibility and customization across various devices and ROMs.

Pros of Shizuku

• Focuses on providing a secure way to access system APIs on Android
• Offers a more user-friendly approach for non-root users
• Actively maintained with regular updates and improvements

Cons of Shizuku

• Limited scope compared to Treble_experimentations' broader focus on custom ROMs
• May require more setup for users unfamiliar with ADB commands
• Less flexibility for system-wide modifications

Code Comparison

Shizuku (Java):

@RequiresPermission(INTERACT_ACROSS_USERS)
public static UserHandle getUserHandle(int userId) {
    return UserHandle.of(userId);
}

Treble_experimentations (Shell script):

if [ -f /vendor/build.prop ]; then
    VENDOR_FINGERPRINT="$(grep -F "ro.vendor.build.fingerprint" /vendor/build.prop | sed "s/.*=//")"
fi

While both projects deal with Android customization, Shizuku focuses on API access, using Java for its implementation. Treble_experimentations, on the other hand, utilizes shell scripts for system-level modifications and custom ROM development. The code snippets highlight these differences in approach and scope.