diff --git a/Teracube/2e/Android.mk b/Teracube/2e/Android.mk
new file mode 100644
index 0000000..af6fd3c
--- /dev/null
+++ b/Teracube/2e/Android.mk
@@ -0,0 +1,8 @@
+LOCAL_PATH := $(call my-dir)
+include $(CLEAR_VARS)
+LOCAL_MODULE_TAGS := optional
+LOCAL_PACKAGE_NAME := treble-overlay-teracube-2e
+LOCAL_MODULE_PATH := $(TARGET_OUT_PRODUCT)/overlay
+LOCAL_IS_RUNTIME_RESOURCE_OVERLAY := true
+LOCAL_PRIVATE_PLATFORM_APIS := true
+include $(BUILD_PACKAGE)
diff --git a/Teracube/2e/AndroidManifest.xml b/Teracube/2e/AndroidManifest.xml
new file mode 100644
index 0000000..05f6923
--- /dev/null
+++ b/Teracube/2e/AndroidManifest.xml
@@ -0,0 +1,10 @@
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+        package="me.phh.treble.overlay.teracube.2e"
+        android:versionCode="1"
+        android:versionName="1.0">
+        <overlay android:targetPackage="android"
+                android:requiredSystemPropertyName="ro.vendor.build.fingerprint"
+		android:requiredSystemPropertyValue="+Teracube/Teracube_2e*"
+		android:priority="312"
+		android:isStatic="true" />
+</manifest>
diff --git a/Teracube/2e/res/values/config.xml b/Teracube/2e/res/values/config.xml
new file mode 100644
index 0000000..18608cc
--- /dev/null
+++ b/Teracube/2e/res/values/config.xml
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="utf-8"?>
+<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
+    <!-- Boolean indicating whether the wifi chipset has dual frequency band support -->
+    <bool translatable="false" name="config_wifi_dual_band_support">true</bool>
+
+    <!-- The bounding path of the cutout region of the main built-in display.
+    Must either be empty if there is no cutout region, or a string that is parsable by
+    {@link android.util.PathParser}.
+    The path is assumed to be specified in display coordinates with pixel units and in
+    the display's native orientation, with the origin of the coordinate system at the
+    center top of the display.
+    To facilitate writing device-independent emulation overlays, the marker `@dp` can be
+    appended after the path string to interpret coordinates in dp instead of px units.
+    Note that a physical cutout should be configured in pixels for the best results.
+    -->
+    <string translatable="false" name="config_mainBuiltInDisplayCutout">
+        M 0,0
+        L -90, 0
+        L -90, 20
+        Q -90, 36 -74, 36
+        L 74, 36
+        Q 90, 36, 90, 20
+        L 90, 0
+        Z
+        @dp
+    </string>
+    <!-- Whether the display cutout region of the main built-in display should be forced to
+         black in software (to avoid aliasing or emulate a cutout that is not physically existent).
+     -->
+    <bool name="config_fillMainBuiltInDisplayCutout">false</bool>
+    <!-- Height of the status bar -->
+    <dimen name="status_bar_height_portrait">36dp</dimen>
+    <dimen name="status_bar_height_landscape">28dp</dimen>
+    <!-- Height of area above QQS where battery/time go (equal to status bar height if > 48dp) -->
+    <dimen name="quick_qs_offset_height">36dp</dimen>
+</resources>
diff --git a/overlay.mk b/overlay.mk
index bd6adc3..be30faa 100755
--- a/overlay.mk
+++ b/overlay.mk
@@ -118,6 +118,8 @@ PRODUCT_PACKAGES += \
 	treble-overlay-telephony-mtk-ims \
 	treble-overlay-telephony-slsi-ims \
 	treble-overlay-telephony-sprd-ims \
+	treble-overlay-teracube-2e \
+	treble-overlay-teracube-v7101o \
 	treble-overlay-tethering \
 	treble-overlay-umidigi-A3S \
 	treble-overlay-umidigi-power \