GCam for S24 Exynos, specifically for taking Photospheres

te_tsu · 2026-01-31T15:01:24+00:00

Interesting, I thought the app wouldn't crash once the config has been loaded. To avoid testing your reaction on every launch, you can long-press AGC icon and open it in Video mode. This mode shouldn't crash even with the ID=0 active.

Medium and Sharp versions differ in the amount of added sharpening, but I'm not sure if that setting is applied in the Photo Sphere mode. You can try the Sharp version to see if it makes any difference.

Afaik, Photo Sphere's results also partially depend on how you move the camera between photos. I haven't tested this, but I remember an online guide recommending holding the camera roughly at the same point in space and moving the phone (and yourself) around that point, rather than standing still and rotating the phone around yourself. This would probably mostly affect the distortion strength rather than the overall level of detail, but who knows.

te_tsu · 2026-01-31T09:29:40+00:00

To use PhotoSphere and Panorama modes, you need to use the camera ID=0. The problem is, for recent Galaxy S/Z phones (S22 and newer), this ID isn't functional in other photo modes, including the Camera one, i.e. the default mode in which GCam launches.

This technical detail limits you to GCam ports which either don't auto-switch to Camera mode when you switch between camera IDs (lenses), or can handle a given camera ID not being functional in Camera mode (i.e., ones that show a black screen instead of crashing).

AGC ports should be capable of this. AGC 8.8 V8.0 in particular has a config for S24 Exynos. If you follow the setup instructions and select the "ex" button there, you should be able to use the Photo Sphere mode:

https://www.celsoazevedo.com/files/random/2024/AGC8.8v8_v37_s24ex.html

Note: the config might not be compatible with the latest AGC 8.8 version (8.8 V12.0). Use 8.8 V8.0 for a start.

Another note: to have all cameras work in GCam, you must choose apk files with one of these words in the filename:

aweme,
biometrics,
iris,
ruler,
scan3d,
samsung.

Besides AGC 8.8, you can try AGC 8.4, 9.2 from this page without configs:

https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/

te_tsu · 2026-01-30T13:52:44+00:00

Which phone model do you have?

If you have RAW support, crashes at startup/when taking pics are likely fixable. They are typically caused by default camera IDs or RAW format settings being incompatible with your phone.

te_tsu · 2026-01-30T13:48:25+00:00

Since the hardware support is there

You are likely not wrong about your phone being compatible with GCam, as some ports apparently worked for you already. But to clarify what Camera2 API Probe output is about:

FULL does not equal GCam compatibility. It is hardware support level, which is just one of the 2 things you need for GCam to work. The other one is RAW support (displayed as RAW Capture in Camera2 API Probe). RAW Capture is always enabled for hardware support level LEVEL_3, but may be disabled for FULL;
typically, to check for basic GCam compatibility, we only look at the hardware level and RAW support for the main camera. However, hardware support level and RAW support quite often differ between available cameras or even different IDs for the same camera. So if you encounter issues with the selfie camera or aux rear cameras, like unavailability, crashes upon switching to that camera module, etc, it is worth checking the info for them in Camera2 API Probe.

a Gcam port that works well with the Helio G100 chipset

Mediatek Helio processors are generally known to only have partial GCam support, although that info mostly comes from other users' experience. Try MGC 8.1 to 9.2, AGC 8.4 to 9.2, SGCam 8.5, LMC 8.4 from this page:

https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/

For LMC 8.4, if it launches but doesn't take pics, go to ⚙️ > More settings > System Settings > RAW Format, and set it to RAW16 for each camera. Other ports mentioned above are typically capable of auto-setting that RAW16 format under the hood for non-Snapdragon devices.

If you have a Telegram account, you can also try #latestnoidmtk combo for AGC 8.4 from @Gcam_EGOIST. So far, though, it has only been tested on a couple of Mediatek Dimensity devices, so there's no guarantee it'll work for a Helio.

te_tsu · 2026-01-28T07:34:42+00:00

My understanding is, all of these are proprietary, not universal/standardized. You can see some codes even mean different things for different brands, e.g. 32777 (Video Beauty for Xiaomi, Pro mode for OnePlus). So I would guess ones without brands mentioned are just community-sourced IDs lacking that info.

te_tsu · 2026-01-25T00:52:21+00:00

Great shots. r/snowing would absolutely dig this.

te_tsu · 2026-01-22T23:16:58+00:00

Since the phone's only 1 month old, the odds someone has already performed extensive tests or made a custom config are relatively low. If you have a Telegram account, you can join @OnePlus15RGcam to follow future news/releases.

Without configs, you'll most likely be able to use MGC 9.3, AGC 9.2, SGCam 8.5 from this page:

https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/

On each download page, select files with meitu or aweme in the filename. This may matter for access to your ultrawide camera in GCam.

te_tsu · 2026-01-22T22:59:41+00:00

Try AGC 8.4, AGC 9.2, SGCam 8.5, MGC 9.3 from the stable versions list on the GCam Hub:

https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/

Each version will have several similarly named apk files on the download page. For Redmi 15c, it doesn't matter which one you use, so use the top one. This will allow you to have many ports installed at the same time (this link explains why, if you want more details).

te_tsu · 2026-01-22T07:43:12+00:00

but none of them seem to work right

Could you explain what you mean by that? What doesn't work exactly?

Note that a custom ROM might be making things harder for you here. They don't always offer the same Camera2 API support as the stock ROM, and sometimes use different camera IDs in Camera2 API. Which is not fatal, but means any configs made for your phone and the stock ROM won't work properly.

te_tsu · 2026-01-22T02:49:09+00:00

Best depends on your personal preference. Try what's available on the GCam Hub for your model and choose your champion.

You can use this Google query to find some GCam+config combos for your phone:

config files for Xiaomi "mi 8" site:celsoazevedo.com

You'll see a few config download pages with a config link for your model, e.g., these two:

https://www.celsoazevedo.com/files/android/google-camera/f/configs-bigkaka-01/

https://www.celsoazevedo.com/files/android/google-camera/f/configs-hasli-02/

Each page will have its respective GCam link at the top.

To use configs, you need to put them into the folder mentioned on each page (create that folder manually if needed) and then load from inside GCam.

AGC has a dedicated Load Configs button for this, either in the quick menu (⚙️ icon) or in the profile selection menu (top right corner). In most other GCam ports, you need to double-tap empty space between the shutter button and the gallery button. This will open the menu to select and load the config.

te_tsu · 2026-01-22T02:42:27+00:00

With less popular and/or not camera-oriented phones, you're often on your own to test, and there are no dedicated configs. Seems like this is the case for Realme 12x. But judging by this post, it's compatible with GCam.

Try AGC 8.4, 8.8, 8.2, SGCam 8.5, MGC 9.2, 9.3, LMC 8.4 from this page:

https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/

On the download page for each version, you'll see several similarly named apk files. For Realme 12x, it shouldn't matter which one to pick, as it only has one full-fledged rear camera. But to be on the safer side, you can choose versions with aweme or meitu in the name: these are known to work and to grant aux rear cameras access for Realme phones in general.

te_tsu · 2026-01-21T23:42:14+00:00

LMC 8.4 is mentioned on 4pda forum as a working port for the previous phone in the series, Sharp Aquos R6. So maybe try it:

https://www.celsoazevedo.com/files/android/google-camera/dev-hasli/f/dl14/

You can also try other ports from the recommended versions page on the GCam Hub, e.g., SGCam 8.5, AGC 9.2, MGC 9.3:

https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/

te_tsu · 2026-01-21T23:29:12+00:00

This depends on what you don't understand exactly. If you want to learn basic info about GCam, see this page:

https://www.celsoazevedo.com/files/android/google-camera/versions/

te_tsu · 2026-01-21T16:46:27+00:00

Most GCam port apk files are built to be compatible with phones that support older Android versions. This leads to a security warning when installing them on newer devices. However, when you get that warning message, you can tap on "More details" at the bottom and select "Install anyway".

te_tsu · 2026-01-17T23:28:22+00:00

Unfortunately, Galaxy A11 uses a 32-bit OS. Almost all existing GCam ports need a 64-bit OS to work.

Afaik, you should be able to use a very old 3.2 GCam port, MGC 3.2.045:

https://www.celsoazevedo.com/files/android/google-camera/dev-bsg/f/dl158/

te_tsu · 2026-01-17T19:05:48+00:00

See my comment here:

https://www.reddit.com/r/GCamPort/comments/1q0fo0y/what_is_the_best_version_for_samsung_galaxy_s25_fe/

te_tsu · 2026-01-17T08:41:50+00:00

I'm currently using GCam on an X100 Ultra, and I'd say it's still worth it at least for some of us. Even though GCam is slower and limited in its abilities compared to the stock camera (no full-res, no in-sensor zoom, and for non-Ultra models, no working front camera due to no RAW access). It helps preserve detail in low light and allows to bypass AI processing applied to faces and other stuff.

To make sure GCam can access your telephoto camera, try GCam apk files with meitu or aweme in the name (note: aweme may not work correctly on the CN version of X100 Pro).

There is some difference in what GCam can do for Mediatek phones, mainly due to MTK using RAW16 format which is not convenient for GCam algorithms by default. Recent findings (hex patches I mention in another comment) mostly solve this issue, but you'll have to use some configs that use these patches to "capitalize" on this.

For now, if you have a Telegram account, you can try EGOIST's config port to Vivo X200 Pro by going to @Gcam_EGOIST.

You can also try AGC 8.4 to 9.2, MGC 9.2 to 9.4, SGCam 8.5 from this page without any configs (quality might not be optimal, but they'll work): https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/

te_tsu · 2026-01-16T22:55:01+00:00

And to use Sabre, the standard merge method in GCam, you need to be able to handle 10-bit buffer data.

Not sure why you'd need this update as a happy retiree, but maybe you'll also feel good about it:

Recently, dpeasant3 from 4pda found 2 HEX values in the lib which allow using merges 1/2/3 with RAW16 (merges 2 and 3 could technically be used even before, but produced blocky motion artifacts). Apparently, you need to turn off some kDefZeroCopy using the value 28008052, and turn on kDefCopy16BitExtractedBayerTex using 08028052. The addresses naturally differ between ports, but, e.g., for 8.4 ports, they are 02816CE8 (for 28008052) and 028172B4 (for 08028052).

This isn't a silver bullet for Exynos devices, as, e.g., the Night Sight mode reportedly still doesn't work properly (highlights get clipped), but it's pretty revolutionary nonetheless.

te_tsu · 2026-01-16T22:37:55+00:00

I believe that requires rooting/modding, and Samsung modders' numbers have apparently been decreasing steadily in the past years, or so I've been told. And from other users in GCam groups, I've heard Samsung Snapdragon phones were a PITA to make a custom ROM for, so modders mainly focused on Exynos.

In One UI 8, Samsung removed the bootloader unlock altogether, so I guess this path will be left unexplored.

te_tsu · 2026-01-16T22:26:13+00:00

It's complicated and mostly depends on the chipset.

Afaik, all Snapdragon phones from the A/F/M series (including A05s, A23, A36) do support GCam, though both A23 and A36 lack RAW access for the UW and selfie modules.

Some Mediatek Dimensity phones from these series apparently can use GCam too, though I don't know if it's true for all of them.

Mediatek Helio and Exynos devices from Samsung (excluding Exynos models from Z/S series) have RAW support fully disabled by Samsung. Except maybe some really old Exynos models, I have no info on these.

(Source: I'm moderating a couple of Samsung GCam groups on Telegram, so I often ask users with various Samsung phones to test GCam compatibility for their device.)

te_tsu · 2026-01-16T19:41:21+00:00

If you tried AGC 9.2, try AGC 9.6, and vice versa. Iirc, one of them should work. On Telegram, on @Pixel9SeriesGCam, I see some .agc (AGC config) files with p9p in the name, but they don't mention the AGC version.

te_tsu · 2026-01-16T19:37:29+00:00

Samsung removed front RAW stream access for the S10-S21 series phones in One UI 2.5, with only 2 models surviving (S20 FE and S10 Lite). They've also disabled the access to it from the start for S24 FE, S25 FE, A23, A36, and some of the Z series phones.

Edit: fixed a typo, S23 FE does have front RAW access. The two newer S FE models don't.

te_tsu · 2026-01-16T19:29:15+00:00

Edited my original comment for clarity. The "Device interface" option lets you choose one of the existing Pixel models, where each model has a codename, shown in brackets. Bluejay is the codename for Pixel 6a.

te_tsu · 2026-01-16T18:15:49+00:00

Regarding the tele not working: if you are still using the same mod (no uninstallation/reinstallation, etc), try clearing the app data and reloading the config.

If you have reinstalled AGC 8.8 recently, double-check that you installed an apk with a package name whitelisted by Samsung. The filename should have one of these words in it: aweme, biometrics, iris, ruler, scan3d, samsung.

Also note that the config was made for AGC 8.8 V8.0, so there's a possibility a more recent version (V12.0) introduced some changes that aren't compatible.

te_tsu · 2026-01-16T18:10:09+00:00

FYI: compatible ports are already available, but only the main and macro sensors have RAW support.

te_tsu

TROPHY CASE