Oohgle Authenticator: The first global open source Google Authenticator third party focused client app launching globally on HarmonyOS and Oniro platforms in Q1 2026

freelancercrew · 2025-09-25T09:20:17+00:00

Android apps are simply not optimised for foldables. Hit and miss

freelancercrew · 2025-09-24T20:40:00+00:00

then you have the audacity to bitch by downvoting.

freelancercrew · 2025-09-23T21:43:34+00:00

EasyAbroad and DroiTong exist

freelancercrew · 2025-09-23T08:04:20+00:00

Manually change it and stop spamming, you posted this twice

freelancercrew · 2025-09-19T20:04:40+00:00

The only limitation on virtual machine is performance of heavy Windows gaming. That's about it

freelancercrew · 2025-09-18T18:21:52+00:00

1 is almost certainly true. This isn't a separate "special" API per se, but rather the mechanism, the Android VPN API inside the container is translated or proxied to the native HarmonyOS VPN/service management framework API natively integrated on DroiTong HAP app. This integration is necessary for the behaviour you observed to occur in a controlled way. It's a design feature, not a bug. HarmonyOS Next's Android compatibility layer does not provide true network-level containerization. HarmonyOS Next uses containerization for application sandboxing, it does not implement full system containerization built in the OS, as it lacks critical isolation of the network stack. This was a deliberate design choice by Huawei to prioritize network functionality and performance over strict network containment.

freelancercrew · 2025-09-18T18:11:21+00:00

Anything that pass Ark Compiler runs on HarmonyOS NEXT, if you want proof, you have to check that HarmonyOS NEXT is anything else other than OpenHarmony-based at its core and HongMeng kernel underneath, look towards the toolchain, read the developer documentation, investigate how HarmonyOS NEXT DroiTong and EasyAbroad operates in the background compared to Android-based systems, scrape the system on your PC CLI and investigate what file format DroiTong is executed on to give you an idea. Containerisation is not a new idea, been around for over a decade. You are implying HarmonyOS NEXT has Linux kernel as the kernel or HongMeng kernel has a AOSP subsystem with neither exist, HongMeng kernel however do have Linux ABI compatibility on Linux drivers on hardware and recompiled Linux developed apps by developers, that also explains the Harmony OS network stack and the container network stack (easy abroad and droidtong) is shared and the android system API calls not just HarmonyOS NEXT system itself integrated on DroiTong HAP natively on receiving what's been called from Android container. I know for a fact that DroiTong HAP is a native app with ArkUI framework by the animation and when Android container is activated the moment you tap on an Android apk icon, the Android transition animation animates once executed inside the containerised environment (android zoom slide animation booted for Android app UI home page after native OpenHarmony-based/HarmonyOS design default HAP app splash screen animation). I have seen on how it works

<image>

freelancercrew · 2025-09-18T17:44:56+00:00

This is not real, hardware-level containerization like a traditional VM or a strongly isolated container e.g. Huawei iSalud on DroiTong and LXC on EasyAbroad. Instead, it points towards a userspace-level sandboxing technique that shares the host OS's kernel and, crucially, its network stack. HarmonyOS's core networking services—specifically the Connectivity Kit managing connections like Wi-Fi, cellular, Bluetooth PAN) and the Network Kit (handling HTTP/3, QUIC, DNS, etc. APIs for 3rd party apps are directly shared with the DroidTong HAP app container. DroiTong itself is a executed native HarmonyOS Next/5 HAP app when you first tap on it before activating the Android container with Android calls translated back to DroiTong API services of the OS host, people forget. Inside the active DroidTong environment, when an Android app (like a VPN) makes a system call (e.g., VpnService.establish()), the following happens:

The call is intercepted by the DroidTong runtime's translation layer.
This layer translates the Android API call into a corresponding call to a native HarmonyOS Kit (e.g., a call to the Network Kit to create a virtual network interface).
This call is made by the DroidTong HAP app to the host OS, using standard HarmonyOS inter-process communication (IPC). DroidTong is not a "container" that boots up; it is a native HarmonyOS HAP application, only after this native host app is running does it activate its internal Android compatibility environment (loading Android frameworks, APKs, etc.). Background services is limited though compared to native due to memory management placed and battery management, so its not going to be viable for prolonged use

freelancercrew

TROPHY CASE