FAQ's and Troubleshooting Tips



- Click on the blue boxes to expand the content.
- To link to a FAQ, click and copy the # link.
- Something missing? Suggest ideas via email: gcam@celsoazevedo.com (unrelated emails will be ignored).

# Can't install the app »

Fix 1:

If you already have a Google Camera app installed, try to remove it first before installing a new one. If your ROM ships with a pre installed app, remove it (eg: using Titanium Backup + root) or use a different ROM.

Fix 2:

The version you're trying to install is not compatible with your Android version. Use a different apk.

# Black screen / viewfinder »

Fix 1:

You may need to install a front camera fix or enable an option to fix the issue.

Fix 2:

The GCam version you're using isn't fully compatible with your phone or your ROM. Try a different version.

# Motion photos not working »

Fix 1:

Motion photos doesn't work on Android 7.x, only Android 8.x or newer.

Fix 2:

This feature requires Google Photos. Other gallery apps will display still images.

Fix 3:

Motion photos requires specific settings for it to work. Sometimes you need to use a Pixel config and a 16:9 resolution instead of the default 4:3. Sometimes there's a menu where you can choose the resolution for this feature (try them all).

# App crashing just after being opened »

Fix 1:

You may need to install a front camera fix or enable an option to fix the issue.

Fix 2:

Older versions may not work on newer Android versions (and vice versa). Try an older apk if using an outdated Android version, or a more recent apk if using the latest Android version.

Fix 3:

Google Camera will crash if you didn't flash a GApps package. Read "how to use GCam without GApps" for more info.

Fix 4:

If it happens after you upgraded to a new version or after changing the app settings, there's a chance you're using not compatible settings. Clean the app data or uninstall and reinstall the app again.

Fix 5:

Using a root file manager/explorer, delete the following files (ignore the ones you can't find), and try again:

/system/etc/permissions/com.google.android.camera.experimental2017.xml
/system/etc/permissions/com.google.android.camera.experimental2016.xml
/system/framework/com.google.android.camera.experimental2016.jar
/system/framework/com.google.android.camera.experimental2017.jar

In some cases you also need to reflash an updated GApps package after removing the files. Keep in mind that dirty flashing GApps can cause some issues if the GApps you already have installed are old. A nandroid (TWRP) backup or a clean install is recommended.

Fix 6:

Google Camera only runs on ROMs with the Camera2 API enabled and some ROMs don't have this enabled. To enable:

- Flash the HAL3_Enabler.zip (by joshuous; use this zip to revert the change), or:
- Edit the build.prop:

# App crashing after taking pictures »

There's a big chance you're using the wrong settings and it causes the app to crash. Find a thread for your phone and see what other people are using or ask for help there.

# Can't open photos from inside the app »

Fix 1:

Go to "Debugging and tools", uncheck "camera.use_photos" and restart the app.

Fix 2:

Install the Google Photos app and try again.

# Over exposed photos »

There are 3 HDR options on most apks: HDR off, HDR+ On, and HDR+ Enhanced (HDR off, HDR+ Auto, and HDR+ On on older versions):

HDR Modes

Try to use HDR+ enhanced (right side option). While it's slower, it takes better photos on hard conditions:

HDR+ On vs HDR+ Enhanced

# Slow motion crash »

It only works on some phones. Most GCam versions based on 5.x don't support it, but some based on 6.x do. Make sure you select the correct FPS for your phone (eg: 120 instead of 240), explore the settings menu to see if such option is available.

Note about Android 7.x:

Older Google Camera versions supported slow motion on many Android 7 ROMs, but some phones needed an updated media_profiles.xml file with high speed profiles. Try to find a XDA thread for your phone, maybe other users with the same phone have a solution for this problem.

Alternative apps:

Some users reported that this feature was working on Nokia's camera.

# Black and white pictures »

Fix 1:

Change one of the settings (eg: disable camera sounds), restart the app, and try again.

Fix 2:

Reinstall the app (remove and install). Sometimes settings from old versions cause issues.

# Forum threads, telegram help groups, etc »

Check this page for a list of forum threads, telegram groups, and useful files/tools for this port.

I suggest you find other people using the same phone as you and see which port/version/settings they're using. See if there's a GCam thread for your phone on XDA or posts on your phone's subreddit.

# How to save error logs »

If the app is crashing and you want to send a log for the developer, check the How to save a logcat with MatLog page.

# How create app clones »

To create clones of Google Camera apps, check my how to clone apps guide.

# How to use GCam without GApps »

You can run Google Camera with microG. Download Services Core from their website, install it, reboot the phone, and then launch Google Camera.

If for some reason MicroG doesn't work for you, you can install Google Services Framework (GSF) manually, although this can result in reduced privacy. TWRP zips are available for Oreo and Pie. They install GSF as a system app and are able to survive system updates:

# How to load and export Google Camera settings (xml files) »

Some versions support import/export of .xml configuration files. Check this guide to know how it works.

# What's "Sabre"? »

Sabre is a merge method created by Google that improves photo quality on some modes. Some call it "super resolution". It's used for Night Sight and some GCam mods also use it for zoomed photos and HDR+ Enhanced. Only works with the RAW10 format (other RAW formats result in black photos).

Sometimes Sabre isn't supported by all cameras and Google Camera will crash after taking a picture. The fix for this is to disable Sabre (only available on some mods) and restart the app.

# What's "Pixel 3 AWB"? »

The Pixel 3 AWB (Auto White Balance) was created by BSG and Savitar and uses the device's colour calibration info instead of the pixel 3 info. This is different from the Colour Balance options available in the viewfinder.

Only some GCam versions come with this setting. It works with one of the "Pixel" models and sometimes it can result in pictures that look different from reality (e.g.: yellow street lights can become white).

# What "Libs" do and which one to use? »

In plain english, the libs included by some version versions affect the noise levels, detail vs smoothness, colours, add/remove brightness to shadows, etc. Usually these versions include the default lib (used by Pixel phones) and a few modified by other modders.

It's impossible to tell which one is better because they work differently on different hardware. It also depends on your preference (more noise + more detail vs less noise + worse details). You have to test to know which one is better for your phone.

# What's "Hot Pixel Correction"? »

Reduces the number of "hot pixels" (red dots) on the picture.

# What's "Lens Shading Correction"? »

Fixes vignetting (darker area around the centre of the picture).

# What's "Black Level"? »

Using a custom "black level" value usually fixes pink or green photos on phones with this problem.

Some versions allow users to use custom values for each colour channel (Crimson Red, DarkGreen, Light Green, Blue). This can be used to improve results in low light.

# What's "Hexagon DSP"? »

Hexagon DSP is an image processor available on some SoCs (processors) and improves processing performance while using less battery. Leaving it ON usually improves speed, but doesn't work on all phones.

Some apks are tagged with "NoHex" or "NoHexagon". Other apps have a "allow unknown devices" setting that enables/disables Hexagon.

# What's "Buffer fix"? »

The "buffer fix" option fixes viewfinder lag on some phones affected by this problem. There's a downside to this setting: on some phones users have to double tap the shutter button in order to take pictures.

# What's "Pixel 3 Color Transform"? »

This replaces the code cameraAPI2 SENSOR_COLOR_TRANSFORM1 and SENSOR_COLOR_TRANSFORM2 with that of pixel 3 (works for the creation of DNG images). Changes colours slightly.

# What's "HDR+ underexposure multiplier"? »

This adjusts the under exposure (if auto exposure is enabled). Set HDR+ underexposure multiplier to 50% and compare it with "normal" photos. Some users use it on 0%, but you need to test and see which value is better for your phone.

# What's "Default GCam CaptureSession"? »

Android 9+ only. Used for capturing images from the camera or reprocessing images captured from the camera in the same session previously. More info on Google's developer website: CameraCaptureSession.

# What's "HDR+ parameters"? »

HDR works by merging a number of pictures. If you select "36", it means that Google Camera will use 36 frames/photos to create the final picture. Higher values improve quality, but only until a certain point and at a speed cost. For daily usage something between 7-12 is usually enough.

# "Autoexposure correction" and "Correction Night Sight" »

Controls the shutter speed. Long shutter speeds can be used for long exposure photos, but it doesn't work well on all phones and users often report crashes. On the OnePlus 3, long exposure times only work with the "Pixel 1" model and crashes with other models. Sometimes going a step up or down can help fixing the pink tint that affects some phones.

# Portrait Mode vs Lens Blur »

Some versions of this port come with these two features. Portrait Mode works better with humans and (sometimes) animals and has better edge detection. Lens blur is older and works with objects too, but it has worse edge detection and sometimes it blurs what shouldn't be blurred.

# How to change the camera/lens used (phones with multiple cameras)? »

Some GCam versions support multiple cameras (main front/rear camera, wide angle, etc). Support also depends on the phone, if it properly declares the available cameras or not.

Usually you can move between cameras by pressing the camera switch button, usually with a normal click or a long click.

The order used depends on the GCam version used/device. Some GCam versions use different colours on the camera switch button (blue, red, etc) with each colour indicating a different camera.

I suggest you read fu24's post about this and also Arnova8G2's post where he explains how it works on (some of) his versions.

# What's "Recompute AWB"? »

It changes Auto White Balance (AWB) specially in low light with HDR enabled. In order to see the difference between "on" and "off", take two pictures with the setting disabled and enabled.

# What's "Select iso priority"? »

(this feature is still being tested)

# What's "Metering mode"? »

This changes the way Google Camera measures the light of the scene on the viewfinder. It doesn't change the final picture, but it may affect the areas of the viewfinder that are darker/brighter.

Some versions come with multiple settings for this option. Some might work on your phone, while others won't do anything. It all depends on the hardware/software of your phone.

# How to change your phone's fingerprint? »

1. Using Magisk Manager, install the MagiskHide Props Config module and reboot.
2. (screen recording) Using a terminal app (e.g.: Termux), type su, press "enter" on your keyboard, and grand root access.
3. Type props > press enter > type 1 (to change fingerprints) and confirm by following the instructions.
4. Pick the phone you want to "emulate".
5. After changing the fingerprint, choose the option to reboot.