Horrible camera

vevs Post time 2015-7-29 23:27:17 | Show all posts  Close [Copy link]
65 18582
Author: vevs

Horrible camera

 Close [Copy link]

6

threads

67

posts

313

credits

Platinum Member

Rank: 3Rank: 3

credits
313
Post time 2015-7-29 06:13:51 From the mobile phone | Show all posts
Use camera ics from google play and tell me... I will upload diferences

3

threads

19

posts

101

credits

Senior Member

Rank: 2

credits
101
Post time 2015-7-29 08:18:25 | Show all posts
cloudvdr replied at 2015-7-29 06:13
Use camera ics from google play and tell me... I will upload diferences




Not so fine art!

2

threads

29

posts

110

credits

Senior Member

Rank: 2

credits
110
Post time 2015-7-29 08:55:02 | Show all posts
I think it's probably just software implementation or some other hardware in the middle, as the Oneplus One has the same camera sensor and doesn't get nearly as many complaints. I think the part that bugs most people is that the noise is sharp, as opposed to smoother noise in other cameras. I'd bank on that being something on the side of the image capturing/saving process. Not sure what level of control Umi has over that, and how much they can actually do to "fix" it.
I'm torn between "it's possible to fix, we just don't know the exact source of the issue" and "there are a few ways to optimize it, but otherwise we're trying to improve something that can't be improved." :/
It sounds like the Umi team has been trying to improve it but hasn't, so either the issue isn't pinpointed or they don't have enough low-level control to fix those issues.

3

threads

19

posts

101

credits

Senior Member

Rank: 2

credits
101
Post time 2015-7-29 09:02:04 | Show all posts
Clone_Tekboy replied at 2015-7-29 08:55
I think it's probably just software implementation or some other hardware in the middle, as the Onep ...

it's various /hal/imgsensor/config.ftbl pointing to nowere and missing denoiser (ISOXNUMBERX_resXres.ncf) along many unconfigured camera feature and perhaps unchecked current through the sensor - a sort of working dummy. Can be fixed tough, by the owner of the kernel or by someone with lot's of time in his hand!
I've already asked for refund, but you should ask to fix this seriusly, it's disappointing!

1

threads

30

posts

239

credits

Platinum Member

Rank: 3Rank: 3

credits
239
Post time 2015-7-29 12:14:25 | Show all posts
Tinkering with the EV calibration made my photos a bit less over exposed and a bit more saturated using stock camera with ISO on Auto, still noise in dark areas though. It's nearer to A better camera unlocked quality but not there yet.

57

threads

154

posts

4977

credits

Tourist

credits
4977

UMIDIGIerDie-Hard UMIDIGI Fans

Post time 2015-7-29 14:51:26 | Show all posts
i found and also use a solution for camera quality till next release lollipop update.
First you upgrade your ROM to Latest UMI eMax KitKat 4.4.4 V05 0715 and You see an improvement if you set the resolution to 13MP with 4:3 aspect ratio and decrease the ISO value 100 or 200 and also set Contrast Low.

12

threads

49

posts

240

credits

Platinum Member

Rank: 3Rank: 3

credits
240

UMIDIGIerDie-Hard UMIDIGI Fans

Post time 2015-7-29 15:54:35 | Show all posts
i've just compared other photos taken with same sensor and haven't noise as emax, i'm sure that working on rom can improve result.

3

threads

19

posts

101

credits

Senior Member

Rank: 2

credits
101
Post time 2015-7-29 19:19:15 | Show all posts
Edited by nananaRev at 2015-7-29 19:50 \n\n
Clone_Tekboy replied at 2015-7-29 08:55
I think it's probably just software implementation or some other hardware in the middle, as the Onep ...

OnePlus is a little washed as quality, altho, you can't really put it up with the current camera shoot of the EMAX.
Check out this photo ( https://www.flickr.com/photos/124215533@N08/ )



and compare it with the following



I can't!
--
Also, as I already wrote.. the SENSOR_DRVNAME reported by the CustInfo (MtkCam - SensorInfo) is OV8858 and GC2755 - dunno if these are in fact the real sensor of the EMAX.
The OnePlus uses the IMX214 and OV5648. Different specs, different hardware, different software.

1

threads

30

posts

239

credits

Platinum Member

Rank: 3Rank: 3

credits
239
Post time 2015-7-29 20:03:17 | Show all posts
Not really that big, but FV-5 camera states it's f/2.0 and not f/2.2

2

threads

29

posts

110

credits

Senior Member

Rank: 2

credits
110
Post time 2015-7-29 23:27:17 | Show all posts
Edited by Clone_Tekboy at 2015-7-30 00:13 \n\n Edited by Clone_Tekboy at 2015-7-30 00:05 \n\nHehe, if the sensor is actually the OV8858 we're just screwed. That just means we're asking them for better upscaling from 8mp to 13mp. I'd love to confirm, but I have no idea how i would other than a teardown.
If it is actually that sensor, I'd rather Umi kill the upscaling and max it out at 8mp so we get decent photos with the hardware we actually have.

EDIT: This same info was on the Umi Hammer, so it could be the case... Or they just use that info for all their phones? An Umi Iron teardown revealed a camera labled with "ZB504A", and it's supposed to be the IMX214. Judging by pictures around the web, the camera is shaped like the IMX214, so that could be correct. Anyone know how to check that number? Also, umi listed the OV8858 as the front facing camera on the iron THAT IS A FLAT OUT LIE!!! look at S7yler's teardown, the front camera definately looks NOTHING like the OV8858.

I found this pic online, and it looks like the emax back camera sensor isn't the OV8858, and looks marginally closer to the IMX214. (Of course, I'd need a closer pic to be certain. It's hard to tell.)


There's no Umi Hammer teardowns out there, so ho hope with cross-checking that one.
1234567Next
You have to log in before you can reply Login | WELCOME TO UMIDIGI COMMUNITY

Points Rules

Quick Reply Top Back to list