GCam FAQs and Troubleshooting Tips (Complete Guide)

The most common reason GCam crashes on Android isn’t actually a bug in the app. It’s a mismatch between the GCam build and your phone’s Camera2 API level. Out of every troubleshooting question I’ve seen on the XDA Forums GCam threads, roughly 7 out of 10 trace back to four root causes: Camera2 API not enabled, the wrong GCam build for your chipset, a missing or wrong XML config file, or simply not enough free storage. This page is the field guide I wish someone had handed me the first time I installed GCam.

Use the table of contents below to jump to the symptom that matches your phone. Every fix here is tested. None of them need root unless I say so directly.

Key Takeaways

  • Most install failures = Camera2 API issue. Check it first before trying anything else.
  • Black preview screen almost always means the GCam build is wrong for your chipset (Snapdragon vs MediaTek vs Exynos).
  • Crashes on launch usually fix themselves by dropping back to a slightly older 9.x build.
  • Pink, green, or washed-out colors mean you’re missing the XML config file for your exact phone model.
  • Every fix on this page works without root, unless I explicitly say otherwise.

Quick Diagnostic: Match Your Symptom

Before reading any deeper, find your problem in the list below. Each one links down to the section that fixes it.

  • APK won’t install at all → see Installation Problems below
  • App opens then immediately crashes → see Crashes and Freezing
  • Black or frozen viewfinder → see Camera2 API Issues
  • Photos look pink, green, or washed out → see Image Quality Issues
  • Night Sight does nothing or freezes → see Crashes and Freezing
  • Can’t find where to load config files → see Configuration File Issues

Installation Problems

The APK won’t install

Nine times out of ten, this is one of two things. First, your phone’s Android version is too old for that GCam build. Most modern GCam 9.x releases need Android 12 or newer. If you’re on Android 10 or 11, look for an 8.x build that matches your phone instead.

Second, you haven’t enabled “Install unknown apps” for your browser or file manager. Go to Settings → Apps → Special access → Install unknown apps, find the app you’re installing from (usually Chrome or Files), and turn the permission on.

It says “app not installed” with no real error

This usually means a different version of GCam is already on the phone and the signatures don’t match. Uninstall the existing GCam first (long-press the icon → App info → Uninstall), then install the new APK. Your photo gallery is safe. The configs in your storage are also safe.

Play Protect blocks the install

Tap “Install anyway” if Google Play Protect shows a warning. GCam ports from BSG, Greatness, Wichaya, and similar known modders are not malicious, but Play Protect doesn’t recognize the unsigned APK as a known developer. If you’d rather skip the warning, you can pause Play Protect from Play Store → profile icon → Play Protect → settings.

Camera2 API Issues

Camera2 is the Android API that lets apps talk directly to the camera sensor. GCam was built on top of it. If your phone has it disabled or restricted by the manufacturer, GCam can’t get full access to the lenses, and you’ll get a black viewfinder or only a partial feature set.

How to check if Camera2 is enabled

Install a free app called “Camera2 API Probe” from the Play Store. Open it. Look at the value next to your main camera ID. You want to see “LEVEL_3” or “FULL”. If it says “LIMITED” or “LEGACY”, you’ll be stuck with a partial GCam experience. The full step-by-step is in our guide on how to check Camera2 API support.

How to enable Camera2 if it’s off

Some phones (especially older Xiaomi, Asus, and some Realme models) need a manual toggle through ADB to flip Camera2 on. The complete walkthrough, including the exact ADB commands, is in our guide to enabling Camera2 API without root.

Most phones from 2022 onwards ship with Camera2 enabled by default, so if your phone is recent, you can skip this section entirely.

Crashes and Freezing

GCam crashes the moment I open it

Try this order:

  • Drop one minor version. If you installed 9.7, try 9.6. The newest build isn’t always the most stable on every phone.
  • Use a build labeled for your chipset. Snapdragon, MediaTek Dimensity, and Exynos each have their own preferred GCam ports. Mixing them is the single biggest cause of immediate crashes.
  • Clear app data. Settings → Apps → GCam → Storage → Clear data. This resets configs and forces a fresh first-run.
  • Reboot once after install. Strange but true: some phones need one reboot before GCam can talk to the camera HAL properly.

GCam freezes when I tap the shutter

This is almost always a RAW or HDR+ setting problem. Open GCam, tap the down arrow at the top, go to Settings → Advanced, and turn off “Save as RAW (DNG)” if it’s on. Try a shot. If it works, leave RAW off until you’re sure your phone has the storage and RAM to handle it (RAW files are 25-50 MB each).

Night Sight starts but never finishes

Night Sight needs you to hold still. Most ports time the exposure between 3 and 6 seconds. If you move, the app sometimes gets stuck trying to align frames. Two fixes:

  • Brace the phone against any flat surface (a railing, a table edge, even a stack of books). Sharpness and reliability both improve a lot.
  • If it still hangs, check Settings → Advanced and turn Astrophotography mode off. On some phones, astro mode loads but never times out.

Image Quality Issues

Photos have a pink, green, or yellow tint

This is the single most common quality complaint and the fix is always the same: you’re using the wrong XML config (or no config at all) for your phone model. The default GCam color science is tuned for Pixel sensors. Your sensor isn’t a Pixel sensor. The fix is loading an XML config that the community has tuned for your exact model.

Photos look soft or blurry

Usually one of these:

  • HDR+ Enhanced is off. Toggle it on. It produces sharper, more detailed shots than the default HDR+ mode, at the cost of a slightly longer shutter delay.
  • Your shutter speed is too long. If GCam is auto-selecting a long exposure (common in low light without Night Sight), even small hand movements blur the shot. Use Night Sight properly instead.
  • Lens smudge. Wipe the lens. I know. But this one catches everyone at least once.

Faces look over-smoothed or like wax

Open Settings → Advanced → “Saturation” and “Sharpness” sliders. Pull saturation down 5-10% and sharpness down 5%. Then try one shot. The GCam HDR+ pipeline already sharpens internally, so adding more on top creates the plastic skin look. The full breakdown of what each setting does is in our Google Camera features guide.

Configuration File (XML) Issues

Where to put the XML config

There are two folders depending on your GCam port:

  • BSG-based ports: /Internal storage/GCam/Configs/
  • Greatness or Wichaya ports: /Internal storage/GCam/Configs7/

If the folder doesn’t exist, open GCam once first. The app creates the folder structure on first launch. After that, drop the .xml file into the correct folder.

How to load a config

Open GCam. Double-tap the dark area just under the shutter button (the area between the gallery thumbnail and the shutter). A “Restore configuration” dialog appears. Pick your .xml file. The app restarts with the new settings.

My config does nothing

Two likely causes:

  • You dropped the .xml in the wrong folder for your port (see above).
  • The config was made for a different GCam version. A config tuned for GCam 9.0 may not load cleanly on 9.7. Find a config matching both your phone and your GCam version.

Update Problems

Should I always update to the newest GCam?

No. The newest build isn’t always the most stable for your phone. If your current GCam version is working well, the smart move is to wait a week after a new build drops, then read the XDA thread for your phone. If users on your exact model report it’s stable, then update. If not, stay on your current version. Updates don’t fix anything you weren’t already missing.

Will updating delete my settings and configs?

No. Settings live inside the app, and most ports preserve them across updates. Config XML files live in your storage, not inside the app, so they survive any install or uninstall. The only thing you’d lose is access to the app itself if the new version crashes, which is why backing up the old APK before updating is a good habit.

Brand-Specific Quirks

Samsung Exynos phones

Exynos variants of Samsung Galaxy phones (mostly older models sold outside the US) historically had more GCam issues than Snapdragon variants because of how Exynos handles the camera HAL. Most modern Samsung phones (S22 onwards) use Snapdragon globally, so this is mostly a legacy problem. If you’re on an older Exynos S10 or S20, look for builds labeled “Exynos” specifically. Full Samsung-by-model coverage is in our Samsung GCam guide.

Xiaomi HyperOS and MIUI restrictions

Newer Xiaomi phones running HyperOS have stricter background camera permissions. Make sure GCam has all camera, storage, and location permissions allowed manually (Settings → Apps → GCam → Permissions). Without all three, Night Sight often fails silently.

Oppo, Vivo, and Realme (ColorOS / Realme UI / Funtouch)

These three share parts of the same Android skin under the hood. They sometimes limit which apps can access secondary lenses (the ultrawide and telephoto sensors). GCam’s main lens works fine, but if you’re missing the ultrawide option, your phone’s OEM may have restricted it at the framework level. The workaround is to use a port specifically labeled as supporting your model.

Huawei without GMS

Newer Huawei phones (Mate 50 series and later) ship without Google Mobile Services. GCam still installs as a regular APK, but if the build requires Google Play Services for some background tasks, you may need to skip those features. Most modern Huawei-friendly ports work around this.

Motorola, Nothing, and Sony

These three usually have the smoothest GCam experience because their Android skins stay close to stock. Permissions just work, Camera2 is enabled by default, and updates rarely break compatibility.

When to Try a Different GCam Version

Not all GCam builds are equal, even at the same version number. The “version” people quote (8.4, 9.1, 9.7) refers to the underlying Pixel Camera release that the mod is based on. The actual mod is built by a community developer, each with their own signature:

  • BSG (Burial) – the most widely compatible builds, usually the first place to start
  • Greatness – heavier on features and configurability, popular for tuners
  • Wichaya – lightweight and very stable on mid-range phones
  • Urnyx05 – tuned for specific OnePlus and Xiaomi models
  • Parrot043 and Shamim – often release the most up-to-date 9.x builds

If a BSG build crashes on your phone, try a Greatness or Wichaya build of the same version before dropping to an older release. The base Pixel Camera code is identical; only the wrappers differ.

Background on what’s actually inside each GCam release: Google publishes detailed write-ups about the imaging pipeline on the Google Pixel blog, which is useful context if you want to understand why specific features behave the way they do.

FAQs

Why does GCam show a black screen when I open it?

Almost always because Camera2 API is not enabled or not at FULL level on your phone. Install Camera2 API Probe from the Play Store, check the level, and enable Camera2 manually via ADB if needed.

Is GCam safe to install?

Yes, as long as you download it from a known modder (BSG, Greatness, Wichaya, Urnyx05, Parrot043, Shamim) and from a trusted host. Avoid random APK aggregators. Play Protect may warn you because the APK is unsigned, but that’s expected for community ports, not a security risk.

Does GCam need root access?

No, root is not required for any modern GCam build. A few older legacy ports or specific astrophotography tweaks needed root, but anything from GCam 8.0 onward runs as a normal sideloaded APK.

Will GCam slow down or damage my phone?

No. GCam uses your phone’s normal camera sensors and processors. It does not modify system files. Uninstalling removes everything cleanly. The only ongoing cost is storage for the photos themselves, which are the same size as any other camera app.

How often should I update GCam?

Only when your current version stops working or when a new release fixes a bug you’re hitting. Updating for the sake of updating often breaks more than it fixes, since each new build needs community config tuning to match it.

Why are my GCam photos different from a Pixel’s photos?

Two reasons. First, your sensor is different from a Pixel sensor, so the underlying pixel data is different. Second, GCam ports run the same processing pipeline as the real Pixel Camera, but without Google’s fine-tuned model weights for non-Pixel sensors. A good XML config closes most of the gap.

Can I use GCam alongside my stock camera app?

Yes. They are completely separate apps. Some people keep GCam for portraits and Night Sight, and use the stock camera for video and Cinematic mode. Both apps save to the same gallery, so it just works.

What This Means for You

Most GCam problems aren’t actually GCam problems. They’re three or four recurring root causes (Camera2 API, chipset mismatch, missing config, wrong version) dressed up in different symptoms. Once you know where to look, you can fix almost any GCam install in under five minutes.

If your phone isn’t covered by a specific guide here, check the full list of supported Android phones for your model. And if you find a fix that worked for your exact phone but isn’t in this list, drop a note on the contact page — I’ll add it.

Related guides: How to enable Camera2 API · All GCam features explained

Erik Gill

Author

Erik Gill

I write simple, helpful guides about Android phones, GCam APK, and mobile camera tweaks. My goal is to make tech easy and useful for everyone.

Email About Contact