Related
Greetings guys, ive seen that the camera api 2 is still broken for galaxy s6 in the android m, this can be checked easelly by running any custom camera app like camera fv 5, a better camera or proshot camera.
All of them return blurry pictures with camera api 2, while works flawlessly with old camera api.
Even though im very very happy with the galaxy default camera app finally supporting shutter speed and raw, i was hoping the camera api 2 wouldve been properly implemented in this build which unfortunatelly it wasnt.
So im trying to do get as much data as possible by asking you guys to post your phone model, android version, sensor brand/model and experience with camera api 2:
Ill go first:
Phone: G920F
Android: Android 6.0.1
Camera Sensor: Sony_IMX240 (To check your sensor install this app from google play: https://play.google.com/store/apps/details?id=com.finalwire.aida64&hl=pt_PT)
Testing:
ProShot(Paid) Blurry pictures,
Camera FV5(Paid)=Blurry Camera API2 (Resolution maximum of 8mp) and up to 3200 iso, but normal image quality with old camera api (Resolution maximum of 16mp) but only 800iso,
A Better Camera (Paid) Blurry Camera Api2 but normal image quality with old camera api.
This problem is included in lollipop 5.1.1
I talk with proshot developers for this problem 5 months ago and he hasn t solution
supera3 said:
This problem is included in lollipop 5.1.1
I talk with proshot developers for this problem 5 months ago and he hasn t solution
Click to expand...
Click to collapse
Hi! I'm the dev of ProShot. I'm really stumped on the soft images issue on Samsung phones. If you shoot RAW you will see that correct focus was achieved, but the JPEG doesn't look quite right. Running a simple sharpen filter produces results closer to the stock camera app, but it's not quite 100%.
No other device has this issue, so Samsung is definitely at fault here. And only offering 8MP resolutions in Android M is a pretty bad oversight, they clearly didn't test this update that well :/
Hi all , I have to say that with CameraFV all problems said up are same here - blury detail on jpg photo , 8mpx max resolution for jpgs in MM. But in RAW everything is just right - detail and resolution. Dont know where is problem but think on 90% is base on Samsung's camera driver. Dont know also situation in S7.
A made also comparisson between RAWs in CameraFV and Stock Camera app for Sammy and may say that cameraFV take better detail at all , stock camera app has more noise and detail is more aggressive.
If u want i can upload reaults here to discuss
Cheers !
edee1337 said:
Hi! I'm the dev of ProShot. I'm really stumped on the soft images issue on Samsung phones. If you shoot RAW you will see that correct focus was achieved, but the JPEG doesn't look quite right. Running a simple sharpen filter produces results closer to the stock camera app, but it's not quite 100%.
No other device has this issue, so Samsung is definitely at fault here. And only offering 8MP resolutions in Android M is a pretty bad oversight, they clearly didn't test this update that well :/
Click to expand...
Click to collapse
Thank you for your contribution people, both camera fv5 and proshot are excelent camera apps. I actually love the ability to disable ois in proshot and the very nice ui. It is indeed a shame that samsung didnt pay more attention to fix buggy camera api 2. I really like the stock app in MM it has pretty much everything and im very happy with it but the phone camera couldve been even more perfect than it already is with proper support for custom camera apps :/
edee1337 said:
Hi! I'm the dev of ProShot. I'm really stumped on the soft images issue on Samsung phones. If you shoot RAW you will see that correct focus was achieved, but the JPEG doesn't look quite right. Running a simple sharpen filter produces results closer to the stock camera app, but it's not quite 100%.
No other device has this issue, so Samsung is definitely at fault here. And only offering 8MP resolutions in Android M is a pretty bad oversight, they clearly didn't test this update that well :/
Click to expand...
Click to collapse
Does this happen in S7 or S6E+ Marshmallow?
Yesterday I borrowed my friends LG G4 and found out they still have best implementaion of camera2 api.
Smasung photos will have always have grennish yellowish tint.
sarvesh563 said:
Does this happen in S7 or S6E+ Marshmallow?
Yesterday I borrowed my friends LG G4 and found out they still have best implementaion of camera2 api.
Smasung photos will have always have grennish yellowish tint.
Click to expand...
Click to collapse
Still haven't been able to get the MM update on my S6, but from other reports I hear it still might be there.
I use ProShot and I get blurry shots on my S6 but to be honest some pictures come out awesome, as if shot using a DSLR, and some it's just too soft. It's not the dev's fault, it's Samsung's.
I use ProShot on my LG G4 also and it doesn't have an issue with that. Noise Reduction removal is better in the G4 as well. In the S6 you see some type of weird over sharpening effect.
What I love about ProShot (with low noise reduction) is that it removes Samsung's over sharpening effect and extreme contrast so pictures come out natural.
---------- Post added at 06:03 PM ---------- Previous post was at 06:03 PM ----------
edee1337 said:
Hi! I'm the dev of ProShot. I'm really stumped on the soft images issue on Samsung phones. If you shoot RAW you will see that correct focus was achieved, but the JPEG doesn't look quite right. Running a simple sharpen filter produces results closer to the stock camera app, but it's not quite 100%.
No other device has this issue, so Samsung is definitely at fault here. And only offering 8MP resolutions in Android M is a pretty bad oversight, they clearly didn't test this update that well :/
Click to expand...
Click to collapse
Here's the interesting thing, when you disable noise reduction on the S6, the pictures are sharp and not blurry.
TheWarKeeper said:
Greetings guys, ive seen that the camera api 2 is still broken for galaxy s6 in the android m, this can be checked easelly by running any custom camera app like camera fv 5, a better camera or proshot camera.
All of them return blurry pictures with camera api 2, while works flawlessly with old camera api.
Even though im very very happy with the galaxy default camera app finally supporting shutter speed and raw, i was hoping the camera api 2 wouldve been properly implemented in this build which unfortunatelly it wasnt.
So im trying to do get as much data as possible by asking you guys to post your phone model, android version, sensor brand/model and experience with camera api 2:
Ill go first:
Phone: G920F
Android: Android 6.0.1
Camera Sensor: Sony_IMX240 (To check your sensor install this app from google play: https://play.google.com/store/apps/details?id=com.finalwire.aida64&hl=pt_PT)
Testing:
ProShot(Paid) Blurry pictures,
Camera FV5(Paid)=Blurry Camera API2 (Resolution maximum of 8mp) and up to 3200 iso, but normal image quality with old camera api (Resolution maximum of 16mp) but only 800iso,
A Better Camera (Paid) Blurry Camera Api2 but normal image quality with old camera api.
Click to expand...
Click to collapse
There is a app called cinema 4k which also uses camera2 api. It didn't work on marshmallow so i had to downgrade to lollipop, after downgrading it worked without any problems
the tech blog on insta said:
There is a app called cinema 4k which also uses camera2 api. It didn't work on marshmallow so i had to downgrade to lollipop, after downgrading it worked without any problems
Click to expand...
Click to collapse
Thats because when you downgraded the camera api 1 was used by the app bu default instead of camera api 2
TheWarKeeper said:
Thats because when you downgraded the camera api 1 was used by the app bu default instead of camera api 2
Click to expand...
Click to collapse
Whats the difference between camera1 api and camera2 api
Camera FV-5 fixed. (16Mpix available, etc...)
atherion said:
Camera FV-5 fixed. (16Mpix available, etc...)
Click to expand...
Click to collapse
Which version you use
don_gori said:
Which version you use
Click to expand...
Click to collapse
Latest 3.15.1
I have some issues with RAW capturing on 3.15.1 , on 10 photos only 1 had DNG file ?
Hi!
I'm on stock marshmallow with the august security patch. According the the manual camera test app my phone does not have raw capabilities. What could be causing this? (I can capture raw with the default camera app just fine)
4k issue on galaxy s7 shots 3264x2448 instead of 3840x2160 using Proshot. Please fix this. No 60fps for FHD option as well.
I am aware that our Mix uses a 1/3.06" 16MP Omnivision Sensor with a Pixel size of the measly 1um. But the Huawei Mate 9 has a similar sized sensor (1/2.9" 12MP sensor with a pixel size of approx. 1.25um.) and shoots really great pics. Obviously Huawei may have used a latest generation Sony sensor with Leica's optics which will blow the Omnivision away. Even the cheapest Sony sensor would outperform an Omnivision any day.
My question is, will shooting images at a lower resolution like 12MP on the Mix give us better results? I'm not expecting Mate 9 like results as the phone's camera was never a priority when I bought this device. But would this help reduce noise or give us better results compared to shooting at 16MP? I am noticing lower noise when shooting at 13MP on Open camera compared to shooting at 16MP.
Does shooting at a lower resolution increase the Pixel size from 1um? Or is it strictly something to do with the sensor? Does the sensor behave the same either way and are we just getting cropped images when shooting at lower resolutions?
I've read in a few places that the sensor is fully utilized regardless but shooting at lower resolutions can reduce noise. If I can at least get half decent 12MP images compared to noisy unreliable 16MP ones, I wouldn't mind shooting at lower resolutions. Of course I am not expecting ground breaking image quality.
Some older Sony phones like the Xperia Z2 used to have a default mode which clicked images at 8MP even though the effective sensor resolution was 21MP. Sony claimed that the lower resolution gave batter images especially lesser noise. I am referring to something like this.
Hope someone can explain this.
@satishp did a search on dpreview.com
https://www.dpreview.com/forums/thread/2995010
The 2nd reply sums it up pretty well.
The answer to your question is no, reducing the resolution will not increase your image quality. The sensor always takes full-resolution image. Reducing resolution is a post-processing function and is no different than reducing resolution on the computer. Note that there are a few cameras with special low-resolution modes that are supposed to improve either the image or performance in certain ways. But when you have these modes you know it because they’re selling features of the camera.
There is now a significant amount of information available publically demonstrating that image quality depends on sensor size and sensor efficiency only. The number of pixels doesn’t matter. When printed at the same print size, images from the same sized sensor exhibit the same amount of noise regardless of resolution.
Thorin78 said:
@satishp did a search on dpreview.com
https://www.dpreview.com/forums/thread/2995010
The 2nd reply sums it up pretty well.
The answer to your question is no, reducing the resolution will not increase your image quality. The sensor always takes full-resolution image. Reducing resolution is a post-processing function and is no different than reducing resolution on the computer. Note that there are a few cameras with special low-resolution modes that are supposed to improve either the image or performance in certain ways. But when you have these modes you know it because they’re selling features of the camera.
There is now a significant amount of information available publically demonstrating that image quality depends on sensor size and sensor efficiency only. The number of pixels doesn’t matter. When printed at the same print size, images from the same sized sensor exhibit the same amount of noise regardless of resolution.
Click to expand...
Click to collapse
Thanks for clearing this! So it may have been placebo that the images shot at 12MP seemed to be less noisy to me. Lol!
I use Open Camera which seems to produce brighter images compared to the stock camera. I'm sure these 3rd party apps aren't magically making the sensor capture more light compared to the stock app. I've noticed that these apps automatically crank up the display brightness to max as soon as they are launched. There may also be some real-time processing involved which makes the images appear brighter and slightly better compared to the stock app.
I am considering getting the Sony Alpha QX1 (with inter-changeable lenses) or the older QX100 which would make the Mix perfect! These lens style cameras attach to the phone and transfer images directly to the phone via NFC pairing. Just wondering whether the mix is too wide for the bracket on the lenses. The QX1 has the same APS-C sensor utilized on some of Sony's Alpha range and the QX100 has the 1" BSI sensor used on the RX100II. Only downside is that none of them can do 4K video.
Thanks again! Cheers!
satishp said:
I am considering getting the Sony Alpha QX1 (with inter-changeable lenses) or the older QX100 which would make the Mix perfect! These lens style cameras attach to the phone and transfer images directly to the phone via NFC pairing. Just wondering whether the mix is too wide for the bracket on the lenses. The QX1 has the same APS-C sensor utilized on some of Sony's Alpha range and the QX100 has the 1" BSI sensor used on the RX100II. Only downside is that none of them can do 4K video.
Thanks again! Cheers!
Click to expand...
Click to collapse
You will need this - https://www.amazon.com/SPA-TA1-Tabl...UTF8&qid=1483946210&sr=8-2&keywords=qx+tablet
The smallest one should work perfectly with the phone. I had the QX-100 and it didn't fit the note 4 out of the box.
emann56 said:
You will need this - https://www.amazon.com/SPA-TA1-Tabl...UTF8&qid=1483946210&sr=8-2&keywords=qx+tablet
The smallest one should work perfectly with the phone. I had the QX-100 and it didn't fit the note 4 out of the box.
Click to expand...
Click to collapse
Seems to be quite expensive just for an attachment. If it didn't fit the Note 4, it most definitely won't fit the Mix. So I guess that attachment is a must and when you add the price of the QX1's body + Lens + the attachment, it doesn't seem to be worth it. Ofcourse, the images would blow away even the best of mobile cameras.
Only if it was priced right!
I have the QX-30, the tablet mount is a must unless you plan on not attaching it to the phone. It makes the overall portability not so great, you're probably better off just getting a full blown dedicated camera but the QX-1 might be good, just make sure to buy one of the lenses otherwise you can't do anything, the SELP1650 might be decent I think.
Also if you're thinking of getting the swiveling rotation mount, don't bother, it's not compatible with the tablet mount.
For those who haven't tried RAW capture yet, stock camera works perfectly fine after activating the camera2 api. Just thought I should mention that since it's not such an uncommon issue.
Camera
benziii said:
For those who haven't tried RAW capture yet, stock camera works perfectly fine after activating the camera2 api. Just thought I should mention that since it's not such an uncommon issue.
Click to expand...
Click to collapse
How do you do that. please give us instructions on how to.
jaime4272 said:
How do you do that. please give us instructions on how to.
Click to expand...
Click to collapse
Add the line "persist.camera.HAL3.enabled=1" at the end of your build.prop, then reboot. It goes without saying you either need a build.prop editor or like me, just use the text editor that comes with Root explorer for example. Next get a camera app that supports RAW, like Open camera or Manual camera.
[Edit] Remember to mount as read/write when you are in system folder, or your changes won't stick. Our build.prop has two empty lines at the bottom, so if you have added something at an earlier time, make sure you have one empty line at the end.
benziii said:
For those who haven't tried RAW capture yet, stock camera works perfectly fine after activating the camera2 api. Just thought I should mention that since it's not such an uncommon issue.
Click to expand...
Click to collapse
Only for my understanding
Does it only activate RAW mode or does it increase the picture quality for ordinary mode too?
vergilbt said:
Only for my understanding
Does it only activate RAW mode or does it increase the picture quality for ordinary mode too?
Click to expand...
Click to collapse
There is more to it than just RAW. Read up on camera2 features and what an api is. But to answer your question, no, it does not increase quality.
Apps that support raw
benziii said:
There is more to it than just RAW. Read up on camera2 features and what an api is. But to answer your question, no, it does not increase quality.
Click to expand...
Click to collapse
I downloaded camera FV-5 which support raw the option said that this phone does not support RAW, any idea?
jaime4272 said:
I downloaded camera FV-5 which support raw the option said that this phone does not support RAW, any idea?
Click to expand...
Click to collapse
Even though I know FV-5 has been praised for years, I've never bought it. I'm not a big snapper so I've often been content with manual modes on the stock cameras. But since I have recently gotten RAW capture going, I've contemplated loosely on paying for either Manual camera or Camera FV-5. All I've tried on the Mix so far, is Manual camera's compatibility app (which checks out), and taken some RAW pics with Open camera.
I'm going to check out some more apps soon.
Considering it is required for RAW capture, I reckon you have a paid version? I quickly tried the free one, and see only one instance of compatibility (under general photo settings). But there is nothing there. Do you get the message when you change picture output?
There is an option on the paid version but it's grayed out because of incompatibility, but there is
you don't improve the noise performance by taking a smaller resolution, you do that by downsizing from a large image.
I think the best method is to use a good manual setting, shoot in raw and then edit in post processing.
however I think the images aren't that reliable
I cannot Open the dng file
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Snapseed and Lightroom cannot parse the dng File ....Amy Help?
gorillalaci said:
I cannot Open the dng file
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Snapseed and Lightroom cannot parse the dng File ....Amy Help?
Click to expand...
Click to collapse
On my desktop I use UFRaw and Gimp / Photoshop. But I haven't gotten any mobile apps to open my RAW images either. Weird.
I know this is a few months old, but I think this app needs to be better known:
https://play.google.com/store/apps/details?id=troop.com.freedcam
Yes, it works with DNGs and can handle our Mix Camera sensor. And yes, it's 100% FREE.
Also, it comes from a XDA dev, so even more kudos for him!!
codymamak said:
I know this is a few months old, but I think this app needs to be better known:
https://play.google.com/store/apps/details?id=troop.com.freedcam
Yes, it works with DNGs and can handle our Mix Camera sensor. And yes, it's 100% FREE.
Also, it comes from a XDA dev, so even more kudos for him!!
Click to expand...
Click to collapse
Installed it, but crashing when try to tap to focus.. Autofocus doesnt work it self
I have it working, but I'm using the LOS 14.1 build 20.5.17 from here on XDA, not MIUI. Sorry but I didn't test stock ROM before flashing.
Also, you can contact the dev at this thread here at XDA: https://forum.xda-developers.com/android/apps-games/camera-freedcam-4-0-3-t3115548
Maybe he can help out.
Hi,
I'm the developer of Open Camera ( http://opencamera.org.uk/ / https://forum.xda-developers.com/android/apps-games/app-camera-t2850557/ ) and was wondering what people's experiences were on the OnePlus 3T with third party camera apps that use Camera2 API?
I've tested a few different third party cameras on my OnePlus 3T, with Camera2 enabled as follows:
Open Camera: enable Settings/"Use Camera2 API".
A Better Camera: enable Settings/General settings/More/"Use Camera2 interface".
Snap Camera HDR (Trial): enable Settings/Other/"Use Camera2 API".
Camera FV-5: this uses Camera2 by default.
AZ Camera: this uses Camera2 by default.
Footej: this uses Camera2 by default.
Lightroom (which has a built-in camera using Camera2)
Mostly things seem good, but there are some issues on my device (these occurred on both Oxygen 4.0.2 and 4.0.3):
* Most seriously, I've seen problems to do with using manual shutter speed. This usually shows in the form of preview corruption (it shows a split-screen, or starts scrolling), but sometimes there's a camera error, in some cases the entire phone freezes for several seconds (with even the home button not responding). In rare cases the phone becomes sluggish until a reboot is forced. It seems to happen with bright scenes (e.g., outdoors in daytime, or pointing close to a bright light - say shutter speed 1/100s or less). There are a few ways to reproduce this:
1. Switch to manual shutter speed, then back to auto. Then point to a bright scene, after a few moments the problem usually happens.
2. Point at bright scene and switch to manual shutter speed, and wait a few moments.
3. Switch to manual shutter speed, and keep varying the shutter speed (even if not pointing to bright scene).
I've reproduced this with: Open Camera, A Better Camera, Snap Camera HDR, Camera FV-5, AZ Camera, Footej, Lightroom.
Unfortunately this doesn't just make manual mode unreliable, but also affects implementation of things like HDR, expo bracketing.
* The ISO value (and possibly shutter speed?) reported by the Camera driver is incorrect in dark scenes. This can be seen by the on-screen values in Open Camera, A Better Camera (see Settings/Viewfinder settings/More/ISO value), Snap Camera HDR, Camera FV-5, AZ Camera, Footej. In Open Camera, this value is CaptureResult.SENSOR_SENSITIVITY obtained from the CaptureRequest request received by onCaptureCompleted.
It can also be seen by looking at the reported ISO in the image's Exif data.
The maximum reported values are ISO 799 and shutter speed 1/16.7s. Why do I suspect this to be incorrect? Firstly because taking a photo of the same scene with the stock camera will show much higher ISO in the Exif (even though the photo looks similar), secondly because switching to manual ISO value of ~800 (either in the stock or a third party camera) results in a much darker photos.
Note, this bug is more serious than it might sound, as it messes up things like using HDR for darker scenes.
* Possibly related to this is that setting a manual ISO of above 800 seems to have no effect - photos are still taken as if they had ISO 800. This can be reproduced with Open Camera, A Better Camera, Snap Camera HDR.
Also, not a camera2 issue, but still relevant to the OnePlus 3T, is double-power-button to open camera: if the device is unlocked, it launches the default camera app, but if the device is locked, it only seems to open the stock OnePlus camera app. Open Camera sets an intent filter for both android.media.action.STILL_IMAGE_CAMERA and android.media.action.STILL_IMAGE_CAMERA_SECURE . This works okay on my Nexus 6. On my OnePlus, the app info for the stock camera app says "no defaults set", so there's nothing to clear.
Supposedly the preferred way to report bugs is https://forums.oneplus.net/feedback/ , but I can't create a new thread until I've posted 5 replies (ah yes, anti-spam measures that encourage users to spam) so I'll have to post here for now. I thought it'd be interesting to know if others have experienced or can reproduce these - or if you're experiencing different issues altogether? (Sometimes even on a single model, there can be frustrating camera bugs that only show on some devices for whatever reason.)
I like to play with manual mode, but just a casual shooter so haven't gone to details, but will give this try. I know there are some inaccuracy, but it's affirming coming from a pro. You can just comment 5 times and post in the oneplus forum. I will also test and post the feedback.
May be fixing these will result in impressive picture quality as hardware is capable just the processing which is average.
Thanks for the finding and posting, at least we know some of the reason now.
I've had problems with the manual shutter speed. Happens when reducing it. Picture starts scrolling then phone freezes up
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
mdwh said:
Hi,
I'm the developer of Open Camera ( http://opencamera.org.uk/ / https://forum.xda-developers.com/android/apps-games/app-camera-t2850557/ ) and was wondering what people's experiences were on the OnePlus 3T with third party camera apps that use Camera2 API?
I've tested a few different third party cameras on my OnePlus 3T, with Camera2 enabled as follows:
Open Camera: enable Settings/"Use Camera2 API".
A Better Camera: enable Settings/General settings/More/"Use Camera2 interface".
Snap Camera HDR (Trial): enable Settings/Other/"Use Camera2 API".
Camera FV-5: this uses Camera2 by default.
AZ Camera: this uses Camera2 by default.
Footej: this uses Camera2 by default.
Lightroom (which has a built-in camera using Camera2)
Mostly things seem good, but there are some issues on my device (these occurred on both Oxygen 4.0.2 and 4.0.3):
* Most seriously, I've seen problems to do with using manual shutter speed. This usually shows in the form of preview corruption (it shows a split-screen, or starts scrolling), but sometimes there's a camera error, in some cases the entire phone freezes for several seconds (with even the home button not responding). In rare cases the phone becomes sluggish until a reboot is forced. It seems to happen with bright scenes (e.g., outdoors in daytime, or pointing close to a bright light - say shutter speed 1/100s or less). There are a few ways to reproduce this:
1. Switch to manual shutter speed, then back to auto. Then point to a bright scene, after a few moments the problem usually happens.
2. Point at bright scene and switch to manual shutter speed, and wait a few moments.
3. Switch to manual shutter speed, and keep varying the shutter speed (even if not pointing to bright scene).
I've reproduced this with: Open Camera, A Better Camera, Snap Camera HDR, Camera FV-5, AZ Camera, Footej, Lightroom.
Unfortunately this doesn't just make manual mode unreliable, but also affects implementation of things like HDR, expo bracketing.
* The ISO value (and possibly shutter speed?) reported by the Camera driver is incorrect in dark scenes. This can be seen by the on-screen values in Open Camera, A Better Camera (see Settings/Viewfinder settings/More/ISO value), Snap Camera HDR, Camera FV-5, AZ Camera, Footej. In Open Camera, this value is CaptureResult.SENSOR_SENSITIVITY obtained from the CaptureRequest request received by onCaptureCompleted.
It can also be seen by looking at the reported ISO in the image's Exif data.
The maximum reported values are ISO 799 and shutter speed 1/16.7s. Why do I suspect this to be incorrect? Firstly because taking a photo of the same scene with the stock camera will show much higher ISO in the Exif (even though the photo looks similar), secondly because switching to manual ISO value of ~800 (either in the stock or a third party camera) results in a much darker photos.
Note, this bug is more serious than it might sound, as it messes up things like using HDR for darker scenes.
* Possibly related to this is that setting a manual ISO of above 800 seems to have no effect - photos are still taken as if they had ISO 800. This can be reproduced with Open Camera, A Better Camera, Snap Camera HDR.
Also, not a camera2 issue, but still relevant to the OnePlus 3T, is double-power-button to open camera: if the device is unlocked, it launches the default camera app, but if the device is locked, it only seems to open the stock OnePlus camera app. Open Camera sets an intent filter for both android.media.action.STILL_IMAGE_CAMERA and android.media.action.STILL_IMAGE_CAMERA_SECURE . This works okay on my Nexus 6. On my OnePlus, the app info for the stock camera app says "no defaults set", so there's nothing to clear.
Supposedly the preferred way to report bugs is https://forums.oneplus.net/feedback/ , but I can't create a new thread until I've posted 5 replies (ah yes, anti-spam measures that encourage users to spam) so I'll have to post here for now. I thought it'd be interesting to know if others have experienced or can reproduce these - or if you're experiencing different issues altogether? (Sometimes even on a single model, there can be frustrating camera bugs that only show on some devices for whatever reason.)
Click to expand...
Click to collapse
hey man first of all thank you very much for developing that app, its awwwwsssome and btw oneplus implemented camera2api in op3t poorly so that could be the reason ( if they were able to implement api2 correctly then there wouldve been 240 fps slow mo for op3t)
I was able to reproduce every issue you've said on my 3T - OOS 4.0.3 - mainly incorrect EXIF data when using camera app <> stock.
Open Camera works okay for me (as it crashes the least), but when trying CFV-5 or Manual Camera then I was also able to reproduce the freezing/hanging/glitched preview screen.
Also a thing I noticed, that my rear camera takes brighter pictures in low light than the back, even tough the shutter is longer on the rear (probably incorrectly reported) - more info here.
I was able to reproduce all of the issues you mentioned on an OOS 4.0.3 based custom ROM, which I guess is kinda the same as stock.
This is a serious issue, you should definitely report this to Oneplus, since all of us seem to be affected by it.
Another thing: Higher ISO and lower shutter speed combo works as intended in the stock camera app. I suspect foul play by Oneplus.
I've experienced the lock screen issue before but not used the camera enough to really notice the other problems yet. I actually have Open Camera installed. Nice work and I love the fact that you open sourced it and didn't plague us with more ads. That is very appreciated!
I really miss the camera app I used on the OnePlus One but its just not compatible (or that's the rumor) with newer models. Maybe Ill flash it.
Definately keep trying on the feedback link. I know the spam-to-post thing is stupid. Have you tried the User Feedback app? Or is that only on the Beta?
Sent from my ONEPLUS A3000 using Tapatalk
For what it's worth after I received my 3t I saw how slow the stock camera was and it's inability to stop motion very well and installed your app and it works quite well. I use your app as my default camera app.
kenhicg said:
For what it's worth after I received my 3t I saw how slow the stock camera was and it's inability to stop motion very well and installed your app and it works quite well. I use your app as my default camera app.
Click to expand...
Click to collapse
Seriously? You defenetly confused with camera apps.
Stock oos camera is wonderful. For exemple, now I'm using as my daily rom, dedicated and unnoficial laos by nvertigo67 for 3t. And I can say, that it is the best rom by far.
Just a moment ago, I'm installed and tested opencamera, and can say anything good (if comparing it with stock one). So please, just try something else and you will see how is amazing, fast, smooth the stock one. Btw, there you can find snapdragon camera(introduce by @nvertigo67 too), that have same perfomance and quality. I'm just prefer oos cam, becouse ui more comfortable.
@mdwh
Nothing personal. You making a good app (use it on my opo). Just whanted to say, that stock one is superb, with op bloobs. Even in laos build.
Getting green squares instead of front camera photos
Thanks for your responses, I've now posted on the OnePlus forums at https://forums.oneplus.net/threads/camera2-api-bugs-for-3rd-party-camera-apps.506100/ .
mdwh said:
Thanks for your responses, I've now posted on the OnePlus forums at https://forums.oneplus.net/threads/camera2-api-bugs-for-3rd-party-camera-apps.506100/ .
Click to expand...
Click to collapse
They responded quickly. Surprisingly quickly. I'm interested to see how fast they will react though...
lapapunk said:
Seriously? You defenetly confused with camera apps.
Stock oos camera is wonderful. For exemple, now I'm using as my daily rom, dedicated and unnoficial laos by nvertigo67 for 3t. And I can say, that it is the best rom by far.
Just a moment ago, I'm installed and tested opencamera, and can say anything good (if comparing it with stock one). So please, just try something else and you will see how is amazing, fast, smooth the stock one. Btw, there you can find snapdragon camera(introduce by @nvertigo67 too), that have same perfomance and quality. I'm just prefer oos cam, becouse ui more comfortable.
@mdwh
Nothing personal. You making a good app (use it on my opo). Just whanted to say, that stock one is superb, with op bloobs. Even in laos build.
Click to expand...
Click to collapse
Obviously you are confused
Sent from my ONEPLUS A3000 using Tapatalk
A month passed, new open beta, same thing is in it.
prathyand said:
I have talked to a ROM Enginieer from OP. He says that it is internally fixed but not released in OpenBetas. Will be released soon. Let's wait n see .
Click to expand...
Click to collapse
Source: https://forums.oneplus.net/threads/camera2-api-bugs-for-3rd-party-camera-apps.506100/#post-16131084
And I really want to have back the functions from Open Camera. It's the main camera since years now and I don't wanna miss it. Never.
Well, there's hope.
What should I say... I really tried my best to get their attention, but the administrative audience keeps being quiet. I really thought of getting an OP5, but at all points in summary, they really grew trust issues. Wasn't one point of their slogan, they hear what the users want? I really don't think so. Otherwise, this issue would have been fixed ages ago or at least a reply from someone who really works on fixing issues like that. That's a major bug and nobody cares. Sad.
I'm really fed up with this situation. I like to try lots of custom ROMs but I'm basically stuck with using stock OOS just for the camera. What can we do to make this happen? Phone calls? Lots of emails? I'm willing to make a lot of fuss to pressure these mofos into fixing this POS API thing.
@redsmith: Abandon OnePlus once and forever. I'm already looking for a new OEM. Currently, there are no developer-friendly phones out, so I have to wait a bit. I won't support this company any longer that claims "We hear what customers say!". They don't. They only look forward to get their newest devices sold by hype. They're not as tiny as they make us believe. They're close to OPPO (even in the same building). They could fix this problem if they want but sadly it seems, that they simply don't.
MickyFoley said:
What should I say... I really tried my best to get their attention, but the administrative audience keeps being quiet. I really thought of getting an OP5, but at all points in summary, they really grew trust issues. Wasn't one point of their slogan, they hear what the users want? I really don't think so. Otherwise, this issue would have been fixed ages ago or at least a reply from someone who really works on fixing issues like that. That's a major bug and nobody cares. Sad.
Click to expand...
Click to collapse
redsmith said:
I'm really fed up with this situation. I like to try lots of custom ROMs but I'm basically stuck with using stock OOS just for the camera. What can we do to make this happen? Phone calls? Lots of emails? I'm willing to make a lot of fuss to pressure these mofos into fixing this POS API thing.
Click to expand...
Click to collapse
MickyFoley said:
@redsmith: Abandon OnePlus once and forever. I'm already looking for a new OEM. Currently, there are no developer-friendly phones out, so I have to wait a bit. I won't support this company any longer that claims "We hear what customers say!". They don't. They only look forward to get their newest devices sold by hype. They're not as tiny as they make us believe. They're close to OPPO (even in the same building). They could fix this problem if they want but sadly it seems, that they simply don't.
Click to expand...
Click to collapse
@Funk Wizard
redsmith said:
I'm really fed up with this situation. I like to try lots of custom ROMs but I'm basically stuck with using stock OOS just for the camera. What can we do to make this happen? Phone calls? Lots of emails? I'm willing to make a lot of fuss to pressure these mofos into fixing this POS API thing.
Click to expand...
Click to collapse
No. Phoenix AEX has the OOS camera (not the port). It's exact. I've even used the new Camera2 for the OP5 on Phoenix. Try it. However, I'm using Sultan's SnapDragon Camera (works on LOS based ROMs and Phoenix since Phoenix auto-switches camera HALs), and it really beats any camera app I've tried in quality ... there are setting to tweak ... quality set to high, raised contrast a step or two up, sharpness a step up, saturation a step down, but ... its my new default.
Sent from my OnePlus3T using XDA Labs
So I was just casually using Google's HDR camera and I wanted to push this camera to its limits so I take a picture in very low light conditions (btw this is one of the best cameras around right now with the Google Camera because the Le Max 2 was mostly lacking with noise and clarity, which the Google Camera helps to fix, and the Le Max 2 has the 21mp for superior detail, a very nice combination. I have a XZ Premium and even that can't compare to the Le Max 2 pictures with the Google Camera at all).The results at first was an ISO of 7450, then I pushed it even further and found the limit was 9600 . This is surprising to find out when the stock max ISO is 1600, please don't take this information as facts although as I can only identify what ISO the camera is running at by the pictures data.
And if the Google Camera does take pictures with an ISO up to 9600, there might be potential to allow the max ISO to be integrated into different camera apps or even system wide with our lovely developers.
I think the only thing holding the Le Max 2's camera capabilities right now is the exposure time as it is limited to just half a second, if we could unlock this exposure time to be something like 32 seconds (this does seem possible as I have seen it on the redmi note 4, and that takes amazing pictures at night with 32 second exposure) this camera could be amazing. Instead of the high noise at night with low shutter speeds (ISO 9600) we could have a low ISO and high exposure time for crisp and natural low light shots! If you got this far thanks for reading, I really appreciate it and if there may be something that is wrong please correct me as I am not a developer, just a person who loves tech, thanks!
Here is one of the images, and I know the metadata states the picture is taken on a Pixel 2 XL, this is because I used build prop to get Google Lens.
https://photos.app.goo.gl/f5iOUOOsvr9OWVZw2
I have done some testing and I believe it works on the the Gcam 4.4 and 5.1 custom HDR+ apks, although I have found out that the ISO only goes up to 9600 in HDR mode, without it the ISO is just like stock (1600), this could imply that the Google's algorithm uses a high ISO.
I_Raptor_I said:
I have done some testing and I believe it works on the the Gcam 4.4 and 5.1 custom HDR+ apks, although I have found out that the ISO only goes up to 9600 in HDR mode, without it the ISO is just like stock (1600), this could imply that the Google's algorithm uses a high ISO.
Click to expand...
Click to collapse
How exactly do I get Google camera on my phone (le max 2) running eui 5.9.26s and rooted with magisk.
andrew0070 said:
How exactly do I get Google camera on my phone (le max 2) running eui 5.9.26s and rooted with magisk.
Click to expand...
Click to collapse
Unfortunately we can't, it only works for android 7 (nougat) versions and above as I understood.
That was few months ago maybe something changed, but I doubt it.
Hi I_Raptor_I,
which Rom are you using?
I am using Resurrection Remix on Android 7.1.2 l, but I think this should work on all recent nougat ROMs with camera API 2 enabled, and if you where wondering this is where I download the latest Google Camera HDR apks:
https://www.celsoazevedo.com/files/android/google-camera/
I am using Arnova's 5.1.018_v1.3 this is a step up from all of the other Google Cameras in terms of photography as the zoom is fixed and zooms in the centre rather than the left which is good, it does have the new portrait mode and motion pictures but they are still very buggy, but the HDR looks much more refined (better quality and low light performance with less iso but more exposure giving more clear images), there is a HDR function for the front but that does not work yet also video does not work, so if you haven't noticed this is a camera app dedicated to mostly HDR pictures. The good thing about this camera is that you can install a MGC camera apk and they don't conflict so you have got a Google camera for video and photography, overall this app is still buggy but contains alot more features and detail, hopefully when this app comes out with its next update the user experience will become much more refined.
I've come from a oneplus 6 to a note 9
The best thing about the Oneplus was the GCAM hack and the way nightmode and portrait would be processed by what app2to be Google photos (including things like colour pop portrait mode where the back ground colour is removed after the image is taken)
I have the current GCAM For the note 9 and undstand as of yet there's no night mode or portrait mode but my question is, is there anyway if making Google process the images if taken by the Samsung camera app, the processing was fabulous and personally I'm missing it
Thanks
gb155 said:
I've come from a oneplus 6 to a note 9
The best thing about the Oneplus was the GCAM hack and the way nightmode and portrait would be processed by what app2to be Google photos (including things like colour pop portrait mode where the back ground colour is removed after the image is taken)
I have the current GCAM For the note 9 and undstand as of yet there's no night mode or portrait mode but my question is, is there anyway if making Google process the images if taken by the Samsung camera app, the processing was fabulous and personally I'm missing it
Thanks
Click to expand...
Click to collapse
Not possible maybe for the snapdragon variant but the exynos is out of luck. If you are using the snapdragon variant you may search for a gcam hack snapdragon chip..
night mode working fine here using GCam_Pixel3Mod_1.3_build.6.1.021 and magisk pix3lify module.
ar stickers work too.
I'm on an exynos
btw nightmode is like opening a picture in photoshop and adjusting exposure, contrast, brightness etc... so you have to have some degree of light.
so it's just software playing around with the photo. basically any photo editor with a decent amount if options could do the exact same thing. dont know what all the fuss is about. it el be standard on all phones within a year.
A lot of it is software yes
But it also increases the shutter too and hence let's more light in so that it can be edited with less grain
Of course I could just use pro mode but gcam did it so well
bober10113 said:
night mode working fine here using GCam_Pixel3Mod_1.3_build.6.1.021 and magisk pix3lify module.
ar stickers work too.
I'm on an exynos
btw nightmode is like opening a picture in photoshop and adjusting exposure, contrast, brightness etc... so you have to have some degree of light.
so it's just software playing around with the photo. basically any photo editor with a decent amount if options could do the exact same thing. dont know what all the fuss is about. it el be standard on all phones within a year.
Click to expand...
Click to collapse