I'm not trying to sound stupid but is there not a way to "up" the camera on the Atrix to an 8MP or so? The reason I even asked is that I am just joining you "elite" group of Atrix owners by stepping up from an XT711. Now before I get too flamed, the XT is really a great handset, or could have been if it hadn't been abandoned by Motorola. I have an XT711 with a xenon flash and 8mp camera that takes OUTSTANDING photos and beautiful HD video, I also bought my wife its little brother, the XT701 that has a 5mp camera. After doing alot of searching, I found a Chinese web site that had a flash file that I used to flash her phone and change her camera to 8mp also, and it worked beautifully! Her camera went from good pictures to great pictures and it was just a simple flash file. Now that my wife and I are both upgrading to the Atrix because of no future support, I am just wondering if this method could be used for the Atrix as well or if anyone has thought about or tried it. I dont know how they changed it in the file, and if I wasn't such a rookie, I would look in it and see cause I still have the zip file, but I wouldn't even know what I was looking at if I opened it. I am sure the camera should be similar to the "X" phone with its 8mp, and from the looks of it, it might actually be the same camera as the newly China released XT882, which is almost the same as the Atrix (actually maybe better with its dual sims) but its camera is sitting at 8mp, not 5mp. Well since I am just a noob, I figured I would at least ask if it had been thought of or tried because I know from my XT phones that those 3 little megapixels can make a very nice difference in your pictures and alot of people including myself would love to have it. Why couldn't it work if the camera was capable? Just curious and hopeful. Thanks in advance!
I can tell you that the difference between 5MP and 8MP is not important, especially on a camera phone that is not designed to print large resolution images in the first place.
You can't increase the megapixels by flashing software onto a phone. Most likely the update adjusted the white balance, aperture, focus, and color contrasts to make the image more appealing. The iPhone has already proven that a lower MP camera can easily beat-out a higher MP if the software and lens is good enough.
I don't know of any current projects related to the Atrix 4G camera software. However, there many camera apps that offer filters and other software related changes to your photos. I suggest checking all of the modes the Atrix 4G offers and then see if any of the 3rd party apps add additional features.
Are you sure that the software cannot be limiting the camera to 5mp? I only ask because I don't know, not because I don't believe. I just read the site where the XT701 upgrade is and it says the software is limiting the camera. I just thought possibly the Atrix could be as well. Here is the translated page:
http://translate.google.com/transla...0/08/08/update_xt701_carema_to_8mpix/&act=url
Well it was at least worth asking. Hopefully with the new GB update coming up, the camera will become more like what I am used to. Thanks!
Since I haven't seen much discussion about the topic here on XDA, I'm particularly curious if anyone else is waiting/looking forward to additional camera features (Manual shutter, RAW, just to name a few) to make its way to our devices. There have been rumors about camera updates in future firmware releases and I'd like to hear what other users are looking forward to in terms of camera features/improvements.
Having an interest in photography (particularly night scenes), I for one was hoping I'd have manual shutter control when I purchased my Edge but it seems that this is not present (yet). Hardware-wise, I don't know how this would turn out... Is the camera even capable?
Considering that the G4 is also upping its camera game and many of the G4 articles published are about its camera, I wonder what kind of things Samsung would bring in to "fight back(?)" and how long it would take them, since the S6 camera is also one of Samsung's selling points for this flagship.
By order of preference, I would be interested in :
1. RAW support
2. ISO 40 in manual ISO mode (currently the lowest manual ISO value available is ISO 100, while the device goes down to ISO 40 in automatic ISO mode)
3. Manual shutter
Info
RAW capturing is the most wanted feature
Come to think of it, shooting in RAW would be pretty sweet. If this came in future updates, I might actually consider leaving my camera at home when going on quick trips.
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.
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