Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Switch camera modules: 12 megapixels, 50 megapixels, 200 megapixels (Samsung)

Open
#347 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
frontend, mobile

Research direction

Start by reading the camera initialization and settings code to find how Fossify Camera selects its default camera; the issue does not name specific files or tests. Check how available camera modules are exposed on Android devices, then assess whether users can choose a module at startup. Done means the app can use a selected 50- or 200-megapixel module instead of always opening the broken 12-megapixel module.

Written by the indexing model from the issue text.

Description

feature request needs triage
Checklist
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.
Feature description

Hello, I've been having a pretty annoying problem lately. Actually, one of the camera modules on my Samsung S23 Ultra isn't working anymore.
It's the 12-megapixel module.

Because of this problem, I've noticed that many apps that use the default camera—in addition to Fossify Camera—simply don't work anymore.

However, the Samsung Camera app was still working because I had locked it at 200 megapixels.
Following an issue with my phone, I had to reset the Samsung Camera app, which now launches exclusively on the 12-megapixel module by default.

To sum up, I can no longer use the Samsung Camera app because of this issue (the app displays “Camera failure,” freezes, and suddenly closes without allowing me to tap any on-screen options, and there’s nothing in the settings).... I also can’t use Fossify Camera because the app uses the 12-megapixel module by default—the one that’s broken. . and it’s impossible to use the others

So here’s my request.

Is it possible, in the Fossify Camera settings, to change how the app launches so that I can choose which camera module will be used when the app starts? This would allow me to use the 50-megapixel or 200-megapixel module.

Why do you want this feature?

I'd like to be able to use the app.

Additional information

This option could be adjusted directly on the app screen in addition to the settings, just like the photo resolution is currently.

In future updates, the option could adapt based on the phone model chosen by the user,

for example, with a Honor phone, instead of offering three types of photo resolution settings, there would be several. (This is just an example; I don’t own a Honor.)

The only solution I’ve found is to use my phone’s front-facing camera, but that’s not practical for taking photos—especially if I’m traveling or anything like that. And right now, I don’t have the budget to buy a new phone or get this one repaired.

Dominant language
Kotlin
Stars
473
Forks
56
Avg merge
2d 7h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FossifyOrg/Camera

All issues in FossifyOrg/Camera

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.