The Secret GCam APK Port for MediaTek Processors Revealed

MediaTek phones often ship with capable camera hardware and modest camera software. A Dimensity or Helio phone can have a large main sensor, a bright lens, and a fast image processor, yet its stock camera app may produce flat HDR, noisy night shots, and dull colours in difficult light. A GCam port changes that equation. It brings Google’s computational photography, including HDR+ merging, Night Sight processing, and portrait depth handling, to phones that never shipped with a Pixel camera. The difference can be striking: cleaner shadows, wider dynamic range, and more natural skin tones from the same sensor you already own.

That promise comes with a catch that every MediaTek owner needs to understand before installing anything. GCam ports are modified versions of a camera app built for Pixel phones, adapted by independent developers to run on many other devices. Adaptation quality varies a great deal by phone model and processor, and a port that works beautifully on one Dimensity phone may crash, show a black viewfinder, or refuse to save photos on another MediaTek phone with a similar name. There is no single GCam port for MediaTek, and anyone who tells you otherwise is selling a shortcut that does not exist. This guide explains how to approach GCam on MediaTek devices safely, how to check compatibility, how to install and test methodically, how to tune config files, and how to keep your stock camera as a reliable backup.

I have tested GCam ports on several MediaTek phones over the years, and the pattern is consistent: the phones that benefit most are the ones where the hardware is good and the stock processing is conservative, which describes a large number of Dimensity 8000 and 9000 series phones and Helio G99 phones. The phones that frustrate owners most are the ones where the camera interface is limited or where a port was built for a different processor variant. The method in this guide is designed to find out which group your phone falls into within an hour, without risking your photos or your system camera.

What a GCam Port Is and Why MediaTek Phones Benefit From Computational Photography

A GCam port is a modified Google Camera app, repackaged so it can install and run on a non-Pixel Android phone. The original app relies on Pixel-specific camera libraries and processing pipelines, so port developers such as BSG, Arnova8G2, Shamim, Nikita, and the LMC team rebuild parts of the app, add compatibility layers, and expose settings that let the app talk to other sensors and processors. The result is not an official Google product, and it is not supported by Google, but when a port matches your phone, it can deliver HDR+ frame merging, Night Sight multi-frame noise reduction, Astrophotography mode, portrait blur, and Super Res Zoom, all processed on your phone.

MediaTek processors, including the Dimensity 9200, Dimensity 8100, Dimensity 8200, Dimensity 7050, Helio G99, and Helio G96, include dedicated image signal processors and AI processing units that are more than capable of handling GCam’s multi-frame work. The bottleneck is usually software, not silicon. Stock camera apps on many MediaTek phones apply heavy noise reduction and aggressive sharpening, or they merge too few frames in HDR, which leaves night photos grainy and high-contrast scenes with blown highlights. GCam merges more frames, aligns them, and averages out noise, which is why the same sensor can produce a visibly cleaner photo through a port.

GCam Ports, Pixel Features, and What Stays Exclusive to Pixel Phones

Not every Pixel feature survives the move to a MediaTek phone. HDR+, Night Sight, portrait mode, and panorama usually work when the port matches the phone. Astrophotography mode works on some ports and needs a tripod and a dark sky. Motion Photos, Top Shot, and some video features may be missing or unstable. Features that depend on Pixel-specific hardware, such as certain Tensor processing paths, may never work on a port, and that is normal. A realistic expectation is better stills in difficult light, not a full Pixel camera, and some of the most exclusive Pixel-only features are worth reading about before you judge a port harshly. Hidden GCam features exclusive to Pixel phones explains which capabilities remain tied to Pixel hardware and why a port cannot always reproduce them.

Dimensity vs Helio: How Processor Families Affect GCam Compatibility

Dimensity phones generally run GCam ports more smoothly than older Helio phones, because Dimensity chips ship with newer camera interfaces and stronger image processors. A Dimensity 8100 or 9200 phone with full Camera2 API support is a strong candidate for a modern GCam 8.4 or 8.9 port. A Helio G99 phone can also run GCam well, especially for stills, but video support and auxiliary camera support are more likely to be limited. A Helio G96 or older Helio phone may run an older GCam 7 or 8.1 port better than a newer build, because newer builds assume camera features the older chip does not expose. Processor family is a useful first filter, but exact model matching matters more, as the next section explains.

Check GCam Compatibility on Your MediaTek Phone Before Installing Anything

Compatibility checking takes ten minutes and saves hours of failed installs. It has three parts: camera API level, exact model and processor variant, and recent user reports for that exact model. Skip any of the three and you are guessing. Do all three and you will know which port versions are worth trying and which ones to avoid.

Check Camera2 API Level With a Camera Capability Checker App

Many GCam ports need a specific camera API level, known as Camera2 API support, enabled in the phone firmware. Install a free camera capability checker app, such as Camera2 API Probe, from the Play Store, open it, and look at the hardware support level for the rear camera. Full or Level 3 support gives the best results, because GCam can control manual exposure, focus, and RAW capture. Limited support may still run a port with fewer features, such as no manual controls or no RAW output. Legacy support usually means GCam will crash, show a black viewfinder, or save no photos. If your phone shows Legacy, look for a port specifically built for limited support, or accept that GCam may not be a good fit for that phone.

While you are in the checker app, note whether RAW capture is listed as supported, and whether the front and rear cameras report different levels. Some MediaTek phones give the main camera Full support and the front camera Limited support, which explains why a port can take excellent rear photos and struggle with selfies on the same phone. Write those levels down, because they predict which features to test first.

What Full, Level 3, Limited, and Legacy Support Mean in Practice

Full support means the phone exposes manual controls for exposure time, ISO, focus, and white balance, plus RAW capture and high-speed capture. Level 3 adds extra capabilities such as YUV reprocessing and additional output streams. Limited support means the phone exposes some manual controls but not the full set, so a port may run but with missing features. Legacy support means the phone only exposes the old Camera1 interface, and most modern GCam ports will not work reliably. If you see Full or Level 3, you have a green light to try a current port. If you see Limited, try a port that other owners of your exact model have reported working, and test stills first.

Identify Your Exact Model, Processor Variant, and Android Version

MediaTek makes many processors with similar names, and phone makers sell the same marketing name with different chips in different regions. A port built for a Dimensity 8100 variant may fail on a Dimensity 8100 Ultra variant, and a port for an Indian variant may fail on a European variant of the same phone. Open Settings, then About phone, and note the exact model number, the processor name, the RAM, and the Android version. Also note the security patch date, because a recent firmware update can change camera behaviour. Port compatibility often depends on Android version as well: a port built for Android 13 may fail on Android 14, and a port built for Android 14 may need a different config on Android 15. Exact model matching saves wasted installs and false conclusions.

Read Recent User Reports for Your Exact MediaTek Model

Look for reports from the last few months, not from two years ago. Old reports may describe a port version that no longer works, or a firmware version that has since changed. Recent reports show current crash issues and working features. Ignore reports that only praise a port without detail. Detailed reports mention night mode, portrait mode, video, and auxiliary cameras separately, and they name the port developer, the version number, and the config file used. A report that says Night Sight works but 4K video crashes is far more useful than a report that says this port is amazing, because it tells you exactly what to test.

How to Install a GCam Port on a MediaTek Phone Step by Step

Install one port version at a time for clear testing. Multiple ports installed together confuse results, because you cannot tell which one produced a photo or a crash. The steps below use the BSG GCam 8.4 port as an example, because BSG builds are widely tested on MediaTek phones, but the same sequence applies to Arnova8G2, Shamim, Nikita, and LMC builds. If you want a fuller walkthrough of the install sequence itself, Installing a GCam port step by step covers the same process for beginners, including how to allow installation from unknown sources safely.

1. Check your Camera2 API level and exact model first, as described above, and write down the port version other owners of your exact model recommend.
2. Open Settings, then Apps, then your browser, and confirm that Install unknown apps is set to Allow for that browser only, so you can install the APK file you download. Turn this permission off again after the install.
3. Download one GCam APK file, such as a BSG MGC 8.4 build, from a reputable GCam port listing. Check the file size and the version name before you tap it, and do not download a port that asks you to install a second helper app or grant device administrator rights.
4. Tap the downloaded APK file, tap Install, and wait for the install to finish. Do not replace or uninstall your stock camera app. A safe port installs alongside the stock camera like a normal app.
5. Open the GCam app and grant only Camera, Microphone, and Photos permissions. Deny location permission if you do not want location saved in photo metadata.
6. Point the phone at a bright scene and check that the viewfinder shows a live image. If the viewfinder is black, force stop the app, clear its data in Settings, then Apps, then GCam, then Storage, then Clear data, and try again once before switching to a different port version.
7. Take a normal daylight photo, then a Night Sight photo in a dim room, then a portrait photo of a person, and check that each one saves to the gallery.
8. Record the port version, the date, and which modes worked in a note on your phone, so you can compare the next candidate fairly.

That eight-step install is deliberately slow, because each step protects you from a common failure. A port that installs cleanly, shows a live viewfinder, and saves daylight, night, and portrait photos is a keeper worth tuning further. A port that fails at step six or seven is not worth hours of settings tweaks, and you should uninstall it cleanly and try the next candidate. The GCam port that works best on a MediaTek phone is the one tested on your exact model, not the newest version number on a download page.

Test Photos, Video, and Auxiliary Cameras Methodically

Test video separately from photos, because GCam video support varies widely on MediaTek phones. Some ports record smooth 1080p video at 30 frames per second. Some ports crash when you switch to 4K video. Some ports record video without stabilisation, so the footage shakes even when the photos are sharp. Test the video resolutions you actually use, starting with 1080p, and only try 4K after 1080p works. A port with great photos but broken video may still suit a stills shooter, while a hybrid shooter who records video daily needs both paths working before committing.

Test auxiliary cameras if your phone has them. Ultra-wide, macro, and telephoto support varies by port, and some ports support only the main camera. Some ports expose auxiliary cameras through settings toggles under Advanced settings, while others need a specific config file to enable them. Enable auxiliary support only if your port documents it for your model. Random toggles can crash the app or produce black photos from a lens that is not connected. Document which cameras work in your log, because a port that covers only the main camera still helps many shooters, and knowing its limits stops you from blaming the port when the ultra-wide button does nothing.

Tune GCam With XML Config Files Carefully for Your Exact MediaTek Model

Config files, usually XML files, adjust GCam processing for a specific phone model. A good config tunes noise reduction, colour, sharpness, HDR frame counts, and saturation for that sensor. A wrong config can create washed-out colours, heavy noise, or plastic-looking skin. Load only configs made for your exact model or a very close variant, load one config at a time, and test daylight and night results before and after. Compare results with no config applied first, so you can tell whether the config actually improved anything. A config should clearly improve results to earn its place, and if it does not, delete it and keep the default settings.

How to Load an XML Config File in GCam 8.4 and LMC Builds

To load a config in most GCam 8.4 builds, create a folder named GCam, then a subfolder named Configs8, in your phone’s internal storage, and copy the XML file there. Open GCam, double-tap the dark area near the shutter button, choose the config file from the list, and tap Restore. In LMC 8.4 builds, the folder is named LMC8.4 instead of GCam, and the double-tap area works the same way. After loading a config, force stop the app once and reopen it, then take a daylight photo and a night photo and compare them with the photos you took before loading the config. If the config was made for a different sensor, the daylight test will usually reveal the problem first, through a green or magenta cast or oversharpened edges.

For a deeper look at what config values actually change and how to tune them for detail without destroying skin tones, GCam XML config for mind-blowing detail explains config tuning in more depth, including sharpness, noise model, and saturation settings that matter most on MediaTek sensors.

Back Up Your Working Config Before Trying a New One

Back up your working setup before trying a new config. Save the working XML file separately, note the port version that works with it, and keep a copy in a cloud folder or on a computer. A new config can break a working setup in seconds, and a backup lets you restore in minutes. Without a backup you may lose a good setup to a bad experiment and spend an evening rebuilding it from memory. Treat configs like camera settings rather than magic files, and test each change deliberately, one at a time.

Adjust Processing Strength for Portraits Versus Landscapes

Adjust processing strength to your taste after a config loads. Some configs favour very clean, noise-free images, which can look plastic on skin. Some configs favour sharp detail with more grain, which can look crunchy at full size. Find a balance that suits your subjects. Portraits need gentler noise reduction and softer sharpening than landscapes, and a single config rarely suits both perfectly. If you shoot both often, keep two configs, one tuned for people and one tuned for scenery, and switch between them with the double-tap menu. That small habit is the difference between a config that helps and a config that fights you.

Solve Common GCam Problems on MediaTek Phones: Black Screen, Slow Processing, Colour Casts

Most GCam failures on MediaTek phones fall into three groups: a black viewfinder, slow processing, or a colour cast. Each one has a different cause and a different fix, and changing many settings at once during troubleshooting hides which fix worked. Change one thing, test, and write down the result, the same way you would test a camera setting.

Fix a Black Viewfinder by Changing Port Version and Clearing App Data

Fix a black viewfinder by trying a different port version first. Black viewfinders often come from processor-specific incompatibility, and a different developer build may solve it where settings tweaks cannot. Clear the port app data between version tests, because old data can carry broken settings into a new version. To clear data, open Settings, then Apps, then GCam, then Storage, then Clear data, and reopen the app. A clean data start gives each version a fair test. If three different port versions all show a black viewfinder on the same phone, the phone’s camera interface is the likely cause, and a port built for an older GCam version, such as 7.4 or 8.1, is worth trying before giving up.

Fix Slow HDR Processing by Lowering Frame Counts on Dimensity and Helio Chips

Fix slow processing by lowering HDR frame counts when the port settings allow it. In GCam settings, look for HDR+ frame count or HDR+ Enhanced frame settings under Advanced, and reduce the number of frames merged per photo. MediaTek processors vary in image processing speed, and heavy HDR merging can take many seconds per photo on a Helio chip, or several seconds on a Dimensity chip under load. A slower merge may still produce a better photo than the stock camera, so decide whether speed or quality matters for a scene. Use the stock camera for fast moments, and use GCam for planned shots where processing time is acceptable. Two cameras for two purposes is a valid workflow, and it is faster than waiting for a slow port to finish a photo you needed in two seconds.

Fix Green or Magenta Colour Casts With a Different Config and White Balance

Fix colour casts by testing different config files and white balance settings. MediaTek sensors render colour differently across models, and a config tuned for another sensor may cast green or magenta across the whole image. Test configs in daylight first, where colour is easiest to judge, because a daylight-accurate config usually performs well at night too, while a config that fails daylight will fail harder at night. If the cast appears only in one mode, such as Night Sight, check the white balance setting for that mode specifically, and try the auto white balance option before forcing a Kelvin value. Judge configs in daylight before trusting night results, and keep the config that gives neutral whites on a white wall in daylight.

Keep Your Stock Camera as Backup: A Dual Camera Workflow That Actually Works

Keep the stock camera as your reliable backup for video and fast moments. Stock camera software is tuned for your exact sensor by the phone maker, and it usually handles video, stabilisation, and fast autofocus best. GCam often wins for stills in difficult light, especially night and high dynamic range scenes. A dual camera workflow uses each app where it wins, and switching apps takes seconds, while losing a moment to a crashed port costs far more. Put both camera apps on your home screen, use GCam for planned stills, and use the stock camera for video, fast action, and any moment you cannot afford to miss.

Update ports cautiously rather than automatically. A new port version can break a working setup, especially when it targets a newer Android version or a different sensor tuning. Read the change notes and recent user reports before updating, keep the old working APK file as a backup, and install a new version only when it fixes a problem you actually have. A working camera setup is precious. Do not gamble it on an untested update before an important shoot, a holiday, or a family event. Test the new version on ordinary days first, and keep the old version until the new one has passed your daylight, night, portrait, and video tests.

Compare GCam and Stock Results Side by Side Every Month

Compare GCam results with stock results side by side monthly. Take the same scene with both apps, in daylight and at night, and compare them on a large screen, not only on the phone. A monthly comparison shows whether GCam still wins, because stock camera updates can close the gap over time through firmware updates. A port that won last year may lose this year, and regular comparison keeps your workflow honest. Use the winner for each scene type rather than loyalty to one app, because loyalty to a result beats loyalty to an app, and the best camera workflow is the one that produces the best photo today, not the one that won a test six months ago.

GCam Port vs Stock Camera on MediaTek: A Head-to-Head Comparison

The table below summarises the usual strengths of each side on a MediaTek phone. Your exact phone may differ, and that is why the monthly comparison in the previous section matters more than any table. Use the table to decide which app to open for a given scene, not to declare a permanent winner.

That comparison explains the dual workflow in one glance. GCam earns its place for stills in difficult light, and the stock camera earns its place for everything that needs speed, video, or an auxiliary lens. Neither side wins everywhere, and a photographer who uses both will take better photos than a photographer who insists on using only one. The best GCam setup for a MediaTek phone pairs a tested port with a reliable stock camera backup, and that pairing is what this guide recommends from start to finish.

Frequently Asked Questions About GCam Ports on MediaTek Processors

Will installing a GCam port void my phone warranty?

Installing a normal app port does not modify system files, and it should not void warranty by itself. Replacing system files could create warranty issues, so avoid any port that requires system modification, root access, or replacing the stock camera. Keep installation at normal app level only, keep the stock camera untouched, and uninstall the port cleanly if you need to send the phone for repair. A port that installs like a normal app and uninstalls cleanly is the safe kind, and any port that asks for more than that should be treated with suspicion.

Why does GCam crash on my MediaTek phone at launch?

Crashes usually come from model or processor incompatibility. Try a different developer build for your exact model, clear app data between tests, and check your Camera2 API support level. A port built for another processor variant often crashes at launch, even when the phone name looks similar. If the app crashes before the viewfinder appears, the port version is the most likely cause. If it crashes only in Night Sight or portrait mode, the config file or a specific setting is the more likely cause, and testing with default settings will narrow it down.

Can GCam improve front camera photos too?

GCam can improve front photos when the port supports that camera, especially for night selfies and portrait selfies where HDR merging helps. Front support varies by port and model, so test front portraits and night selfies separately from rear camera tests. Keep the stock camera for front video when GCam front video fails or stutters, because front video stabilisation is often better in the stock app. Dual app use covers both cases, and a front camera test takes only a few minutes.

Which GCam port version should MediaTek owners try first?

Start with the version that recent owners of your exact model recommend, not with the newest version overall. For many Dimensity phones that is a BSG GCam 8.4 build, while for many Helio G99 phones it is a Shamim or LMC 8.4 build, and for older Helio phones it may be an Arnova8G2 GCam 8.1 build. Version numbers alone do not predict success, because a build tuned for a Snapdragon phone can fail on a MediaTek phone even when it is newer. Model-specific reports beat version numbers every time, so let those reports choose your first candidate.

Do I need to root my phone to use a GCam port?

No. A normal GCam port installs like any other app and does not need root access. If a download page tells you to root your phone, unlock the bootloader, or replace system files to install GCam, stop and find a different port. Rooting is a separate choice with its own risks, and it is not required for the ports in this guide. Keep your phone unmodified, keep the stock camera, and treat any port that demands system changes as unsafe.

Your Next Steps: Check, Install, Test, and Keep the Stock Camera Ready

Check your Camera2 API level and exact model today before downloading any port, and write down the port version that recent owners of your exact model recommend. Install one candidate port, test daylight, night, portrait, and video modes, and keep the stock camera as backup while you do it. Save a working config separately, note the port version and the features that work, and compare GCam with stock results monthly so your workflow stays honest.

That methodical test will reveal whether GCam truly improves your MediaTek phone, and it will do so without risking your photos or your system camera. If the port wins for night stills, keep it for those scenes and use the stock camera for video and fast moments. If the port crashes or the stock camera wins across the board, uninstall the port cleanly, delete its config folders, and try again in a few months when a newer build for your exact model appears. Either outcome is useful, because you will have made the decision from your own test results instead of from a download page promise.