Forwarded from XiaomiTime Prototypes
I spent several days with vivo x70pro+ firmware searching for any signs of mythical V1 ISP they claimed on presentation... and couldn't find any. They seem to use lots of AI operations based on 888 chipset capabilities, especially the AIdenoise that seem to involve tensor operations as well as Qualcomm Hexagon DSP. The only function pointing towards "uncommon" method is the Geler-Shi dataset that might be used for some AWB operation that could involve that V1 custom chip. Too bad device has no root, nor bl unlock to dig any further.
IMX586 LIB MOD
for k20pro/mi9tpro ofilm lens
Ressurected custom bins project for my device. Now it comes in two variations - for sum & average binning modes, can choose those with volume keys during magisk flash, as well as read what is binning and what to expect from certain mode.
Module is UltraCVM v8.1 ready - both avg & sum noise models already in the camera mod (use the very top imx586 model for average binning & imx586 SUM for sum mode).
What's else in:
- external clocks OC'd
- ported imx598 clocks bandwidth
- cleaned up registers
Libs don't work with 48mp patch! Please don't bother with that.
for k20pro/mi9tpro ofilm lens
Ressurected custom bins project for my device. Now it comes in two variations - for sum & average binning modes, can choose those with volume keys during magisk flash, as well as read what is binning and what to expect from certain mode.
Module is UltraCVM v8.1 ready - both avg & sum noise models already in the camera mod (use the very top imx586 model for average binning & imx586 SUM for sum mode).
What's else in:
- external clocks OC'd
- ported imx598 clocks bandwidth
- cleaned up registers
Libs don't work with 48mp patch! Please don't bother with that.
No shit educated laziness is dragging normies into thinking that bringing trojan horse into own house is a great idea. With every major social app on the phone collecting all sorts of data, through ultrasound spyware analytics for current tv program, to a always on microphone - Big Brother is always watching pretending to be a friend ready to help, but never really explains how. I've heard many times "so what? I have nothing to hide as I don't do anything bad". But it's never about something cunning you might do - it's always about the general normie agenda that highlights certain social group, so that it can be offered more laziness.
https://www.mirror.co.uk/news/weird-news/woman-finds-amazon-thousands-recordings-25240984
https://www.mirror.co.uk/news/weird-news/woman-finds-amazon-thousands-recordings-25240984
👍1
Meanwhile 61 samsung devices are banned from being used in Russia 🤣
https://kad.arbitr.ru/Document/Pdf/12c0db2f-d4ed-4af5-8d64-46a890fbc9b3/8ecedc29-f7c8-44ca-a49c-bb375d2824fa/A40-29590-2020_20211019_Prochie_sudebnye_dokumenty.pdf?isAddStamp=True
https://kad.arbitr.ru/Document/Pdf/12c0db2f-d4ed-4af5-8d64-46a890fbc9b3/8ecedc29-f7c8-44ca-a49c-bb375d2824fa/A40-29590-2020_20211019_Prochie_sudebnye_dokumenty.pdf?isAddStamp=True
Alright, so here is a deal with Pixel 6/pro - there are 2 quad bayer sensors - main Gn1 & tele imx586, 50 & 48mp accordingly.
Now, google brings full res api for sdk31 so one might think "well they bring fullres for own devices, right?". As far as I can tell now - NO. As surprising as it is - there are no signs of them using this api in the upcoming google camera.
That would be fine - there is a chance of using opmode that would poke certain streamconfig, but... no streamconfig or scaler in the dumpsys having any signs of full res. Operation modes is what most oems use by this day and it's a problematic stuff as that results in proprietary implementation, so that giving a unified solution for everyone and not using yourself is quite idiotic.
Despite all that, they seem to be utilizing something like binning modes for both quad sensors. Sensor binning is the process of combining the electric charge from adjacent pixels into one super-pixel to reduce noise by increasing the signal-to-noise ratio. So theoretically it's possible they averaging or summing pixel charges there - it's a great control for various scenes/conditions.
It's too early for any concrete statements without getting more data, but it is what it is - a gcam mod having full resolution and a native gcam probably don't 🤡
Now, google brings full res api for sdk31 so one might think "well they bring fullres for own devices, right?". As far as I can tell now - NO. As surprising as it is - there are no signs of them using this api in the upcoming google camera.
That would be fine - there is a chance of using opmode that would poke certain streamconfig, but... no streamconfig or scaler in the dumpsys having any signs of full res. Operation modes is what most oems use by this day and it's a problematic stuff as that results in proprietary implementation, so that giving a unified solution for everyone and not using yourself is quite idiotic.
Despite all that, they seem to be utilizing something like binning modes for both quad sensors. Sensor binning is the process of combining the electric charge from adjacent pixels into one super-pixel to reduce noise by increasing the signal-to-noise ratio. So theoretically it's possible they averaging or summing pixel charges there - it's a great control for various scenes/conditions.
It's too early for any concrete statements without getting more data, but it is what it is - a gcam mod having full resolution and a native gcam probably don't 🤡
👍1