How to Install GCam on Any Android Phone and Actually Get It Working

Last Updated on 15 May, 2026 by Montel Anthony

Google’s Pixel camera app produces some of the best mobile photos on the planet, and you do not need a Pixel to run it. Millions of Android users on Samsung, Motorola, OnePlus, Xiaomi, and other phones run modded GCam APKs that bring Pixel-grade Night Sight, astrophotography, and HDR+ processing to hardware Google never intended to support. This guide covers every step — from confirming Camera2 API compatibility to picking the right APK, loading config files, and fixing the crashes that most installation guides never explain.

Key Takeaways

• Camera2 API support determines whether GCam can run on your device at all
• Finding a port built for your chipset matters more than picking the newest version
• Config files unlock camera-specific tuning that generic ports miss completely
• Black screen crashes and AR errors have direct fixes that work without root access
• GCam 9.x requires Android 12 or above; earlier Android versions need GCam 8.x or older

What GCam Does That Your Stock Camera Cannot Match

Google Camera processes images through a computational stack that most phone manufacturers have not replicated. Your phone’s default camera records what the sensor sees. GCam applies multi-frame processing to what the sensor collected.

The most obvious example is Night Sight. Standard night mode on a budget Android phone takes one slow exposure and brightens the result. GCam captures a burst of shorter exposures, aligns them to correct for hand movement, then merges them into a single frame. The output retains shadow detail and colour accuracy that stock night modes destroy through aggressive noise reduction.

HDR+ works on a similar principle. A Samsung Galaxy A-series phone running GCam consistently produces sky-and-foreground exposures with far more balanced tonal range than Samsung’s native app on the same hardware. The difference is not the sensor. The same sensor produces better output because different software processes the raw data.

Astrophotography mode extends Night Sight to capture durations of up to four minutes. The phone must stay completely still — propped on a surface or mounted to a tripod. Pixel phones have carried this feature since 2019, and the ported version works on compatible Android hardware with no root access required.

Portrait mode in GCam uses depth information differently from most stock implementations. Rather than relying purely on a secondary telephoto or wide lens for depth mapping, GCam runs a neural network analysis on the primary lens output. This produces edge separation between subject and background that holds up even on single-camera phones where competing portrait modes look artificial.

Top Shot is another GCam feature that stock cameras rarely implement well. When you press the shutter button, GCam captures a short burst and suggests the frame where eyes are open and faces are unblurred. It is not a manual burst mode. GCam picks the best frame for you.

The trade-offs are real. GCam ports sometimes break video recording on specific chipsets. Some ports conflict with MediaTek hardware and produce green tints. Understanding these limitations before installing saves you from blaming the wrong variable when something does not work as expected.

How to Confirm Camera2 API Support Before You Install GCam on Android

Camera2 API is the Android framework layer that gives apps full control over the camera sensor pipeline. GCam requires it. Without Camera2 API at Full or Level 3 support, GCam will install but produce broken output or crash the moment you open the viewfinder.

The fastest check is through a free diagnostic app. Open the Google Play Store and install Camera2 API Probe, published by March Media Lab. Open the app and look at the Hardware Support Level listed for your rear camera.

Five support levels exist:

• Legacy: Camera2 API is technically present but not usable. GCam will not work reliably on these devices.
• Limited: Only basic Camera2 features are accessible. GCam may run but with significant processing compromises.
• External: Applies to USB cameras, not internal phone sensors. Not relevant for this process.
• Full: Camera2 API is completely supported. GCam has access to everything it needs.
• Level 3: Full support plus RAW image capture and YUV reprocessing. The best outcome for GCam performance.

Full and Level 3 support give you a clean GCam install. Limited support means you need a port specifically written to work around those hardware restrictions. Legacy support means GCam will not produce usable photos on that device.

Most phones from Qualcomm Snapdragon-based manufacturers — Xiaomi, OnePlus, Motorola, Sony — report Full or Level 3 support. Samsung Exynos devices have historically defaulted to Limited mode, though developer ports from BSG and Zoran contain Exynos-specific workarounds that compensate for the reduced API access.

MediaTek chipsets are the hardest category for GCam compatibility. A number of MediaTek phones ship with Camera2 API disabled at the system level. Some manufacturers enable it through software updates after community pressure, but there is no guarantee. If your phone runs a MediaTek chip and Camera2 API Probe reports Legacy, your realistic options are a MediaTek-specific port or a Camera Go mod — a lighter version of the app with fewer processing demands.

Do you know which chipset your phone runs? If not, open Settings, tap About Phone, and look for Processor or SoC. Some phones list it under Hardware Information. Identifying the chip name before searching for a port eliminates most of the failed-install guesswork.

How to Find the Right GCam APK for Your Device

Picking the wrong GCam APK is the single most common reason installs fail. Every port targets a specific Android version range, and many are tuned for particular chipsets or specific phone models. Downloading the newest available build without checking compatibility first wastes time.

The two main community hubs for GCam ports are GCam Hub run by Celso Azevedo and the XDA Developers port hub thread at xdaforums.com. GCam Hub organises downloads by version and developer with recommended stable builds labelled clearly. XDA carries deeper device-specific discussion, changelog histories, and user reports sorted by phone model.

Step one: match GCam version to your Android version.

• GCam 9.x: Android 12 and above (some builds also work on Android 11)
• GCam 8.6 to 8.9: Android 11 and above
• GCam 8.1 to 8.5: Android 10 and above
• GCam 7.x: Android 9 and above
• GCam 6.x: Android 9 and above (use GCam 7+ on Android 10 if 6.x shows instability)
• GCam 5.x: Android 8 and above
• GCam 3.x: Android 6 and above, supports 32-bit processors

Check your Android version under Settings > About Phone > Android Version before selecting any build.

Step two: match the developer port to your chipset.

Several developers maintain active ports across multiple GCam versions:

• BSG (Butter Smooth Google Camera): The most widely tested stable port available. Works across the broadest range of Qualcomm-based devices. The current recommended BSG 9.4 release is MGC_9.4.103_V36, published February 2026, targeting Android 11 and above. Start here for Snapdragon devices.
• BigKaka: Reliable for Snapdragon mid-range and flagship phones. Maintains active builds in the 9.x, 8.x, and earlier series simultaneously.
• Shamim: Strong on Samsung Exynos and Qualcomm midrange hardware. SGCAM builds carry model-specific config libraries with extensive community testing.
• Zoran: Built specifically for Exynos chipsets. If your Samsung Galaxy runs Exynos rather than Snapdragon, try Zoran’s ZGCAM before any other port. Exynos exposure and white balance behaviour differs from Snapdragon, and Zoran’s port corrects for it at the config level.
• Arnova8G2: One of the original port developers. Less active on GCam 9.x builds but remains the best source for GCam 5.x compatibility on older Android hardware.

For Samsung Galaxy users on Exynos specifically: Zoran’s ZGCAM series produces better colour science and tonal accuracy than a generic BSG build. The difference in skin tone rendering is visible at first comparison. Exynos hardware defaults to a warmer colour balance, and Zoran’s config pre-corrects for it rather than leaving that adjustment to the user.

If your phone runs a current Qualcomm chip and you want a single starting recommendation: download BSG 9.4 for Android 12 or higher, or BSG 8.9 for Android 11. Both have config files available for dozens of popular phone models. Exhaust these options before moving to device-specific ports.

Step three: search for your exact phone model.

Use the search function at celsoazevedo.com/files/android/search/ with your phone’s model name. Results surface developer notes, required camera fix APKs, confirmed config files, and known issues for your device. The search saves more time than browsing developer pages manually.

How to Install GCam on Android: Step-by-Step Instructions

Before downloading anything, your phone must permit APK installations from outside the Google Play Store. Android blocks sideloading by default.

Enable Unknown Sources Installation

The setting location varies by Android version:

1. Open Settings.
2. Go to Apps or Application Manager.
3. Tap the three-dot menu at the top right.
4. Select Special App Access.
5. Tap Install Unknown Apps.
6. Select your browser or file manager app.
7. Toggle Allow From This Source to on.

On Android 12 and later, the permission prompt appears automatically when you attempt to open a downloaded APK file. You can approve it from that prompt directly without going through Settings.

Download the GCam APK

1. Open your phone’s browser and go to celsoazevedo.com/files/android/google-camera/dev-suggested/.
2. Locate the GCam version matching your Android version from the chart above.
3. Expand the section for your chosen version.
4. Tap the APK filename link for your preferred developer.
5. Confirm the download prompt by tapping OK.
6. The file saves to your Downloads folder.

Do not download GCam APKs from random websites, YouTube video descriptions, or unverified Telegram channels. The two trusted sources are Celso Azevedo’s site and the official XDA Port Hub thread. Both link directly to developer-hosted files. Downloading from unverified sources puts your device at security risk from modified APKs.

Install the APK

1. Open your Files or Downloads app.
2. Tap the GCam APK file.
3. Tap Install at the permission prompt.
4. Installation completes in under ten seconds.
5. Tap Open to launch GCam immediately, or find it in your app drawer.

Grant Camera Permissions on First Launch

GCam requests access to your camera, microphone, location, and storage when it first opens. Grant all of them. Refusing camera access or storage access stops GCam from functioning entirely. Location access is optional — it tags your photos with GPS coordinates if granted.

Run a Basic Compatibility Test

Point GCam at a scene with strong contrast between bright and dark areas. A window with outdoor light behind it works well. If the viewfinder displays a live preview and the shutter button captures a photo successfully, the install is working. Move to the config file step.

If the viewfinder stays black after granting permissions, read the black screen fix in the troubleshooting section below before proceeding.

GCam Config Files: The Step Most Guides Miss

A config file is an XML export of GCam’s internal settings, tuned for a specific phone’s camera hardware. Without a config, GCam applies default Pixel processing values to your non-Pixel hardware. Colours may skew green or magenta. Autofocus may hunt through focus distances instead of locking. HDR+ may clip highlights that your sensor’s dynamic range is capable of retaining.

Config files are small XML files that GCam reads from a specific folder on your phone’s internal storage. Community-created configs are available for hundreds of phone models through the same developer pages where you downloaded the APK.

How to Find a Config

On the Celso Azevedo stable versions page, each APK entry includes a configs link next to the filename. Tap that link and search the list for your phone model or chipset. Configs named for a specific model like the Xiaomi Redmi Note 13 Pro will work best on that phone. If your exact model is not listed, look for configs built for phones sharing the same chipset — a Snapdragon 778G config from one manufacturer will produce similar results on any phone using that processor.

How to Install a Config File

1. Download the XML config file from the developer’s config page.
2. Open your file manager and navigate to internal storage.
3. Find the folder DCIM/GCam/configs. Some ports use DCIM/GoogleCamera/Configs instead. Create the folder if it does not exist.
4. Move the XML file into that folder.
5. Open GCam.
6. Tap the black bar at the bottom of the viewfinder.
7. A config import panel appears listing available XML files.
8. Select your config file.
9. Tap Restore.

GCam will close and reopen briefly. The config settings are active when it returns.

Diagnosing Config Problems

A config that produces a green tint is coded for different camera hardware. It corrects for a white balance baseline that does not match your phone’s sensor. Try a second config from the same list, or try one built for a different phone using the same chipset.

A config that produces overexposed portraits is applying HDR+ tuning that suits outdoor landscapes more than close-range subjects. Open GCam settings, find the HDR+ control, and reduce the enhancement level by one step. Reshoot the same portrait.

Is the output still off after testing three or four configs? Search the XDA thread for your phone model. Members post device-specific configs with build version notes, which removes the guesswork of matching config to GCam version.

Fixing GCam Black Screen, Crashes, and Common Compatibility Errors

GCam crashes on first launch more often than any other install failure point. The cause is almost always one of three things: a mismatched Android version, a conflicting Camera2 API level, or a missing camera fix companion APK.

Fix 1: Black Screen in the GCam Viewfinder

A black screen viewfinder means GCam loaded but cannot access the camera sensor feed. The app is running. The camera pipe is not connecting. This is different from a crash.

The solution in most cases is a camera fix APK. These are small companion applications that patch the interface between GCam and the device’s camera hardware driver — the HAL layer. BSG’s download pages include a camera fix link alongside each major APK. Download and install the camera fix before reopening GCam. The black screen clears on most affected devices after applying the fix.

Fix 2: GCam Crashes Immediately on Opening

An instant crash on every launch means the APK targets a different Android version than the one your phone runs. Check your Android version under Settings > About Phone. Cross-reference with the version chart in the finding-a-port section. A GCam 9.x build on Android 10 crashes every time — that is expected behaviour, not a bug.

Uninstall the current GCam APK. Download the version that matches your Android version. Reinstall. The crash stops.

Fix 3: Video Footage Records With a Green Tint

This is a known conflict on MediaTek chipsets and some older Snapdragon 6xx series devices. GCam’s video pipeline uses a YUV color space format that certain chipsets do not handle correctly. The photo pipeline processes differently and produces clean output, making this problem video-specific.

Open GCam, go to More Settings, then Video, and disable HDR Video. Standard video output records in the correct colour format on affected devices without the green cast.

Fix 4: AR Stickers and Playground Features Cause Crashes

Playground and AR sticker features require Google Play Services AR and ARCore device certification. GCam crashes when these features activate on phones where ARCore is not supported.

Open GCam settings and disable all AR features under the AR section. GCam operates without them. Every other feature continues to work normally after disabling AR.

Fix 5: GCam Photos Save to the Wrong Folder

Some ports default to saving photos in a GCam-specific sub-folder inside DCIM rather than your main camera roll. Your stock gallery app may not display them automatically.

Navigate to More Settings > Storage > Save Location inside GCam. Set the save location to DCIM/Camera. All subsequent GCam photos will appear in the same folder as your stock camera photos.

Fix 6: Slow Processing After Every Shot

Extremely long processing times between shots usually means HDR+ Enhanced is active on a device without enough processing headroom to run it efficiently. Snapdragon 6xx and Exynos 9-series devices are the most common affected hardware.

Switch from HDR+ Enhanced to standard HDR+ in the viewfinder controls. Shot-to-shot time drops significantly without a visible quality reduction in most shooting conditions.

Brand-Specific GCam Guidance for Samsung, Motorola, OnePlus, and Xiaomi

The install process is the same across all Android brands. The port selection and config tuning differ meaningfully by manufacturer.

Samsung Galaxy

Samsung phones split into two chipset lines depending on the market region. North American and Korean Galaxy flagships typically run Snapdragon. European and some Asian models run Exynos. Check your model code or Settings > About Phone > Processor to confirm.

Snapdragon Samsung devices work with any standard BSG or BigKaka port. Exynos Samsung devices produce better results with Zoran’s ZGCAM builds. Samsung’s One UI sometimes requires an additional camera fix APK — check the BSG or Zoran page for your specific Galaxy model.

Motorola

Motorola’s Android One and near-stock ROM devices are among the easiest for GCam compatibility. Camera2 API support is Full or Level 3 on most Motorola mid-range and flagship phones from 2020 onwards. BSG 9.x or 8.x runs cleanly on Motorola Edge and Moto G Power series devices without a camera fix APK in most cases.

OnePlus

OnePlus OxygenOS exposes Camera2 API at Full or Level 3 on all current devices. GCam installs cleanly. The main consideration for OnePlus is choosing the right BSG or BigKaka build for your OxygenOS version. OnePlus 10 and newer users on Android 13 or 14 should target BSG 9.x builds.

Xiaomi

Xiaomi’s MIUI and HyperOS skins are compatible with GCam on most Qualcomm-powered models. The specific challenge with Xiaomi is that MIUI has periodically blocked third-party camera apps from accessing the Camera2 API pipeline. If GCam produces broken output on a Xiaomi device, check the MIUI security settings. Some builds require you to set MIUI Optimization to off in Developer Options before GCam gains full Camera2 access. The Cloudorian guide on enabling Android Developer Options walks through accessing those settings on any Android phone.

Xiaomi users also benefit most from device-specific config files. MIUI’s post-processing applies sharpening and saturation before Camera2 API output reaches GCam. Configs tuned for MIUI hardware correct for this processing rather than stacking additional sharpening on top.

How to Keep GCam Updated Without the Play Store

GCam ports update multiple times per year. BSG published updates in February 2026, October 2024, and March 2024 for different version branches within a twelve-month window. You will not receive update notifications because these APKs come from outside the Play Store.

Where to Track New Releases

Celso Azevedo’s site links to four update alert channels from its stable versions page: a Telegram channel at t.me/googlecameraport, an RSS feed, a Bluesky account at bsky.app/profile/gcamfeed.bsky.social, and a Mastodon account at mastodon.social/@gcam. Subscribe to whichever channel you check regularly.

The XDA Port Hub thread provides additional context on each release — user reports on whether new builds regress specific chipsets, notes on which phones benefit most from the update, and comparisons against the previous version.

Running Two GCam Versions at Once

Different GCam ports use different Android package names. Android treats them as entirely separate apps. You can install BSG 9.4 and BSG 8.9 on the same phone simultaneously. This proves useful when one version handles stills cleanly but another handles video better on your chipset.

Check the developer’s release notes before installing a second build alongside the first. BSG documents when package names change between versions. A package name change means the two versions install as separate apps with no conflict. The same package name means the newer version overwrites the older one on install.

Should you update every time a new build drops?

A build producing good output on your phone does not break when a newer version releases. Updates target specific issues and add features. If the current version produces the photos you want, wait for community reports on whether the new build improves output on your chipset before updating. XDA threads for your phone model accumulate real-world comparisons within days of each new release.

Run These Tests After Your First GCam Install

Once GCam is running and your config is loaded, take a structured set of test shots before deciding the install is complete.

1. A full-resolution photo outside in daylight, standard mode. Check foreground and sky detail simultaneously.
2. A portrait photo with a person at arm’s length, still in standard mode. Check background blur edge accuracy and skin tone.
3. A photo inside a room with mixed window light and artificial ceiling light. HDR+ should balance both light sources.
4. One Night Sight photo in a dim interior with no direct light source. Check for colour accuracy and retained shadow detail.
5. A ten-second video clip. Watch it back and confirm colour accuracy and audio sync.

Compare each GCam result to the same scene captured by your stock camera app. The comparison makes the processing difference immediately visible. Shadow detail in the indoor shot, highlight recovery in the window, and skin tone accuracy in the portrait are the three areas where GCam typically produces the most visible improvement.

If daylight output looks excellent but video shows a green tint, apply the video fix from the troubleshooting section. If portrait blur looks artificial, reduce the bokeh intensity slider in GCam’s portrait settings. If Night Sight output looks flat and underexposed, make sure the phone was completely stationary during capture.

For expanding what you can do with your Android photography setup beyond GCam, the free tools guide for photographers on Cloudorian covers editing apps and workflow tools that work directly with GCam output on Android, Windows, and Mac.

The active GCam developer community at XDA and Celso Azevedo’s site means almost every current mid-range and flagship Android phone has a confirmed working port in 2026. The install process takes under fifteen minutes on any compatible device. The output difference shows up in the first test photo.