yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A52s 5G] sanderbos:
Okay, I actually got something working on A52s, thanks to a comment from Windoors here:

https://xdaforums.com/t/gcam-port.4253773/post-85637019

You have to change the Photo Session, and no I have no idea what that is or what the values below actually mean.

To make it concrete, here is how I got GCam working on the A52s (emphasis on 'S'):

- Download and install

BSG: MGC_8.1.101_A9_GV2a

Download MGC_8.1.101_A9_GV2a by BSG.

www.celsoazevedo.com

I picked the ruler package name version

- Load luke-A52-BSG-GV1.xml from the configs section of the URL above (location of file does not matter, double tap next to shutter button and select it).

- Now you have a camera app that freezes up after 3 seconds on A52s (you can still take pictures before that freeze)

- Go to the Settings, then

Modules

Back (1.0)

Session of photo modes (near the bottom of the list)

Photo

and enter the value 61448

Then do the same for

Settings / Modules / Back (1.0) / Session of photo modes / Portrait / 61448

Settings / Modules / Back (1.0) / Session of photo modes / Night Sight / 61448

Settings / Modules / Back (0.5) / Session of photo modes / Photo / 61448

Settings / Modules / Back (0.5) / Session of photo modes / Portrait / 61448

Settings / Modules / Back (0.5) / Session of photo modes / Night Sight / 61448

Settings / Modules / Front (1.0) / Session of photo modes / Photo / 61448

Settings / Modules / Front (1.0) / Session of photo modes / Portrait / 61448

Settings / Modules / Front (1.0) / Session of photo modes / Night Sight / 61448

Settings / Modules / Front (1.2) / Session of photo modes / Photo / 61448

Settings / Modules / Front (1.2) / Session of photo modes / Portrait / 61448

Settings / Modules / Front (1.2) / Session of photo modes / Night Sight / 61448

And presto working GCam with all camera's working, both for photos and videos.

When I first wrote this post I was just glad to have something working, but now many months later I can say this 'recipe' has been what I have been using for many months (I have now switched, see my message from Feb 6 2022 in this thread, but if you're starting out I recommend the way described here).

If you want to try it with other GCam versions, that 'Session' value is stored in different locations.

For instance in Gcam-8.1.101.build-V6.2.211013 from Arnova8G2 it is under Settings|Advanced|Stream Config|Enable OPMode and then set it for Main

and in MGC_8.3.252_V0e it is under Settings|Photo modes session config|Session ID

But both of these versions at least initially appear to have less stability and features, so I am at least for continuing to experiment with MGC_8.1.101_A9_GV1u for now.
[Samsung Galaxy A52s 5G] althafjava:
Not working front camera continue to freeze
[Samsung Galaxy A52s 5G] sanderbos:
But the back camera no longer freezes for you now?

I just tried the front camera again on my A52s. for me it is working fine. DId you really change the value in three different locations in the configuration?
[Samsung Galaxy A52s 5G] do-tim:
Working for me thx!
[Samsung Galaxy A52s 5G] dexlemaffo:
Had the freezing bug before I stumbled upon your post. I was afraid it gonna mess up the phone but it was worth the shot!

Thanks a lot !

PS : Just got a new A52S (8/256) yesterday, I'm wondering why XDA doesn't have a proper page for the model (I know for sure that it has the same camera setups as the previous models (A52 LTE and A52 5G)
[Samsung Galaxy A52s 5G] Pegli010:
This one worked for my new a52s :-)

Unfortunately, in a Telergram group I found that the max shutter speed has to be set at 8 seconds.

This way, the total exposure time is way shorter.

It could be nice if it could be possible to get more frames, in order to reach a total exposure of about 4 minutes (just like the astro mode on the pixels and in other gcams)
[Samsung Galaxy A52s 5G] sanderbos:
I am not sure what you are saying.

You are aware that the MGC_8.1.101_A9_GV1u GCam used in my description above does have an Astro mode? If you go to the night sight mode in that GCam version, and open the settings from the top, you can enable the astro mode. And if you take a picture with that enabled it will take an exposure of about a minute and a half.

(Admittedly, I still have not really tried it successfully, so I do not know for sure that it actually really works, but that is mostly caused by clouds....)
[Samsung Galaxy A52s 5G] Pegli010:
Thanks sanderbos :)

I know about astromode: in other models, it enables exposures of more than four minutes (about fifteen shots of 16 seconds each stacked togheter). Since the a52s has a maximum exposure time of just 10 seconds, the pictures in astromode are limited at about one ad a half minute.

This is the reason of my question if it could be possible to stack more than just 15 shots (I'm not a developer and I have no idea :-) )
[Samsung Galaxy A52s 5G] sanderbos:
I am a developer, but I also have no idea! :-)

Like I said before, I really have not ever taken a useful picture in this mode myself (and it's cloudy again here tonight)

If you go to the GCam Settings|Modules|Back (1.0)|Astro max exposure time

you can force it to 35 seconds. If you then take a picture of night sky (or at least a pitch dark room) it will go to 1 minute 55 seconds of processing. So I wonder whether this 10 second limit is really a thing. But in this GCam version at least on A52s you cannot set it beyond 35 seconds (also not if you try to sneakily force it in the xml config file, which I just tried).

But you are not limited to this GCam version. As I said at the end of the comment of October 24, you are not limited to this one GCam version, it is just that in other versions you have go and find the 'Photo Session Id' setting somewhere in the settings. So you can try to find a GCam version that a) let's you configure the astro mode more and b) let's you set the photo session id to prevent the viewfinder from freezing.

Or did the people in the Telegram group say it is limited for all GCam versions on this phone (again, you can set it to 35 seconds it seems to me, but I cannot really try it out with a real sky).
[Samsung Galaxy A52s 5G] Pegli010:
It's cloudy here, too :) but I tryed in a dark room. With a gcam in my old LG G5, i got a total time of 4 minutes and a bunch of seconds, while with a52s less than two minutes.

I tryed to set it to a longer exposure time: 35 seconds will be useless for stars because they move, a good value should be around 16 seconds (which is the base setting for astrophotagraphy mode in the pixel phones)

The final images seem about the same to me, probably because this phone model cannot take single shots longer than 10 seconds, no matter what gcam settings are.

In a telegram group abaut a52s gcam, I found this:

"-goto night sight turn on astro from drop down menu & IMPORTANT THING IS KEEP 8 SEC PER FRAME "

This a short video about the astro mode on pixels:
[Samsung Galaxy A52s 5G] sanderbos:
Let me start off by saying that I am not that interested in the astrophotography mode, that is not why I use GCam at all.

But I have now become interested in what it means, and what the limitations of my A52s are, I am now just curious.

I did find this article

Astrophotography with Night Sight on Pixel Phones

Posted by Florian Kainz and Kiran Murthy, Software Engineers, Google Research Taking pictures of outdoor scenes at night has so far been the dom...

ai.googleblog.com

which also described what you say, about how it is intended to be 15 shots of 16 seconds each, and then they put them all together compensating for the rotation of earth.

(Note that that article is from 2019, so it is of course possible that Google has changed their optimium settings since then)

And as I said the maximum 'shot-time' for astrophotography with the MGC_8.1.101_A9_GV1u on A52s that I can find is 1 minute 55 seconds, so 115 seconds. It can be less, but not more, for whatever reason.

But I do not think the maximum exposure time is 8 or 10 seconds. Rather I think the limitation is that you can get a maximum of 115 seconds of 'shot-time'. So you can get an exposure time of 16 or even 35 seconds if you configure that, you just can't get those 15 exposures that Google found to be ideal.

It could very well be that 8 seconds is recommended for other reasons, but not for the technical reason that the A52s simply cannot manage more.

I am going to wait for a clear sky and then try with 16 seconds configured, that matches the initial Google recommendation, and then you get a maximum of 7 shots in the maximum alotted 115 seconds. But I will take that photo in Amsterdam, so a lot of light pollution from the city, so it's never going to be great.

[Removed video experiment]

If you take an astrophotography shot in a dark room and expriment with pointing the camera at a different subject every 16 seconds (or every 8 seconds) you can see that it really takes 16 second exposures.

(I also tried to use the astrophotography mode of some other GCam versions, specically MGC_8.3.252_V0e, Gcam-8.1.101.build-V6.2.211013, NGCam_8.2.300-v1.4, but none of them even really wanted to take a long picture even with the lens covered, so MGC_8.1.101etc. is at least not a bad starting point)
[Samsung Galaxy A52s 5G] Pegli010:
Thnks for your experiment, sanderbos :)

I also live in a highly pollute area (Genova, Italy), and I wait for some clear sky to take some pics.

(a little advice: with most gcams, the astrophotography under the "night mode" activates itself only with the phone on a tripod (or laid down steady, better if with the timer on)
[Samsung Galaxy A52s 5G] Jakubek07:
I am using mgc 8.1 with xml and samsun libraries and i was wondering same about expanding exposure, i happend do try in last few days some mode form nikita 7.xxx not sure wich and i foind out it had started 4 minutes exposure but it was buggy build and i forget about it i will try to download bunch of them and try to shoot stars in next week during nightshifts so we can compare
[Samsung Galaxy A52s 5G] sanderbos:
So at least with MGC_8.1.101_A9_GV1u+lukeconfig+a52sphotosessionidfix+setastroexposeto16 it works technically. So only 7 exposures (1m55s) and not 15, but at least you get a picture out it. I now had a first evening with some moments without clouds and I could test a bit. And I could only see 1 star myself so Google saw a lot more, but the result is still not pretty (see attachment).

(An interesting bit in the picture is the line in the middle, thtat was probably a plane or UFO that flew over, but if you count the bright dots in that line it seems to have taken 12 exposures)

But I am guessing that the biggest cause for the picture not being good is not the lack of very long exposure, or the phone or the app, but simply because I took this picture in the middle of a city (I did pick a darkened park) and there is too much light pollution.

You can look at https://www.lightpollutionmap.info/ to see where not too take pictures, and I managed to take my pictures in a bright pink spot, the worst possible place :cool:
[Samsung Galaxy A52s 5G] Jakubek07:
Ok i tryed nikita cam it was NGCam_7.4.104-v1.9_snap.apk wich wid xml cinfiguration file of sa3idis.djelfa.config2samsungA71.xml and seting cameras to sesion module of EISv3 (that setting or seting it to 61448 stops camera from crashin after 2seconds) and surprisingly it gave me over 6 minutes of exposure for astrophotography, sadly that night it was too cloudy so i couldn't review it's real application but sadly for other of uses of this mode it didnot showed any significant upgrade over 1:09 of MGC_8.1.101_A9_GV1n_scan3d.apk, also it fails to focus in dark, i will try it on stars as it might be better at fixed focus on infinity, attached first photo with over 6minutes of exposure second under 2minutes
[Samsung Galaxy A52s 5G] Jakubek07:
Ok yesterday i got chance during night to see some stars but sadly nikitacam was continuously failing to focus, its lacking corect config for a52 so there is no point of its over 6minutes of exposure, it doesn't focus in automatic mode nor when manually seting infinity so for best results i advise MGC_8.1.101_A9_GV1n_scan3d.apk with config for your version of a52 for my a52s 5g i use 🏵️For-A52s(Morgenman)🍁.xml i also noticed that ading specific library doesn't provide any noticeable improvement in image quality and it even add something like dead pixels to resulting image, here i provide no.1 image of nikita version (blurry) no.2 Image of MGC (sharp) and some random night sky with MGC
[Samsung Galaxy A52s 5G] sanderbos:
Thank you for sharing!!

So you made PXL_20211203_201439628.NIGHT.jpg with MGC_8.1.101etc.apk on A52(s)? Because that one is just stunning!

(but PXL_20211213_195539798.NIGHT.jpg is nice too)

I never used Telegram before today, but now I was curious so for others he is talking about this config:

One Power in 📷 Galaxy Gcam • A52 - A72

For BSG 8.1 (MGC 8.1)

t.me

But then you first have to load this library?:

ルーク | Luke in 📷 Galaxy Gcam • Repo

Lib to be used in 8.1 gcam Tuned for samsung devices Thanks to morgenman

t.me

Or are you saying you used that config but did not load the library?

Does that also help make regular photos better, because in the end I don't really care about Astophotography ?

(although I did just realize I will be in a darker spot on earth on Christmas day)
[Samsung Galaxy A52s 5G] Jakubek07:
Yea i tryed ading libraries but it result in some false lights (like dead pixels from camera or something) best results jut from stock MGC app or only with config (xml) file added, i am looking forward for February because android 12 will come to this device and it should bring new ports
[Samsung Galaxy A52s 5G] sanderbos:
Okay, thanks for your reply, I think I will just stay on he luke config file then, because I think that that morgeman config file is only meant for if you use the lib as well. I'm actually also quite happy with MGC 8.1.101+luke, I am not really looking for more.

I don't share your optimism with respect to Android 12. I've had in the past two times on other phones that a major Android upgrade made the GCam version I was using at the time stopped working and I was forced to switch.

And the new Pixels come with their own unique tensor co-processor, which I guess the GCam on the Pixels may be using (also maybe not), so maybe future GCam updates by Google will simply not work on other phones.

(and that is actually fine by me, as long as existing GCam versions continue to work on future phones and Android versions)
[Samsung Galaxy A52s 5G] vandal4e:
does it work with forced 4k 60fps + EIS ? or limited to 4k 30?
[Samsung Galaxy A52s 5G] lXlRaideNlXl:
Where did you get the Morgenman xml config? Can you share the link?

EDIT: FOUND IT!
[Samsung Galaxy A52s 5G] gerhard_wa:
I'm so happy for you, that you really finally did find it and that you bothered to share this fantastic news with the whole world. And in all caps no less! Thank you very much for this enormously interesting update.
[Samsung Galaxy A52s 5G] cosmicice.:
Hi,

Thank you so much for sharing this absolutely amazing solution, although I do have one issue, the app refreshes whenever I change my lense from 0.5 to 1.0+. I'm not sure why it happens nor am I sure if it's just for me, but hopefully there's a solution.

Thanks,

cosmicice
[Samsung Galaxy A52s 5G] sanderbos:
The different camera modules do all work though right? For me it's the same, in fact also if you switch to the selfie cam, but I did not even really notice it because it only takes 1 second.

(I do also have sometimes that I switch to the ultra wide and that it stays on regular cam and I have to do it one more time, that is more annoying to me because sometimes I don't notice it)
[Samsung Galaxy A52s 5G] cosmicice.:
Well yeah it's not a big deal, but it kind of sucks when I can't change lenses while I'm taking a video. Also, is it just me, or does the app not rotate icons when I rotate the phone?
[Samsung Galaxy A52s 5G] sanderbos:
Ah, I see. But I would say the bug is more that the 'lens' buttons are not temporarily removed when you record a video (like the Samsung app does, the Samsung app also does not let you switch camera modules while recording video, my guess would be the phone hardware can't do that).

Edit: Oh, I had 1080p@60fps configured in the Samsung camera app, then you cannot switch cameras, but in 4K mode you can indeed switch as cosmicice points out in the next comment.

And for me the icons do rotate when I rotate the phone (for instance the numbers in the 'lenses' and the arrows in the selfie cam switch).
[Samsung Galaxy A52s 5G] cosmicice.:
I'm not sure, the stock camera app by Samsung let's me switch modules between 0.5 to 1.0+. I've attached a video for you to see.

Also the number in the lenses do rotate for me, but only if I switch my phone's orientation to landscape, which is fine but not great.

edit: xda didn't accept my upload, here's a link:
[Samsung Galaxy A52s 5G] sonic_ear:
I try to Google it but didn't make it, can you help me?
[Samsung Galaxy A52s 5G] Saky22:
Here you go
[Samsung Galaxy A52s 5G] sonic_ear:
Thanks man appreciate so much 😁.
[Samsung Galaxy A52s 5G] Rene040:
Does anybody know if the Gcam + Morgenman XML still works on Android 12? Or any Gcam for that matter?
[Samsung Galaxy A52s 5G] sanderbos:
I am not using Morgenman config, but very likely it will work just fine because

MGC_8.1.101_A9_GV1u + luke-A52-config + PhotoSessionFix

still works great on

A52s+Android 12
[Samsung Galaxy A52s 5G] Rene040:
That's great news, I believe the Morgenman is just the Luke config+ the fix so you don't have to do it manually in settings. ( Haven't confirmed that but it seems like it)
[Samsung Galaxy A52s 5G] sanderbos:
Just for completeness, that is not true.

They are surely based on one each other, but if you look with a diff tool at these files you see a lot of small differences in all kinds of areas of the configuration.

I think the Morgenman file is meant to be used with the Morgenman .so library file, but everybody who uses that config seems to use it without that library :sneaky:

(I also now tried the morgenman xml file linked above in the comment from January 10, so can now confirm it works on A52s+Android 12 :) (without the Morgenman extra library))

It is true that Morgenman config includes the Photo Session Fix so will work out of the box on A52s.

Now that I have used the luke config a number of months and made small personal adjustments, I would say the most 'controversial' aspect of the Luke config is that it increases the saturation by a lot:

Settings|Modules|Back 1.0| Image Processing|Main Settings|Saturation

is set to 1.25, and that leads to very colorful pictures but I found that when I took pictures of white people in dimly lit environments it makes their faces really red.

Just for that reason alone Morgenman (which has that value set to a more modest 1.0625) may be a better starting point.
[Samsung Galaxy A52s 5G] ZizoZipzinger:
Hi, sorry to bother you but I think I messed something up. I installed the latest gcam scan3d version from the 20.01 I think and after loading morgenman xml it still stop working after 3s. What did I miss?
[Samsung Galaxy A52s 5G] sanderbos:
What GCam version is that (link)? Is that an MGC 8.1 version. Because Morgenman config is meant to be used with MGC 8.1 I think (so also not 8.2 or later).

If I look at the BSG releases there was no MGC release on 20.01.2022.

I see now that they recommend a later MGC 8.1 release in the Telegram group, but since I do not use that one I am just going to link to the exact version I use:

BSG: MGC_8.1.101_A9_GV2b

Download MGC_8.1.101_A9_GV2b by BSG.

www.celsoazevedo.com

(and I use the ruler version, but if you want to use the scan3d I think that's just fine)
[Samsung Galaxy A52s 5G] ZizoZipzinger:
https://1-dontsharethislink.celsoazevedo.com/file/filesc/MGC_8.1.101_A9_GV1z_scan3d.apk

This is the link. What config do you primarily use and recommend? Also what adjustments did you make if you would share of course. Thanks a lot!
[Samsung Galaxy A52s 5G] sanderbos:
So that is fine then, the I would say it should work. I could link to my own comment on the top of page two of this XDA thread, but let's push ahead a bit with your files.

So what do you see if you open gcam, have loaded Morgenman config, and go to:

- Dropdown from arrow at the top of the app

- Settings

- Modules

- Back 1.0

- Session of the photo modes (near bottom of long list, you have to tap on it to see the current value)

It should have the value 61448 entered, does it have that for you?

(and if not, you can just enter it now)
[Samsung Galaxy A52s 5G] ZizoZipzinger:
Before morganman I had installed luke and made all those adjustments. However I thought I had to reinstall with a new version for the morganman config(obviously I wasn't thinking clearly) and completely forgot about this adjustment. I tried to change it now but it has different interface than before(attached two photos).

Edit:

I troed entering 61448 on the three options and it started working!

Thanks a lot!

Btw do you suggest to tweak anything else for better processing? Like the interface or HDRNet?
[Samsung Galaxy A52s 5G] sanderbos:
So from the second picture I guess you have to set it three times now, for photo portrait and night sight separately, where previously it was only one value.

So then it would make sense that Morgenman or other older configs do not work, because for instance Morgenman only has 5 such config values in total (one for each module), I just checked the xml for that.

But you can push through now with your version if you want, you just have to manually enter the value 61448 three times probably, and then also for Back 0.5, and Front 1.0.

(Or you can just get the older GCam.... But since you are at this stage you can at least now manually make it work now)
[Samsung Galaxy A52s 5G] ZizoZipzinger:
I tried entering 61448 on the three options and it started working!

Thanks a lot and sorry for wasting your time!

Btw do you suggest to tweak anything else for better processing? Like the interface or HDRNet?