Which sensor is the Axon using? All we know so far is a 20MP ISOCELL sensor, but not even a part number. Easiest way to find out would be for someone with the device to download AIDA64 and go to the Devices screen. To anyone who does, thanks in advance!
Camera part?
- Thread starter AB__CD
- Start date
I'm not seeing anything. Is there something else I can try?
Attachments
Had to do it manually in app settings. ????
Attachments
Whoops doesnt seem like it's recognized by S/W yet. Thanks for your effort though.
@peramikic posted on the ZTE forum (referenced in the last post at the bottom of this page) that the kernel source identifies the sensor as S5K2T8. Samsung doesn't list that on their site as a mass-produced sensor for purchase, but Truly Semiconductors does.
I posted the same on the ZTE forums, but the best guess is that's a 20MP variant of the S5K2P8, which is a 1/2.6" ISOCELL sensor with 16MP. Wikipedia lists the P8 as the only (mainstream) Samsung sensor never used in a Samsung phone. It is, however, found in the Lenovo Vibe Z2 Pro. Take Wikipedia as a source as you will, but the Z2 Pro forum on XDA mentions the P8 sensor.
I was under the impression that Samsung doesn't sell the sensors it makes for its own use to other companies, though I could be wrong. If that's the case, though, it would make sense that they crammed 20MP on what was previously a 16MP sensor and sold it to ZTE, allowing ZTE to claim that the Axon 7 uses a Samsung sensor was made specifically for ZTE.
The question is why Samsung never used the P8. They produce the S5K2P2, which is nearly identical and found in the S5, S6, and Note 5.
I posted the same on the ZTE forums, but the best guess is that's a 20MP variant of the S5K2P8, which is a 1/2.6" ISOCELL sensor with 16MP. Wikipedia lists the P8 as the only (mainstream) Samsung sensor never used in a Samsung phone. It is, however, found in the Lenovo Vibe Z2 Pro. Take Wikipedia as a source as you will, but the Z2 Pro forum on XDA mentions the P8 sensor.
I was under the impression that Samsung doesn't sell the sensors it makes for its own use to other companies, though I could be wrong. If that's the case, though, it would make sense that they crammed 20MP on what was previously a 16MP sensor and sold it to ZTE, allowing ZTE to claim that the Axon 7 uses a Samsung sensor was made specifically for ZTE.
The question is why Samsung never used the P8. They produce the S5K2P2, which is nearly identical and found in the S5, S6, and Note 5.
Last edited:
It makes sense that it's a 16MP sensor "expanded" to 20MP.
A few days ago I noticed something weird: using the devcheck app, I remember dividing the sensor size by the number of pixels would give me 1.1um in one direction and 1.45um in the other. I guess we would get a square pixel size if the did the calculation with a 4/3 ratio rather than a 16/9 ratio
A few days ago I noticed something weird: using the devcheck app, I remember dividing the sensor size by the number of pixels would give me 1.1um in one direction and 1.45um in the other. I guess we would get a square pixel size if the did the calculation with a 4/3 ratio rather than a 16/9 ratio
I believe the rumor is they were testing it for the S7 and then dropped in favor for whatever they ended up using in that line. It would make sense that they would have a bunch ready to get rid of for cheap, or just to recoup any R&D by selling it to someone who still wanted it.
Any number of reasons, though none I can think of seem good enough not to say, exactly, what the module is. Maybe some caveat with being able to say "custom-made by Samsung for ZTE"?
I know that was a popular theory early on and it may very well be true. AFAIK, they don't have any other sensors with the "T" notation, so it could be the BRITECELL. IIRC, Samsung did say that it was a 20MP sensor with 1.0µm pixels and utilizing phase detection.
And it's entirely possible that Samsung abandoned the idea (RWB) for the same reason Motorola abandoned "Clear Pixel" (RGBC) and Sony abandoned RGBW: image quality issues. Or maybe they want to see what ZTE does with it. Who knows.
So some more tidbits from the kernel, here are all the possible mfgs for the sensor module apparently, with their ID codes
#define S5K2T8_SENSOR_INFO_MODULE_ID_SUNNY 0x01
#define S5K2T8_SENSOR_INFO_MODULE_ID_TRULY 0x02
#define S5K2T8_SENSOR_INFO_MODULE_ID_A_KERR 0x03
#define S5K2T8_SENSOR_INFO_MODULE_ID_LITEARRAY 0x04
#define S5K2T8_SENSOR_INFO_MODULE_ID_DARLING 0x05
#define S5K2T8_SENSOR_INFO_MODULE_ID_QTECH 0x06
#define S5K2T8_SENSOR_INFO_MODULE_ID_OFLIM 0x07
#define S5K2T8_SENSOR_INFO_MODULE_ID_FOXCONN 0x11
#define S5K2T8_SENSOR_INFO_MODULE_ID_IMPORTEK 0x12
#define S5K2T8_SENSOR_INFO_MODULE_ID_ALTEK 0x13
#define S5K2T8_SENSOR_INFO_MODULE_ID_ABICO 0x14
#define S5K2T8_SENSOR_INFO_MODULE_ID_LITE_ON 0x15
#define S5K2T8_SENSOR_INFO_MODULE_ID_SEMCO 0xA1
MODULE_Map_Table S5K2T8_MODULE_MAP[] = {
{ S5K2T8_SENSOR_INFO_MODULE_ID_SUNNY, "sunny_s5k2t8","sunny_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_TRULY, "truly_s5k2t8","truly_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_A_KERR, "a_kerr_s5k2t8","a_kerr_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_LITEARRAY, "litearray_s5k2t8","litearray_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_DARLING, "darling_s5k2t8","darling_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_QTECH, "qtech_s5k2t8","qtech_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_OFLIM, "oflim_s5k2t8","oflim_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_FOXCONN, "foxconn_s5k2t8","foxconn_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_IMPORTEK, "importek_s5k2t8","importek_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_ALTEK, "altek_s5k2t8","altek_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_ABICO, "abico_s5k2t8","abico_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_LITE_ON, "lite_on_s5k2t8","lite_on_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_SEMCO, "semco_s5k2t8","semco_s5k2t8",NULL},
};
---------- Post added at 06:19 PM ---------- Previous post was at 06:04 PM ----------
What is the sensor size reported by dev check?
#define S5K2T8_SENSOR_INFO_MODULE_ID_SUNNY 0x01
#define S5K2T8_SENSOR_INFO_MODULE_ID_TRULY 0x02
#define S5K2T8_SENSOR_INFO_MODULE_ID_A_KERR 0x03
#define S5K2T8_SENSOR_INFO_MODULE_ID_LITEARRAY 0x04
#define S5K2T8_SENSOR_INFO_MODULE_ID_DARLING 0x05
#define S5K2T8_SENSOR_INFO_MODULE_ID_QTECH 0x06
#define S5K2T8_SENSOR_INFO_MODULE_ID_OFLIM 0x07
#define S5K2T8_SENSOR_INFO_MODULE_ID_FOXCONN 0x11
#define S5K2T8_SENSOR_INFO_MODULE_ID_IMPORTEK 0x12
#define S5K2T8_SENSOR_INFO_MODULE_ID_ALTEK 0x13
#define S5K2T8_SENSOR_INFO_MODULE_ID_ABICO 0x14
#define S5K2T8_SENSOR_INFO_MODULE_ID_LITE_ON 0x15
#define S5K2T8_SENSOR_INFO_MODULE_ID_SEMCO 0xA1
MODULE_Map_Table S5K2T8_MODULE_MAP[] = {
{ S5K2T8_SENSOR_INFO_MODULE_ID_SUNNY, "sunny_s5k2t8","sunny_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_TRULY, "truly_s5k2t8","truly_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_A_KERR, "a_kerr_s5k2t8","a_kerr_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_LITEARRAY, "litearray_s5k2t8","litearray_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_DARLING, "darling_s5k2t8","darling_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_QTECH, "qtech_s5k2t8","qtech_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_OFLIM, "oflim_s5k2t8","oflim_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_FOXCONN, "foxconn_s5k2t8","foxconn_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_IMPORTEK, "importek_s5k2t8","importek_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_ALTEK, "altek_s5k2t8","altek_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_ABICO, "abico_s5k2t8","abico_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_LITE_ON, "lite_on_s5k2t8","lite_on_s5k2t8",NULL},
{ S5K2T8_SENSOR_INFO_MODULE_ID_SEMCO, "semco_s5k2t8","semco_s5k2t8",NULL},
};
---------- Post added at 06:19 PM ---------- Previous post was at 06:04 PM ----------
What is the sensor size reported by dev check?
Welp, there's Truly!
This is new territory for me; I didn't realize the kernel was written like that (identifying multiple manufacturers). Why is that done? Do they use different...drivers?
And so, just out of curiosity, if ZTE were to change the camera module in the future, I assume it would just be an added line (or lines) with that module information? Don't get me wrong, I'm not suggesting they will or that it's even that simple, but from an identification standpoint, is that all that's necessary?
The sensor seems to be a 4:3 but the native 20MP res is 16:9. That means there is 30% of the sensor that is not used and this is actually a 30+MP sensor. The pixel pitch is 1.08 on width, but isocell has that pixel issolation so the pixel width is most likely 1um. that would make the sensor 31.5MP in full res... if pixels are square
---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------
EEPROM mapping and to allow for different lens correction profiles and such. Each manufacturer would have a calibration correction so they can all be standardized in QA. Now truly having a camera module that is f2 but 6 element lens kinda makes sense, they probably could not fit an extra element without a larger bump to keep the f1.8
That's...weird.The sensor seems to be a 4:3 but the native 20MP res is 16:9. That means there is 30% of the sensor that is not used and this is actually a 30+MP sensor. The pixel pitch is 1.08 on width, but isocell has that pixel issolation so the pixel width is most likely 1um. that would make the sensor 31.5MP in full res... if pixels are square
Top Liked Posts
-
There are no posts matching your filters.
-
2
Any number of reasons, though none I can think of seem good enough not to say, exactly, what the module is. Maybe some caveat with being able to say "custom-made by Samsung for ZTE"?
I know that was a popular theory early on and it may very well be true. AFAIK, they don't have any other sensors with the "T" notation, so it could be the BRITECELL. IIRC, Samsung did say that it was a 20MP sensor with 1.0µm pixels and utilizing phase detection.
And it's entirely possible that Samsung abandoned the idea (RWB) for the same reason Motorola abandoned "Clear Pixel" (RGBC) and Sony abandoned RGBW: image quality issues. Or maybe they want to see what ZTE does with it. Who knows.1@peramikic posted on the ZTE forum (referenced in the last post at the bottom of this page) that the kernel source identifies the sensor as S5K2T8. Samsung doesn't list that on their site as a mass-produced sensor for purchase, but Truly Semiconductors does.
I posted the same on the ZTE forums, but the best guess is that's a 20MP variant of the S5K2P8, which is a 1/2.6" ISOCELL sensor with 16MP. Wikipedia lists the P8 as the only (mainstream) Samsung sensor never used in a Samsung phone. It is, however, found in the Lenovo Vibe Z2 Pro. Take Wikipedia as a source as you will, but the Z2 Pro forum on XDA mentions the P8 sensor.
I was under the impression that Samsung doesn't sell the sensors it makes for its own use to other companies, though I could be wrong. If that's the case, though, it would make sense that they crammed 20MP on what was previously a 16MP sensor and sold it to ZTE, allowing ZTE to claim that the Axon 7 uses a Samsung sensor was made specifically for ZTE.
The question is why Samsung never used the P8. They produce the S5K2P2, which is nearly identical and found in the S5, S6, and Note 5.1
