Shoot in RAW on Sumsung M31 - Samsung Galaxy M31 Questions & Answers

I want to shoot in RAW on M31. Can anyone help me with this?
Some Problems I faced:-
1. I read that we can enable RAW support with TWRP
2. by enabling Camera2Api. Which requires ROOT. (don't have a reliable method NOW)
3. Samsung Enabled PRO mode in September update. But has not enabled RAW support.
~well I (not everyone ) don't need a PRO mode in Stock Camera because there are other apps (like Camera FV-5, Open camera, etc.)
4. The Gcam mod works sometimes and sometimes crashes.(it's totally a mess)(well if the Zcam dev is seeing this, I am still grateful to you as you made a mod that sometimes works .its better than nothing)
if anybody helps me in this regard then I will be thankful

GreateProtim said:
I want to shoot in RAW on M31. Can anyone help me with this?
Some Problems I faced:-
1. I read that we can enable RAW support with TWRP
2. by enabling Camera2Api. Which requires ROOT. (don't have a reliable method NOW)
3. Samsung Enabled PRO mode in September update. But has not enabled RAW support.
~well I (not everyone ) don't need a PRO mode in Stock Camera because there are other apps (like Camera FV-5, Open camera, etc.)
4. The Gcam mod works sometimes and sometimes crashes.(it's totally a mess)(well if the Zcam dev is seeing this, I am still grateful to you as you made a mod that sometimes works .its better than nothing)
if anybody helps me in this regard then I will be thankful
Click to expand...
Click to collapse
No more news bro? Did gcam work?

GreateProtim said:
I want to shoot in RAW on M31. Can anyone help me with this?
Some Problems I faced:-
1. I read that we can enable RAW support with TWRP
2. by enabling Camera2Api. Which requires ROOT. (don't have a reliable method NOW)
3. Samsung Enabled PRO mode in September update. But has not enabled RAW support.
~well I (not everyone ) don't need a PRO mode in Stock Camera because there are other apps (like Camera FV-5, Open camera, etc.)
4. The Gcam mod works sometimes and sometimes crashes.(it's totally a mess)(well if the Zcam dev is seeing this, I am still grateful to you as you made a mod that sometimes works .its better than nothing)
if anybody helps me in this regard then I will be thankful
Click to expand...
Click to collapse
You cannot shoot RAW on Android 10 or above unless:
a) Samsung adds the feature (unlikely)
b) Google gives up the dynamic partitions (very unlikely)
c) You downgrade your phone to Android 9 or below. (which you can)

Related

[Q] n00b question about "userland camera fix"

Hi
XDAndroid is so cool! Of course a few unstabillities.
I have seen that there is an userland camera fix. Does anyone have a link to a thread about this?
I have TD2 Topaz
Actually, user-land support is there in latest builds. However, that doesn't mean that camera is working.
The simplified architecture of Android (or any *nix based system for that matter) is as follows:
Code:
User (You!)
-----------
User-land (Applications, Daemons...etc.)
-----------
Kernel (you could say drivers)
-----------
Hardware
Each level interacts with what's above it and below it directly. Meaning, for the camera to be usable, we still need to wait for the kernel side support which is still a work in progress.
I hope that makes sense.
Yes thank you
pro explanation for noob users! thanx

[11/10][P900 Only][KERNEL] Custom kernel [Basic 1.0 | Pro 1.3]

BASIC KERNEL
Features:
knox removal
adb insecure
selinux permissive
init.d support
busybox
frandom
ntfs rw support with app
PRO KERNEL
Features:
knox removal
adb insecure
selinux permissive
init.d support
busybox
frandom
ntfs rw support with app
synapse support (installs with kernel)
cpu oc/uv support
gpu oc/gpu support
battery tweaks
network tweaks
... and much more
This branch is mainly based on skyhigh kernel (@UpInTheAir)
PRO-VTFB KERNEL
The same as pro branch with vt and fb enabled support.
if doubt, do not use it.
note: booting is longer as usual
CHANGELOG:
v1.3:
- optimization and performance tweaks
v1.2:
- Synced with SkyHigh kernel 1.9
DOWNLOAD
Basic branch v1.0 https://yadi.sk/d/IYF-XNCGbbrPh
Pro branch v1.3 https://yadi.sk/d/SKdK47o1bwJTT
Pro-vtfb branch 1.3 https://yadi.sk/d/XbwusUz8bwJUQ
CREDITS
UpInTheAir, xluco, halaszk88, AndreiLux and many others
SOURCE CODE
https://github.com/bonuzzz/kernel_p900
Great a lot of people have been waiting for this will flash and test it out later tonight
Thanks for your work! Great to see more people with the right knowledge with their hands on a Note Pro.
Unfortunately I use the camera daily....I'll keep an eye on this, though, in case that gets worked out.
ExtremeRyno said:
Thanks for your work! Great to see more people with the right knowledge with their hands on a Note Pro.
Unfortunately I use the camera daily....I'll keep an eye on this, though, in case that gets worked out.
Click to expand...
Click to collapse
I'm a retired deveopler and don't mind helping out a little where I can. I've enjoyed tweaking my P900 to the max & I'm also glad to finally see some stuff coming out here on XDA for the P900 wifi version. Not much activity on any other forum for this device either. Most likely because of the price of the device and people worring about the Knox tripping issue. I noticed on another forum that someone had compiled a fully functional kernel however they too were experiencing issues with the camera. Anybody have any ideas of whats causing the camera issue? I can possibly help out with the developement of a AOSP rom, or a blazing fast slimmed down ROM. I have plenty of developement knowledge in this area, if there are any interest for one. As for the Kernel issues I'm not too familiar with the compiling however most likely could figure it out.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Flashed this kernel and my tablet won't boot
golfinggino said:
Flashed this kernel and my tablet won't boot
Click to expand...
Click to collapse
? I hope you made a backup of your stock kernel before flashing...
Has anyone else flashed this kernel and can confirm if it is booting or not?
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
I started from scratch and flashed the tweaked p900 rom and this kernel and now it is working great it seems to be much quicker then what it was I really appreciate your work and it makes this tablet what it should be
golfinggino said:
I started from scratch and flashed the tweaked p900 rom and this kernel and now it is working great it seems to be much quicker then what it was I really appreciate your work and it makes this tablet what it should be
Click to expand...
Click to collapse
Can you describe what happens when you select the "Camera" application. Does it force close, not launch, display some type of error. If you could provide the details of what happens, it may be possible to provide a working solution or "Work around."
Also, try installing another camera application from the Android Market and see if that application works. Maybe using another camera source will work and that could be a temporary work around till the issue us resolved. Let us know. Thanks!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Mine says warning camera failed
golfinggino said:
Mine says warning camera failed
Click to expand...
Click to collapse
Ok, Thanks. We'll see if we can figure this thing out...
Did you try installing another camera app from the play store and see what happens when you launch it?
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
here's my observations:
1. Samsung Knox does not get removed as claimed in OP
2. Knox FC every time something is installed and uninstalled (likely under different circumstances too)
3. front camera works perfectly fine
4. rear camera does indeed fail
5. Google camera and 3rd party camera apps fail too
6. Z Device Test still detects all the hardware properties of the rear camera (but maybe that info is retrieved from elsewhere in the /system)
7a. all logcat apps do not work. i waited about 3 to 4 minutes for each to load.
7b. I haven't used it on this tab in a long time so I don't know if kernel caused this
7c. yes, I granted SU to the logcat apps, and later verified that SU wasn't denied.
my relevant info:
p900 USA wifi-only 64gb model
P900UEU1ANC5 (XAR)
edit:
to anyone that cannot boot after installing:
1. try wiping cache and dalvik cache
2. re download and try again if above doesn't fix it
3. if above doesn't fix it and you're on NAE, try updating to ANC5 (or newer?) THEN flashing the kernel again
4. if you're on a version newer than ANC5 that might be the problem and you are out of luck until the kernel is updated for it.
don't ask me about how to update, that's your burden
Sterist said:
here's my observations:
1. Samsung Knox does not get removed as claimed in OP
2. Knox FC every time something is installed and uninstalled (likely under different circumstances too)
3. front camera works perfectly fine
4. rear camera does indeed fail
5. Google camera and 3rd party camera apps fail too
6. Z Device Test still detects all the hardware properties of the rear camera (but maybe that info is retrieved from elsewhere in the /system)
7a. all logcat apps do not work. i waited about 3 to 4 minutes for each to load.
7b. I haven't used it on this tab in a long time so I don't know if kernel caused this
7c. yes, I granted SU to the logcat apps, and later verified that SU wasn't denied.
my relevant info:
p900 USA wifi-only 64gb model
P900UEU1ANC5 (XAR)
edit:
to anyone that cannot boot after installing:
1. try wiping cache and dalvik cache
2. re download and try again if above doesn't fix it
3. if above doesn't fix it and you're on NAE, try updating to ANC5 (or newer?) THEN flashing the kernel again
4. if you're on a version newer than ANC5 that might be the problem and you are out of luck until the kernel is updated for it.
don't ask me about how to update, that's your burden
Click to expand...
Click to collapse
thanks for you post
indeed knox doesn't fully uninstall. i forgot two apks to delete.
what program do you test front camera? it is very helpful info to resolve problem
also i have problem with ntfs mount. i will solve on next update.
flashlight doesn't work
bonuzzz said:
thanks for you post
indeed knox doesn't fully uninstall. i forgot two apks to delete.
what program do you test front camera? it is very helpful info to resolve problem
also i have problem with ntfs mount. i will solve on next update.
Click to expand...
Click to collapse
stock, Google camera, and Z Device Test
edit: flashlight does work for me
edit #2: with stock, you can't get to front camera again after switching to rear, because the app will just close when the rear fails. mine was already on front, then I switched to rear and
Sterist said:
stock, Google camera, and Z Device Test
edit: flashlight does work for me
edit #2: with stock, you can't get to front camera again after switching to rear, because the app will just close when the rear fails. mine was already on front, then I switched to rear and
Click to expand...
Click to collapse
i think there is problem with permissions but i can't find where is exactly
bonuzzz said:
i think there is problem with permissions but i can't find where is exactly
Click to expand...
Click to collapse
probably SElinux
Sterist said:
probably SElinux
Click to expand...
Click to collapse
it's permissive
and camera works in stock kernel with selinux permissive.
z device test sees two cameras, so it doesn't kernel problem. back camera and flashlight dont work for me. front camera works fine. i dont have any ideas except permissions
if anyone want to help, this is a kernel without any mods https://yadi.sk/d/-RWbv8htbYW28
ps: replaced link above. logcat is working here
bonuzzz said:
it's permissive
and camera works in stock kernel with selinux permissive.
z device test sees two cameras, so it doesn't kernel problem. back camera and flashlight dont work for me. front camera works fine. i dont have any ideas except permissions
Click to expand...
Click to collapse
that might be the app not able to turn on this tab's LED
torch apps work
Okay, this has nothing to do with me since I have P905 with stock kernel. I just read this thread by curiosity and though one thing about camera. Can you open test menu anyway on that device which opens on 3G models (and phones) by typing *#0*# to dialer (P900 has no dialer right?) There you can perform some tests to device and one is to check does camera work right.
Hope this helps, or then it wont
Spere said:
Okay, this has nothing to do with me since I have P905 with stock kernel. I just read this thread by curiosity and though one thing about camera. Can you open test menu anyway on that device which opens on 3G models (and phones) by typing *#0*# to dialer (P900 has no dialer right?) There you can perform some tests to device and one is to check does camera work right.
Hope this helps, or then it wont
Click to expand...
Click to collapse
p900 doesn't have dialer
z device test detects both cameras..
i now realize why it seems much faster - i am running with interactive and fiops and it is contantly at 2000mhz no lower frequencies are being used - i though it was like this on performance not interactive - obviously the battery is not great right now lol

Install multiple versions of GCam on Redmi k20 pro

Hello guys, I just bought this phone and was blown away how the GCam clicks way better photos, but I saw that I loved both the san1ty and MGC ports. But cannot install both of them, can only install only one port. Do you know a method which I can install multiple versions of GCam on this phone without any interruption or problem. I tried the APK editor method but it's seemed too complex and with little help in Google it just throws parsing problem while installing.
Download Lucky-Patcher
Install one of your camera ports
Launch Lucky-Patcher > Search for your new camera app > Tools > Clone App > Modify Manifest, resources & classes
Uninstall the old App
Install Camera App #2
Done
You can install more than two cameras, simple clone your first installed app again and repeat the steps above
Working and up-to-date Cam Ports:
san1ty 6.2.0.30
celsoazevedo.com/files/android/google-camera/dev-san1ty/
Arnova8G2 6.2.0.30 / 6.3.0.17
celsoazevedo.com/files/android/google-camera/dev-arnova8G2/
celsoazevedo.com/files/android/google-camera/dev-arnova8G2-beta/
Urnyx05 6.2.0.30
celsoazevedo.com/files/android/google-camera/dev-urnyx05/
xtrme 6.1.0.21
celsoazevedo.com/files/android/google-camera/dev-xtrme/
// If possible shoot in RAW and use Lightroom-App / Snapseed
Could someone download, verify and share these versions: ?
4pda.ru/forum/index.php?showtopic=774539&st=17400#entry86676803
4pda.ru/forum/index.php?showtopic=937006&st=5240#entry87626067

[MOD][FIX] Audio Bitrate Increase For Poco X3 NFC

Disclaimer :
Code:
I am not responsible for any damage to your device!
Use this mod at your own risk!
What's this?
This mod increases the audio bitrate on video recording from a disgraceful 96kbps to a respectable 320kbps. Thus, giving a richer, more pleasing audio quality.
Still confused? Click here for a better explanation
Requirements :
- A rooted phone with magisk installed
- An opened mind (important!)
Contributors :
@Jt380p
@Slim K
* NOTES * (READ) :
- Not all ROMs are compatible with this mod, you might end up in a bootloop. YOU HAVE BEEN WARNED!
Download :
https://drive.google.com/file/d/1wr-p7puOL8nYb1wj1AyVbh9XmMp5kRKI/view?usp=sharing (Flash with magisk manager)
Source :
https://forum.xda-developers.com/Mi-9/themes/magisk-audio-bitrate-increase-t3927810
Audio files provided by @Slim K
Thanks to :
@Slim K
@topjohnwu for Magisk
Created : 7/11/2020
Last updated : 7/11/2020
reserved
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Slim K said:
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Click to expand...
Click to collapse
For me it works on Stock, but not on Urnyx05 GCam. Thanks Dev.
Lineage android 11 will benefit from it, or that is already implemented in them?
So which ROMs are not compatible?
Aki-to said:
So which ROMs are not compatible?
Click to expand...
Click to collapse
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Slim K said:
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Click to expand...
Click to collapse
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
This mod is also so extremely tiny, you could pretty much make these changes manually. Just take care of permissions and replace the file, that's it. It's even less complicated than working with /etc/fstab, it seems.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Aki-to said:
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
Click to expand...
Click to collapse
You assume correctly. The path to the functions can be usually found in /data/adb/magisk/util_functions.sh on your device.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Click to expand...
Click to collapse
Why write code twice when it already exists and works for everyone.
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
nike1973 said:
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
Click to expand...
Click to collapse
Yes it works
Thank you. Works on MIUI EU 12.0.6.
Eu 12.0.6, super stabilization (on stock camera) crashes when module is active.
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
Anyone tried on Xiaomi.eu rom?
Running 12.0.8.
Hi!
gkhnkaanyrtc said:
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
View attachment 5272691View attachment 5272693
Click to expand...
Click to collapse
Hi! I have the same problem ... Did you fix it? I use Miui 12.0.1 with Android 11
320kbps should be the default, I wonder why the f**k Xiaomi gives us 96kbps.
Does it work in Pixel Experience rom on Surya?

Question GSI Anyone? (maybe some dev interest?)

Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it
Bwhite... said:
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it
Click to expand...
Click to collapse
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...
domineus said:
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...
Click to expand...
Click to collapse
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.
Bwhite... said:
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.
Click to expand...
Click to collapse
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers
domineus said:
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers
Click to expand...
Click to collapse
ok thank you for all this useful information.
Sorry for the stupid question, but what is GSI? is this a custom rom?
NeoGoku123 said:
Sorry for the stupid question, but what is GSI? is this a custom rom?
Click to expand...
Click to collapse
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com
domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).
NikG25 said:
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).
Click to expand...
Click to collapse
I wasn't able to fix them but I didn't try. I don't have the dev machine to try and fix the issues and rebuild a LoS GSI to get it working. Which is a shame :/
But given that I have had a really good time with it otherwise because I like the potential of it

Categories

Resources