Database Develop

[MOD]Camera NX V7.4, Google Camera with Pixel features for Nexus2015

Hello N6P users, I succeed in getting the ZSL HDR+ works on Nexus 5X, as Nexus 6P has the same camera hardware and better SoC, I'd like to ask someone test my mod, to see if the function works.
What's ZSL HDR+?
ZSL = zero shooting lag, means you won't get camera freeze after taking a HDR+ auto shoot. it is build-in the Google Camera 4.2 and only works on Pixel phones, now I force the app using Pixel configuration, it should perform the same ZSL HDR+ shooting on Nexus 6P.
Details about the ZSL HDR+.
ZSL-enhanced For 8.0+ only, ZSL HDR+ For 7.1.1+ only, Android 7.0 users please use NoZSL version.
APK was signed by ZipSign using my own signature, it won't replace your default camera app, it will install as a normal app, with a different camera icon.
Last Update
03/24/2018 V7.4
Base on Google Camera 5.2
1. Bring back HDR+ on Nexus 5X/6P.
2. Add Lens Blur mode.
3. EIS should be back to normal on Pixel 1, as EIS will be disabled with 4K quality with official version.
4. Active Google photos combination to view results again on enhanced version.
Details and download link for V7.4
01/02/2018 V7.3.1
Bug fix version
1. Fix abort HDR+ process FC problem.
2. Fix viewfinder flickering issue.
3. Add ZSL version for Android 7.1+, the previous one should be ZSL-enhanced version.
Bugs:
1. smart-burst always mark the first photo (ZSL-enhanced version).
2. Autofocus won't work after manually focus, need lock then unlock the AF/AE lock.
12/31/2017 V7.3
Current the new version is only for Android 8.0+, will release the updated version for Android 7.0.
1. Add the most wanted feature, Portrait mode (use Pixel 2's front lens software method, it needs a human face shows up to work.).
2. Remove silence feedback service, crash report service, and the broken Help menu, for faster app launch.
3. Remove Google photos combination, motion photo still works but you need to view it through Google photos manually.
I have named it wrong and this one should be the ZSL-enhanced version, sorry for the wrong package errors on Android 7.1.2
Details and download link for V7.3.1
11/06/2017 V7.2.0
This is bug fix version, not only for Pixel 2016, everyone who is using enhanced version should grab this update.
1. Fix crash issue on Pixel 2016.
2. Fix provider author name mistake leads to a thumbnail generation issue.
3. Motion pictures should be saved with a file name "MVIMG-####-##" right now, it became "IMG-####-##" in V7.1 version, which was wrong, this might mess the G photos when index media files.
Enhanced version users should get the experimental2017 library now.
Sorry, after some more test it seems experimental2017 is not necessary, just install the new version it will be ok.
About the Lens photo editor, it will be available after the picture upload to Google cloud.
10/19/2017 V7.1.0
1. Based on the last Google Camera 5.1.014, add Pixel 2016 phones support (need test).
2. Video 60FPS mode with EIS FC bug Fixed.
3. Motion photos for Pixel 2016 phones.
4. Micro video (Motion photos) EIS use gyro sensor enabled for Pixel (it was only activated on Pixel XL), need feedback.
5. Update icon support adapted icon and regular icon.
6. Disable Motion photos and G-photo integration for Android 7.1.
-- Now there is a new ZSL-enhanced version for Motion photos, G-photos combine, diet smart-burst on Android 8.x.
-- NOZSL and ZSL version will perform the old way while added new face retouching.
-- Bugs: after shooting photos, review it and you will see a black screen, need to wait for HDR+ process, I don't know it is normal or just hardware limited.
Details and download link for V7.2 / V7.1 (All version)
Useful links
Custom Rom Black Screen Issue Fix:
Please use the http://opengapps.org/ Open Gapps "Stock" Option or above. Or you can find the fix in N5X thread(See below).
* 60FPS video recording succeed with @defcomg 's mod.
Unlock 60FPS with this mod: https://forum.xda-developers.com/showpost.php?p=70748865&postcount=161
More Details of this mod, please go to the Nexus 5X thread
http://forum.xda-developers.com/nexus-5x/themes-apps/mod-google-camera-4-2-nexus-5x-android-t3477980
Donation support
If you like my work, feel free to buy me a coffee, https://www.paypal.me/chromloop . :highfive:
Donation list::highfive:
Jeffrey Dubinsky
Jorge Ciprian
Peter P Pizzimenti

So we're SOL if we are on 7.1?

cc101 said:
So we're SOL if we are on 7.1?
Click to expand...
Click to collapse
uuhhh (For 7.1.1 only, ZSL broken on 7.0)

opz187 said:
uuhhh (For 7.1.1 only, ZSL broken on 7.0)
Click to expand...
Click to collapse
Uuhhh, big difference between 7.0 and 7.1

Argh already using v3.1 but can't test v4 cos I'm under 7.0 ...

Works great. The zero lag is true for sure. Not a big camera user but it seems to do what is advertised.
I'm on the developers preview
Sent from my Pixel XL using Tapatalk

I am using it too. Awesome stuff. Thank you. Using it on 7.1.1.
Sent from my Pixel XL using XDA-Developers mobile app

Get black screen only on nitrogen rom. But have custom kernel installed

Works great on 7.1.1 even with ElementalX 3.08!! There is some lag when its moving around, the regular camera doesnt have this, but its probably what makes the ZSL possible! There is still some lag with HDR+ on, but none with HDR Auto

btw this is working mint dude. good job. plan to keep it updated? id def choose this over the stock dp'7.1 camera

inthedark22 said:
Get black screen only on nitrogen rom. But have custom kernel installed
Click to expand...
Click to collapse
He said loud and clear this is for dev preview 7.1.1, there is an older version for 7.0, and nitrogen falls in neither of those, because its 7.1.0 !!!
And @op great job, this is fantastic. Now if only 1080p 60fps worked, it would be a dream

inthedark22 said:
Get black screen only on nitrogen rom. But have custom kernel installed
Click to expand...
Click to collapse
probably because that's AOSP based. working on stock 7.1.1

7.1 7.1.1 7.1.0 ? too bad

Works great thanks
Sent from my Pixel XL using Tapatalk

Great work. Camera is really quick.

inthedark22 said:
Get black screen only on nitrogen rom. But have custom kernel installed
Click to expand...
Click to collapse
Can you try using ex kernel to see if it works? I think its the kernel thing, when we have the 7.1 kernel source we might get it work on 7.0.

vladniko said:
Works great on 7.1.1 even with ElementalX 3.08!! There is some lag when its moving around, the regular camera doesnt have this, but its probably what makes the ZSL possible! There is still some lag with HDR+ on, but none with HDR Auto
Click to expand...
Click to collapse
Did the lag happen when using the stock camera?
Good to see custom 7.0 kernel on 7.1.1 did not break the camera, I would like to see some one on 7.0 using ex 3.08 kernel can get camera usable.

Charles_l said:
Did the lag happen when using the stock camera?
Good to see custom 7.0 kernel on 7.1.1 did not break the camera, I would like to see some one on 7.0 using ex 3.08 kernel can get camera usable.
Click to expand...
Click to collapse
By lag I meant shutter lag with hdr+ on. With hdr auto, it works like a charm with zero shutter lag. This is all in the NZ Camera

vladniko said:
By lag I meant shutter lag with hdr+ on. With hdr auto, it works like a charm with zero shutter lag. This is all in the NZ Camera
Click to expand...
Click to collapse
Ah I see. I would like to ask if the zsl also works if you turn off the HDR+ ? As no zsl switch inside the app for N6P, only one for N5X and it is disabled by default...
I force it enable for N5X, but for N6P I dont know if it is enabled or not.
I suppose it is enabled as the bursts mode needs it.

Charles_l said:
Ah I see. I would like to ask if the zsl also works if you turn off the HDR+ ? As no zsl switch inside the app for N6P, only one for N5X and it is disabled by default...
I force it enable for N5X, but for N6P I dont know if it is enabled or not.
I suppose it is enabled as the bursts mode needs it.
Click to expand...
Click to collapse
Yea with hdr off there is Zero shutter lag

Modded Google Cam on Mix 2

Created this thread to share working settings for our Mix 2 + IMX 386 on the latest Modded Google Cam. Feel free to share your working setups for Google Cam
Version Google Cam V4.0
ROM: Xiaomi.eu 9.22
Settings: See picture attachments below
What doesnt work:
HDR+ with Flash On
Autofocus
Tap to focus
Manual Focus Fix:
Swipe left to go into video mode and tap to focus before going back into picture mode

It have the same main camera sensor as Mi 6 which also do not have autofocus and touch to focus to work.

It's quite annoying when it doesn't have HDR+ and autofocus together, hope it can be fixed in future version
Sent from my MIX 2 using Tapatalk

jaco168 said:
It's quite annoying when it doesn't have HDR+ and autofocus together, hope it can be fixed in future version
Sent from my MIX 2 using Tapatalk
Click to expand...
Click to collapse
You can manual focus using this workaround: Swipe left to go into video mode and tap to focus before going back into picture mode

Does the new version of Google GCam mod support Autofocus yet?

Has anyone tried the Google Camera v5.1 yet?
Link: https://www.androidcentral.com/pixe...motion-photos-and-other-features-working-some

I tried to install google camera,installed successfully,but stop working. keep give me error. so I can not run it.

If you want to test the latest versions for Modded Google Cam, check the MIi6 thread related to this, there are regular updates as soon as they are released by the original modders:
https://forum.xda-developers.com/mi-6/themes/google-camera-hdr-t3655762

What I found out: The Oneplus Camera also works on Mi Mix 2.
Also I think this is the original thread for the modded Google Camera: https://forum.xda-developers.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552/ and it works for the Mi Mix 2 too.

kurtextrem said:
What I found out: The Oneplus Camera also works on Mi Mix 2.
Also I think this is the original thread for the modded Google Camera: https://forum.xda-developers.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552/ and it works for the Mi Mix 2 too.
Click to expand...
Click to collapse
Does not work for me. Are you on miui or custom rom? Which version of gcam worked for you?

MIUI EU ROM and Magisk + Camera2 API Enabler Magisk Module

how is the mix2 with this, any samples? im considering this because ive had enough of the s8 and want pure android with the performance to boot, where as the s8 just doesn't cut it but the camera is amazing

Autofocus doesnt work with HDR/HDR+ enabled. The camera works fine with auto focus without HDR features. I HDR+ is the reason why you want this mod then we are out of luck, its no better than the default MIUI cam.. may be a tad better NR processing on low light images.

subashchandran said:
Autofocus doesnt work with HDR/HDR+ enabled. The camera works fine with auto focus without HDR features. I HDR+ is the reason why you want this mod then we are out of luck, its no better than the default MIUI cam.. may be a tad better NR processing on low light images.
Click to expand...
Click to collapse
Try this:
loooller said:
You can manual focus using this workaround: Swipe left to go into video mode and tap to focus before going back into picture mode
Click to expand...
Click to collapse

Are you sure auto focus works for the default cam app when having HDR enabled? It doesn't at least for me. Thus I see no difference between GCam mod, Oneplus camera and default camera. Also, manually focusing seems to work without the left swipe.

kurtextrem said:
Are you sure auto focus works for the default cam app when having HDR enabled? It doesn't at least for me. Thus I see no difference between GCam mod, Oneplus camera and default camera. Also, manually focusing seems to work without the left swipe.
Click to expand...
Click to collapse
So, I am writing this based on my experience on my Mi6 (Mi Mix 2 still has a locked bootloader for now), when you activate the HDR+ the autofocus will die, at that point you focus in Video mode, go back to Photo and take the picture.
In that way the HDR+ is working properly and as expected. You just need to keep your hands steady.
Also, on Mi6 has been reported that the Autofocus is working now with the latest version (with some bugs and messing around with the OmniVision module):
Kisakuku said:
B-S-G's Modded Google Camera 5.1.016 with HDR+ for Android 7.0 / ARM64 v1.1 All-in-One Full Manual
Download
Changelog:
Added more camera configs
Fixed circular auto-focus indicator
Fixed auto-focus debug info display
Turn on camera.af.debug.show in developer settings
New settings take effect after application is restarted
Must clear data / cache after installation and if the app force closes
Click to expand...
Click to collapse

Lexmazter said:
So, I am writing this based on my experience on my Mi6 (Mi Mix 2 still has a locked bootloader for now), when you activate the HDR+ the autofocus will die, at that point you focus in Video mode, go back to Photo and take the picture.
In that way the HDR+ is working properly and as expected. You just need to keep your hands steady.
Also, on Mi6 has been reported that the Autofocus is working now with the latest version (with some bugs and messing around with the OmniVision module):
Click to expand...
Click to collapse
My Autofocus works with HDR+ on, I got the APK from the mi 6 thread (b-s-g camera).
https://forum.xda-developers.com/showpost.php?p=74513338&postcount=184

Any improvement in low light? What about portrait mode with the mix2? Is it working?

any sample images?

gb155 said:
any sample images?
Click to expand...
Click to collapse
Check the samples from Mi 6 thread below:
tupacsoul said:
Ok, I've been testing the kenzo build, but same error, autofocus stop working with HDR+ on.
By the way, I think anyone must work on this for our device... the differences betweet photos taken with MIUI camera and Google Camera are very big...
This is with Google Camera on HDR+
This is with MIUI Camera on HDR
This is with Google Camera on HDR+
This is with MIUI Camera on HDR
(Click on the image to see bigger the detail)
As can be seen, the HDR+ post processing is very much better than MIUI original.
Click to expand...
Click to collapse

Motorised front camera rom compatibility?

Does anyone have any idea on wether it can work on aosp roms or not? The guys over at the OP7Pro forums can't get it to work. It would be great if the camera mechanism on the K20 Pro engages when the camera module itself is enganged.

for k20pro, in current lineage gsi you can maually control front camera motor via command in terminal simulater. and now phhuson's gsi seems work well with op7pro's camera motor - see at his github issue.

mi a2 gcam front camera only 5mp ?

Is there anyway to use the full 20mp in front facing camera.. All gcam takes default 5mp by pixel binding.. also flash didn't work like stock... It acts like a torch while capturing photo

androshanki said:
Is there anyway to use the full 20mp in front facing camera.. All gcam takes default 5mp by pixel binding.. also flash didn't work like stock... It acts like a torch while capturing photo
Click to expand...
Click to collapse
i am using miui 12 pie and both stock and gcam are working at the same time .....
both have their advantages....
1. gcam uses pixel binning ( combining ) them
_so your camera is not really using 5mpx ..it is using max pixels merged into a 5mpx output_
_this might give you a good or better looking photo than some 20mpx sensors on some phones
_people use gcam because of Google's theoretical excellence in processing photos *** therefore better photos than stock ... because if you feel.stock has better photos than there is no argument for using gcam
2. gcam mods which allow you to choose to manually force the gcam to use the secondary ( aux ) exist ...you can use it in combo with magisk modules
_dont expect a giant leap in photo quality since our aux sensor is for low light ...and was never meant not even by Xiaomi to act as the main shooter
_stock camera changing between sensors automatically while in gcam.you will. have to.do.it manually _
_VERY IMPORTANTLy ...our aux sensor is NOT api2 compliant only our main sensor ...as per Xiaomi ...so Xiaomi needs to fix that if it can be fixed....that is why our phone isn't released with api2 enabled..
Options:
1. Use magisk module in stock rom to get stock camera
2. Use stock rom to use miui 12 pie to get both stock and gcam working at the same time
3. Use gcam with aux sensor select button in settings to activate it manually in custom rom
4. buy a jasmine or wayne device and donate it to gcam.modder or dev stating your wish that he/she fixes it so it runs how you feel.it should run
I'm pretty certain this info is old and if you looked you'd find all the magisk modules and gcams and mods and info floating around ...
go check out the official gcam mods page for devs working on cams for our device and try them.all to find the one you like best and maybe give them.a small donation
try out the stock cam magisk module to see if it works correctly on custom rom
failing that just your miui with magisk to have it all.
Stock makes great depth of field photos imho
Gcam takes richer photos in general like but if you aren't careful you might run in oversaturation ..more options
_you can enable arcore and ar stickers by magisk mod and using patched playground from gcam mods page

This doesn't seem to be a GCam issue... All camera apps just see 5MP for the front and secondary back camera. It's probably an internal issue with Camera2Api?

General Xiaomi Sensor Lottery - The Ultimate Poll

Hi folks.
It came to the attention of some users that Xiaomi mixes a lot the sensors that are used in this device. It´s indeed a lottery.
Although this might not greatly affect conventional user experience, there are still some differences that can become relevant when addressing bugs, faulty parts and overall complaints.
For instance:
Proximity Sensor - most of earlier units seem to have included Elliptic Labs Proximity Sensor (with high level of complaints), while later ones appear to increasingly come with Xiaomi Proximity Sensor - sourced from Minghao (apparently more reliable).
Camera - even though camera modules are all the same accross units, they come with a random mix of lenses. For instance, on main camera, the s5khm2_i_samsung denotes a lens sourced from Ofilm (with f1.9) and s5khm2_ii_samsung means that the lens came from Sunny (with f1.89) - so with slightly wider angle of capture. Also, even though quality of capture seems equivalent, Ofilm presents a slightly yellowish tint when compared to Sunny.
Gyro/Accelerometer - some units come with icm4x6xx from TDK (slightly more power draw but apparently more sensitive, and perhaps better EIS capabilities?) and others come with lsm6dso from STMicro (less power hungry but also less sensitive). TDK variants also appear to come with 32 sensors overall vs the 31 found on STMicro version - the additional one is xiaomi.sensor.free_fall, which seemingly protects the hard drive in case of falls.
Charger Board - some units come with bq2597x, while others come with ln8000 (reports of it having a buggy PMIC and more problems in Custom ROM compatibility - e.g. Poco X3 Pro)
Display Panel - apparently, most are sourced from Samsung (dsi_k6_38), although they can also come from Tianma (dsi_k6_36), Visionox (dsi_k6_41) or Huaxing (dsi_k6_42). For instance, I have two devices with the same Samsung panel reference and even so, they present very visible differences among them - with one being more bright with a slight reddish tint, and the other being a bit more contrasty, with less nits and with a slight yellowish tint.
As informed consumers, having complete information about what is inside our unit is a fair and reasonable ask.
Therefore, we are opening a poll below, so we can all share our sensor mix and try to understand if they form a pattern on how the device behaves.
For information on sensors, you can run the app Device Info HW (https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw).
For information on screen maker on unrooted MIUI, you can run a bug report - open the dialer and type *#*#284#*#* -> navigate to MIUI/debug_log/bugreport-date-time.zip -> inside the zip, open another zip called bugreport-version-date-time.zip -> open the file dumpstate_board.txt -> find "detect panel" -> et voila!
Feel free to answer the poll and provide more relevant details.
Cheers!

I'm curious on knowing the charging board, idk if my own Note 10 Pro has bq2597x or the infamous ln8000

Panel: K6_38_0C_0A_FHD_DSC_VIDEO
Accel & Gyro: lsm6dso
Touch: goodix_ts
Main camera: s5khm2_i_samsung
Charger board: ln8000
Proximity: Xiaomi

Proximity - Xiaomi
Main Camera - Sunny
Gyro - TDK
Charger Board - bq2597x
I can't get the screen info from Device Info HW (with root) or from the dialer.
I'll add, mine is more recent, ordered in March 2022 and shipped directly from China.

Xiaomi Redmi Note 10 Pro 6/128GB (manufactured 12-2021) M2101K6G (rooted)​
Screen: dsi_k6_38 (Samsung)
Gyro/Accelerometer: icm4x6xx (TDK)
Touchscreen: gtx8 (?!)
Camera:
s5khm2_i_samsung (f1.9)
imx471_i_sony
imx355_i_sony
gc02m1_i_gc
ov5675_i_ov
Charger Board: bq2597x-charger
Proximity: Xiaomi
I've got a different touchscreen: gtx8 (?)
I only knew about 'goodix_ts' and 'focaltech' fts_ts
The gtx8 works with TWRP and ArrowOS 12L
I also, keep reading that there is another camera chip used in some devices: s5khm2_ii_samsung
Touchscreen not working in TWRP
When I install TWRP and reboot into it, the touchscreen simply does not work, the same thing with OrangeFox
forum.xda-developers.com
I ordered a second handset with the sole intent to use a custom ROM and now worry that it will come with unsupported hardware.

david003 said:
Proximity - Xiaomi
Main Camera - Sunny
Gyro - TDK
Charger Board - bq2597x
I can't get the screen info from Device Info HW (with root) or from the dialer.
I'll add, mine is more recent, ordered in March 2022 and shipped directly from China.
Click to expand...
Click to collapse
The screen is called LCM in the Device Info HW app but it needs root.
Patoilo​For information on screen maker on unrooted MIUI, you can run a bug report - open the dialer and type *#*#284#*#* -> navigate to MIUI/debug_log/bugreport-date-time.zip -> inside the zip, open another zip called bugreport-version-date-time.zip -> open the file dumpstate_board.txt -> find "detect panel"

I have the Xiaomi Proximity Sensor on my 256GB variant and it's just as rubbish as the Elliptic Labs Proximity Sensor on my 128GB variant. Virtual proximity sensors are terrible.

Patoilo said:
[...]
Feel free to answer the poll and provide more relevant details.
Click to expand...
Click to collapse
I've just got a second device with another mix of sensors. You might consider allowing multiple voting in the poll (dunno if possible)
Xiaomi Redmi Note 10 Pro 6/128GB (manufactured 07-2022) M2101K6G (no root)​
Screen: detect panel K6_38_0C_0A_FHD_DSC_VIDEO
Gyro/Accelerometer: icm4x6xx (TDK)
Touchscreen: goodix_ts
Camera:
s5khm2_i_samsung (f1.9)
imx471_i_sony
imx355_ii_sony
ov02b1_ii_ov
ov5675_ii_ov
Charger Board: ln8000_charger
Proximity: Xiaomi
How bad the support for ln8000 is?

It is usual that manufacturers have a second source for components to keep up the supply chain in case one supplier faces difficulties.
Probably the following website is a more comprehensive source for developers to get a look on the different components that are used in the Redmi Note 10 Pro:
Last uploads - Device Info HW
deviceinfohw.ru

Fostel said:
The screen is called LCM in the Device Info HW app but it needs root.
Patoilo​For information on screen maker on unrooted MIUI, you can run a bug report - open the dialer and type *#*#284#*#* -> navigate to MIUI/debug_log/bugreport-date-time.zip -> inside the zip, open another zip called bugreport-version-date-time.zip -> open the file dumpstate_board.txt -> find "detect panel"
Click to expand...
Click to collapse
I tried the HW info app while the phone is rooted, and I can see LCM now. Mine shows dsi_k6_38_0c_0a_fhd_dsc_video_display, which I guess is Samsung.

Voted for whatever is present in my recently Amazon.es bought Xiaomi Redmi Note 10 Pro 6/128GB, namely:
Proximity - Xiaomi
Gyro/Accelerometer - icm4x6xx (TDK)
Charger Board - bq2597x
What is not in the survey entries but also present in my device:
Main Camera - s5khm2_ii_samsung (Edit: unnoticed typo in entry, it's the Samsung Sunny apparently, so corrected...)
Screen - fts_ts (K6_38_0C_0A_FHD_DSC_VIDEO in dumpstate_board.txt = Samsung or Focaltech?)
That screen one is really cheaty as it prevents me from installing TWRP (it looses touch), so I make do with last year's crDroid recovery -- because it can be driven entirely via hardware buttons...

pnin said:
Voted for whatever is present in my recently Amazon.es bought Xiaomi Redmi Note 10 Pro 6/128GB, namely:
Proximity - Xiaomi
Gyro/Accelerometer - icm4x6xx (TDK)
Charger Board - bq2597x
What is not in the survey entries but also present in my device:
Main Camera - s5khm2_ii_samsung (Edit: unnoticed typo in entry, it's the Samsung Sunny apparently, so corrected...)
Screen - fts_ts (K6_38_0C_0A_FHD_DSC_VIDEO in dumpstate_board.txt = Samsung or Focaltech?)
That screen one is really cheaty as it prevents me from installing TWRP (it looses touch), so I make do with last year's crDroid recovery -- because it can be driven entirely via hardware buttons...
Click to expand...
Click to collapse
The 'fts_ts' is a touchscreen that does not work on custom ROMs yet.
The 'K6_38_0C...' is the Samsung display.

Got the third device which has the same mix as the second one. Manufactured at the same time.
Xiaomi Redmi Note 10 Pro 6/128GB (manufactured 07-2022) M2101K6G (no root)​
Screen: detect panel K6_38_0C_0A_FHD_DSC_VIDEO
Gyro/Accelerometer: icm4x6xx (TDK)
Touchscreen: goodix_ts
Camera:
s5khm2_i_samsung (f1.9)
imx471_i_sony
imx355_ii_sony
ov02b1_ii_ov
ov5675_ii_ov
Charger Board: ln8000_charger
Proximity: Xiaomi
The screen is the same on all of them (Samsung K6_38) but the unit manufactured in 2021/12 produces a nicer (warmer) picture. Fortunately, Lineage gives the option to calibrate the display so I was able to tweak the RGB balance on the other ones.

pnin said:
Voted for whatever is present in my recently Amazon.es bought Xiaomi Redmi Note 10 Pro 6/128GB, namely:
Proximity - Xiaomi
Gyro/Accelerometer - icm4x6xx (TDK)
Charger Board - bq2597x
What is not in the survey entries but also present in my device:
Main Camera - s5khm2_ii_samsung (Edit: unnoticed typo in entry, it's the Samsung Sunny apparently, so corrected...)
Screen - fts_ts (K6_38_0C_0A_FHD_DSC_VIDEO in dumpstate_board.txt = Samsung or Focaltech?)
That screen one is really cheaty as it prevents me from installing TWRP (it looses touch), so I make do with last year's crDroid recovery -- because it can be driven entirely via hardware buttons...
Click to expand...
Click to collapse
there is an unofficial version of orangefox that works.
Release OrangeFox Recovery R11.1_3 · basamaryan/android_device_xiaomi_sweet-TWRP
Changelog: • Corrected version naming (R11) • Synced the latest OrangeFox source • Updated Magisk to 26.1 • Updated the kernel Notes: • There are 2 versions. One for MIUI and one for AOSP. The MIUI...
github.com

chemyy said:
there is an unofficial version of orangefox that works.
Release OrangeFox Recovery R11.1_3 · basamaryan/android_device_xiaomi_sweet-TWRP
Changelog: • Corrected version naming (R11) • Synced the latest OrangeFox source • Updated Magisk to 26.1 • Updated the kernel Notes: • There are 2 versions. One for MIUI and one for AOSP. The MIUI...
github.com
Click to expand...
Click to collapse
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com

Thanks for the info, @chemyy and @Sheist!.
EDIT: I have now tried this unofficial OFox (setting it up via fastboot) and I'm glad to report that IT WORKS!
FYI, I had tried many others previously, including the latest stable TWRP and PBRP, and none did...