Unless you have a Google Pixel and have the official app, you are likely using a GCam mod on your phone. It is the most popular camera app on Android, because Its performance tends to be much higher than other alternatives and it’s really easy to use.
However, by searching for mods for GCam you will surely have achieved something: there are many variations, so many! This complicates life for users, who don’t know which version to choose for their device.
Taking this into account, and if you are also one of the affected people, we have decided to give you a helping hand. Today we will tell you Why are there so many versions of GCam and which one should you choose?. It’s honestly simpler than it sounds.
What is the development version of Google Camera (GCam)?
Although there are several mod repositories for Pixel Camera (this is the new name of the GCam), there is hardly one more well-known and complete than Celso Azevedo’s site. They practically publish on their blog all the great GCam developers within the Android community. Plus, everything is organized as neatly as possible, so our entire tutorial will start from there.
Entering the GCam Hub by Celso Azevedothe first thing you will find is a list of stable releases of GCam mods. Come on, you’ll see a list that says things like “Google Camera 9.X”, “Google Camera 8.6 – 8.9” and more.
This is easy to understand, as it only refers to the development version of GCam on which the mods are based. Depending on the version selected, you will find more or less functionalityalthough development of a mod may not have been completed in newer releases.
Furthermore, The minimum Android version is mentioned in the same list which you should use with each version. And what happens when you select a development version? This is where the doubts begin, but now we will help you.
Why are there GCam variants called BSG, BigKaka, Shamin and others?
When you choose a development version of GCam, you will surely find different variations of them. These appear with names like the following:
- BSG 9.2: MGC_9.2.113_A11_V29 (BSG, 05-10-2024, configurations, Android 11+).
- Big Kaka 9.2: AGC9.2.14_V13.0 (BigKaka, 05-08-2024, configurations).
- Big Kaka 9.1: AGC9.1.24_V15 (BigKaka, 2024-04-24, configurations).
- BSG 9.1: MGC_9.1.098_A11_15 (BSG, 03/30/2024, configurations, Android 11+).
- Shamim 9.1: SGCAM_9.1.098.24_STABLE_V10 (Shamim, 13-11-2023).
What does everything indicate? The first thing is the pseudonym of the developer of that modpeople like BSG, BigKaka and Shamin. There are many GCam moddersbut these are some of the most famous.
Next is the development version on which a mod is based (9.2, 9.1, etc.) and here a small detail comes into play: even if the version is the same, there are probably some small differences between the mods by every developer.
Then it appears the package namewhich offers additional and slightly more detailed information. With it you can know who developed the mod, exactly which variant of the GCam it is based onwhat is the published version and more. Let’s look at an example:
MGC_9.2.113_A11_V29:
- MGC: Indicates that this is a mod developed by BSG (all its packages have this ID).
- MGC is from BSG, AGC is from BigKaka, SGCAM is from Shamin and so on.
- 9.2.113: it is the exact development version of the GCam on which the mod was created.
- A11– The minimum recommended version of Android (some developers do not indicate it).
- V29– The specific version of the mod for that variant (higher, better developed).
Finally, There is a set of data in parentheses and also provide further information:
- Developer pseudonym.
- Date that version of a mod was released.
- A link to specific configurations for certain mobile phones (configurations).
- The minimum recommended Android version.
So far, so good, everything has become much easier to understand, REAL? Well, it turns out that one more detail is missing which is also very important.
What are snap, scan3d, aweme, meitu, ENG and more in GCam mod packages?
When you select the version of a Google Camera mod from a specific developer, you you’ll find a handful of additional variations. They are APK packages with different names, saying things like “snap”, “scan 3d”, “aweme”etc.
You will surely think: “Isn’t it easier to just make a universal APK and stop worrying?”. The truth is that yes, and that’s the truth all packages are very similarbut the problem is how cell phones use cameras.
Some manufacturers (like OnePlus or Samsung) only allow access to all cameras using a package name in their whitelist. If not, you can only use the main camera. In other cases, the GCam app will constantly crash if you don’t use a compatible package or you won’t be able to install it at all.
There are cases so extreme that you can only use a mod directly. of the GCam if you install a custom ROM on your phone that is not based on the stock ROM (ColorOS, OxygenOS, One UI, etc.). Although there is also the other extreme, as in ASUS or Xiaomi, where freedom is almost total.
What should you do? The ideal is to try the different packages until you find what works for you, but here it is a quick guide on how they should be divided:
- No specific package name: It is the universal version of the APK.
- ENG.apk (com.google.android.GoogleCameraEng): mod compatible with Google Lens.
- glens.apk (com.google.android.glens): mod compatible with Google Lens.
- snap.apk (org.codeaurora.snapcam): phones with Snapdragon or OnePlus chips.
- qcamera.apk (org.codeaurora.qcamera3): For phones with Snapdragon chips.
- aweme.apk (com.ss.android.ugc.aweme): smartphones Realme, OPPO and OnePlus.
- ruler.apk (com.samsung.android.ruler): devices produced by SAMSUNG.
- scan3d.apk (com.samsung.android.scan3d): devices SAMSUNG.
- meitu.apk (com.meitu.meiyancamera): cell phones Realme, Vivo, OPPO or OnePlus.
Now, knowing all this, you will surely find the perfect version of GCam for your mobile. Can you tell us how it went?
