Fibonas, Microg , GBOX | Siapa sih Mereka ?!

Technological context: Why Google apps are complicated on Huawei

• Since 2019, after Huawei and affiliates were placed on the US Entity List (trade war/trade restrictions), US tech companies can’t license or serve Huawei.
• Impact on Huawei devices:
  • Huawei can’t get Google Mobile Services (GMS) (e.g., Play Store and related Google service licensing).
  • US components are also restricted (the subtitles mention Snapdragon, Micron, Hynix, and limits around chips/RAM from US manufacturers).

“Android exists, but it’s not the same as normal Android”

The speaker distinguishes between:

• Android / AOSP (open source) Huawei can still use this because it’s open.

• A “native Android experience” with Google services This requires licensed Google utilities (e.g., Play services, Play Integrity/Protect, cloud messaging, login, payments, etc.). Because Huawei can’t legally/technically fully include standard GMS, the “Android version” shown (e.g., Android 12/16) doesn’t automatically mean full Google functionality.

Huawei’s workaround evolution (solutions over time)

1. Early workaround: Phone cloning

   • “Phone clone” transferred contacts/photos/files (and some apps).
   • Google-dependent apps often failed (e.g., notifications, lag, crashes).

2. “Web shortcut” approach

   • Example: adding a browser shortcut (e.g., a youtube.com shortcut) to approximate app behavior.
   • Still “around the problem,” not true native support.

3. App ecosystem push: App Gallery + HMS Core

   • After sanctions, Huawei focuses on App Gallery and HMS Core.
   • Developers must do more than upload an APK: they need equivalents for login, push notifications, security, payments, maps, analytics, and more.

4. Petal Search / app sourcing

   • Petal Search can surface apps from sources outside App Gallery (often APK Pure or other APK sources).
   • But installing an APK doesn’t guarantee Google services will run, because Huawei lacks full GMS.

The “three solutions” for Google apps on Huawei (Fibonacci, MicroG, GBox)

The video claims these are widely used—especially in Asia (e.g., Malaysia/Indonesia).

1) MicroG

• Presented as community/open-source, not a Huawei original.
• Goal: provide Google functionality in a more privacy-oriented way (the speaker claims it can be less trackable than full Google GMS).
• Since it’s open source, the community can audit the code.
  • The speaker warns to download from official GitHub only.
• Limitations:
  • It covers only parts of Google services (example mentioned: notification-related service).
  • It may not cover complex workflows like Play Protect/Integrity end-to-end.

2) Fibonas / Fibonacci (name unclear in subtitles)

• Intended role: searching/browsing inside App Gallery (the speaker claims MicroG can’t do this).
• The speaker suspects Huawei may have funded it but couldn’t publish details due to sanctions (no solid evidence provided).

3) GBox / Google Box

• Described as a virtualized/container “fake Android” environment to run Google apps that otherwise wouldn’t work.
• Comparison: like an emulator/container—apps run “inside a room” that simulates a Google-like environment rather than being truly native to Huawei.
• Practical but not perfect:
  • Possible performance/battery/RAM overhead.
  • Not all features work reliably.

Key risks and limitations mentioned

• Not native → compatibility problems

  • Examples mentioned in the subtitles: WhatsApp errors, notification reliability issues, and some payment/security integrations failing.
  • Google Wallet + NFC “clearly don’t work.”
  • Android Auto is difficult.
  • Uncertainty about connecting to WearOS smartwatches.

• Update lag

  • Licensed Android gets Google updates quickly via Play Store.
  • Non-native/virtualized approaches (like GBox) may update slower, delaying compatibility.

• Safety/data concerns are a “grey area”

  • The speaker claims they found no major open reports of widespread “Hacked/bridged” Huawei devices via GBox (based on “deep research with AI/ChatGPT”).
  • However, the speaker refuses certainty: safety depends on probability, and data theft is not guaranteed—or provably absent.

Review / guidance emphasis from the speaker

• If you want Google-native app behavior, the device must effectively have full licensed Google services—otherwise it’s not truly “native.”
• For users: research each app’s compatibility, especially for banking/payments/DRM/NFC/auto integrations.
• If you use MicroG: download only from official GitHub to avoid tampered builds.
• Overall framing: Huawei users (especially post-2019) accept tradeoffs—good hardware with ecosystem compromises.

Main speakers / sources (as stated)

• The subtitles reference a single recurring narrator/host: “Sik Budi” (ends with “Sik Budi and see you…”).
• No other named speaker is clearly presented; technical components (MicroG, Petal, GBox) are discussed as products/systems rather than people.