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.
PatoiloFor 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.
PatoiloFor 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...
Related
I have never been more confused by hardware variants. So, for the benefit of myself and other developers working on this device, I would like to compile all the relevant information about hardware variants here. And also what is working/not working.
Please, no chit chat. Only post here if you know the answer to these questions.
Fingerprint Sensor:
fpc1020 (older devices) and Goodix (newer devices)
Does the Goodix sensor work on all versions of MIUI or only the more recent versions?
Does the /data/goodix folder only show up if you have the goodix sensor?
Touchscreen:
FocalTech (older devices) and Atmel (newer devices)
Are there FocalTech devices with the Goodix fingerprint sensor? Or do all Goodix devices have the Atmel screen?
What is the output of
Code:
cat /sys/class/input/input*/name
Panel:
Mine is BOE, are there other panels?
Front Camera:
Are there different ones? and what versions of MIUI do they work on/not work on?
Rear Camera:
Are there different ones? and what versions of MIUI do they work on/not work on?
If you have goodix folder on /data,you have a goodix fp
Goodix fp works on all miui versions..
Sorry for my bad English
I have a phone with goodix fingerprint.
Does the Goodix sensor work on all versions of MIUI or only the more recent versions?
Does the /data/goodix folder only show up if you have the goodix sensor?
Click to expand...
Click to collapse
It works on all MIUI Lollipop versions. Also it works on Miui MM (6.7.21; other versions was not tested by me) but sometimes.
It does not work on the official CM13 builds. Maybe it need fingerprintd patch to work. So we need source code.
Front Camera:
Are there different ones? and what versions of MIUI do they work on/not work on?
Click to expand...
Click to collapse
I think that there two revisions with different front camera hardware.
Both versions has driver in the CM13 kernel sources. All works on all miui versions.
BUT it does not work on custom MM roms because TheStrix did not add enough blobs from MiuiMM vendor folder
my panel is BOE too (no vibro on buttons in cm) but second version is TIANMA
I have goodix fp, atmel touchscreen and newest rear camera which one isnt working on custom roms. What a good chance How can I know which panel in my phone? And I want to know, is there any chance to all the these working together except miui? Sorry for my bad english.
mine tianma nt35596 panel fpc fp sensor
mine tianma nt35596 panel fpc fp sensor
There are 3 panels boe,sharp and tianma. I have tianma, also there are 2 different light sensors liteon and sensortek I have liteon.
Sent from my Redmi Note 3 using Tapatalk
theres 2 back camera (s5k3p3_omida and s5k3p3_fxxxx i forgot the numbers after f)
and 3 front cam (doesnt remember)
Fingerprint Sensor:
I have FPC1020 one. I guess most of kenzo's have it.
For CM, I use fingerprint HAL/libs from MIUI M builds for kenzo. We have updated FPC1020 kernel driver that works with M fingerprint HALs. (here)
Not sure about goodix, I never tried it. Maybe the kernel driver released by Xiaomi in their LP release may not go well with M Goodix fingerprint HAL/libs found in MIUI M builds for kenzo. (As LP HALs won't work on M)
Touchscreen:
I have Focaltech FT5X06 one.
Of what I know till now, I never saw a Goodix FP sensor being shipped with devices with Atmel touchscreen (I may be wrong here though)
Display Panels:
Xiaomi added device tree entries for 3 panels in their kernel release
tianma-nt35596
boe-nt35532
sharp-r63315
Mine has tianma-nt35596. And I have seen the devices having the other 2 panels. Also I never came across any RN3 other than these 3 panels so this is it most probably.
Front Camera:
Mine has "ov5670_omi5f06"
Would like to know what all camera sensors other than this Xiaomi ships.
I have a jira issue reported for CM13 by some guy claiming from camera do not work for him. Recently said he have a
Rear Camera:
Mine has "s5k3p3_omida01"
Again, would like to know what all camera sensors other than this Xiaomi ships.
I think, few have "s5k3p3_gt24c64" as well.
EDIT: For the eeprom{0,1,2,3,4,6} defined here,
"qcom,[email protected]" (rear) uses eeprom0 eeprom1 eeprom3 eeprom4
"qcom,[email protected]" (front) uses eeprom2 eeprom6
Now, about additional sensors mentioned here, are handled by this code committed by Xiaomi originally: https://github.com/TheStrix/android...mmit/a887d0c73d029c339a50dc8d16ce698c13eaa1ae
TheStrix said:
Rear Camera:
Mine has "s5k3p3_omida01"
Again, would like to know what all camera sensors other than this Xiaomi ships.
I think, few have "s5k3p3_gt24c64" as well.
Click to expand...
Click to collapse
Most devices have either Omida or s5k3p3_f16s01c
@TheStrix I have Atmel and goodix in my device. How can I know which panel and camera sensor is in my device? Sorry for my english.
Probably rare, but I have a Sharp r63315 panel
Indian version of Kenzo comes with Mostly Tianma nt35596 and Focaltech (FW) 0×20, Camera Rear Samsung S5k3p3_omida01, Front Omnivision ov5670_omif506 and Lightsensor is sensortek(I have replaced LCD panel and after that i got same tianma and Fpc so mostly in india they ship with Tianma,Fpc)
Goodix FP related files displayed in "/sys/class" folder on my device.
mine has
TP Version: FocalTech FT5346
LCD Tianma nt35596
Camera s5k3p3_omida01, ov5670_omi5f06
FPC Fingerprint
Sensortek proximity sensor
(bought from china)
btw I just bought mine recently and on the box it says 2016.7 so I don't think older / newer decides the hardware in the phone, probably factory's or maybe just the availability of parts.
I have two Redmi Note 3:
Dark Gray 32GB (Aug/2016):
Fingerprint Sensor:
Not unlocked bootloader so cannot conclusively tell one, but can take photos by fingerprint. Also have "uninput-fpc" in /sys/class/input/input11/name, and "[email protected]_fpc1020.108" in /sys/class/input/input11/name.
So I guess it is FPC one.
Touchscreen:
Focaltech FT5346
Display Panels:
tianma-nt35596.
Back Camera:
s5k3p3_omida01
Front Camera:
ov5670_omi5f06
Gold 32GB (July/2016):
Fingerprint Sensor:
Same as the above.
Touchscreen:
ATMEL
Display Panels:
boe-nt35532
Back Camera:
s5k3p3_omida01
Front Camera:
ov5670_omi5f06
i have s5k5e8_yx13:0 front camera sensor
Cod3AlchemisT said:
I have two Redmi Note 3:
Dark Gray 32GB (Aug/2016):
Fingerprint Sensor:
Not unlocked bootloader so cannot conclusively tell one, but can take photos by fingerprint. Also have "uninput-fpc" in /sys/class/input/input11/name, and "[email protected]_fpc1020.108" in /sys/class/input/input11/name.
So I guess it is FPC one.
Touchscreen:
Focaltech FT5346
Display Panels:
tianma-nt35596.
Back Camera:
s5k3p3_omida01
Front Camera:
ov5670_omi5f06
Gold 32GB (July/2016):
Fingerprint Sensor:
Same as the above.
Touchscreen:
ATMEL
Display Panels:
boe-nt35532
Back Camera:
s5k3p3_omida01
Front Camera:
ov5670_omi5f06
Click to expand...
Click to collapse
The color doesn't matter
I have a jira issue reported for CM13 by some guy claiming from camera do not work for him. Recently said he have a
Click to expand...
Click to collapse
Yeah, that's me
---------- Post added at 10:06 PM ---------- Previous post was at 10:02 PM ----------
FP : fpc102x( probably 1020 ) worked on all ROMs that have been tested ( miui+cm )
Panel : BOE
Touchscreen : Atmel dt2w kernel doesnt work
Front camera : S5K5E8 works only on the miui based ROMs ( including xiaomi.eu ones )
Back camera : S5K3P3 worked on all ROMs that have been tested ( miui+cm ). The flash is bugged, capturing images with flash is really weird, the exposure is incorrectly set and the picture gets whitish and unrealistic colors, when i turn off the flashlight it has a weird double flickering instead of just turning off, really weird and uncommon on the mediatek version. ( i had the mtk in the past )
Im really looking forward for fixes related to the front camera, its really painful it does not work with official cm 13 ROM
---------- Post added at 10:10 PM ---------- Previous post was at 10:06 PM ----------
Light sensor : stk3x1x ( seems to be the same as proximity one, im getting all the information from Aida64
Kate Hardware
@flar2 would it also be possible to officially support the Redmi Note 3 Special Edition?
This version is originally meant for the Taiwanese market, but it features all the necessary LTE Frequencies to work in Europe. The Pro version lacks LTE here in Germany (one important band not supported).
The special edition will boot CM13 with it's kernel, it will just force close in the fingerprint settings. This apparently can be fixed by flashing the Kenzo firmware (without radio).
I will get my Special Edition early next week and will be posting the hardware details in this thread.
If so, how did you do it?
Thanks in advance!
Honestly i don't understand what do you mean!
But just now i found this post on Facebook Group!
---------------
Modification of Google Cameras ?
Version 7.0.009.259843690
Modification version: Stable version of V5.
I want to express my deep gratitude to the people who helped me both mentally and through deeds, because together we achieved our result: we tried to make 7.0.009 more stable than it was before.
Good luck with your photos!
Modification of version 7.0.009 V5
Cloud
Attention after installing the modification, clear the application data, otherwise the application may experience problems while working with it. Hope for understanding.
• Added the item "Use improved bonding of frames" Saber "". Saber is a merge method created by Google that improves the quality of photos in some modes. Some call it “super resolution” because of the sharpness / detail refinement. Sometimes "Saber" is not supported by all cameras, and Google Camera crashes after shooting. In this case, the only solution is to disable Saber. It was made in the majority at the request of the owners of Redmi K20 Pro.
• Added item "Auto White Balance in Auto HDR +". Selecting auto white balance will work the same on Auto HDR +.
• Added item "Image Zoom". Thanks xenius9.
• Fixed "Astrophotography" mode.
• "Astrophotography" mode is activated by default, no need to go into any settings. Installed and use. It was tested on the Redmi K20 PRO. Thank you burial.live for the tests and patience.
• IQ library updated to version 3.7. Thanks r0m10.
• Added item "Suppression of hot pixels". Hot pixels in the photo will be suppressed. Thanks xenius9.
• Added item "Ignore black pixels". Black dots in the photo will be suppressed. Thanks xenius9.
• Added item "Compression DNG" RAW "". Reduces the size of DNG "RAW" files. There is no direct relationship between quality and final size.
• The items related to the mode in the item "Settings for Developers" are changed to:
camera.cuttle.tripod - the tripod itself.
camera.cuttle.tripod_interface - interface.
In general, I do not recommend turning it off.
• Added code to hide slow motion due to its inoperability on devices: MI 9T, MI 9, Redmi K20, Redmi K20 Pro, Redmi Note7 Pro, Redmi Note 4, Zenfone Max Pro M2.
• Saber now works on Redmi Note 7, but only with a tripod, otherwise I’ll be blurry. It is not known how I achieved this in the testing process already.
• Replaced a third of all the icons.
• Minor changes.
____________
The link
https://mega.nz/#!ue5HzaTT!V2_TC7hjDJ_cDTeygr6c4_M9aWpqJdBUu4O1pTRPy54
Of the five phones I've owned recently with rear fingerprint sensors (Honor 7X, Honor 8X, Samsung S9, Google Pixel 3a, Redmi Note 7), the only one which doesn't natively support fingerprint gestures is the Redmi Note 7.
Therefore, I can't swipe down or up on the fingerprint sensor on the Redmi Note 7 to expand or collapse the notification shade the way I can on the other phones. This is a major annoyance for me since I use the notification shade often when I'm using a phone one-handed, and the rear fingerprint sensor is so convenient for this purpose.
So I tried about a dozen different apps on the Play Store until I found one that did exactly what I wanted, and it's free. It's called Keyboard/Button Mapper.
https://play.google.com/store/apps/details?id=io.github.sds100.keymapper
It's not so easy to figure out at first, so I can post instructions if anyone needs help. In summary, however, you would create two new keymaps with the following mappings:
Trigger: <swipe down>
Action: Expand Notification Drawer
Trigger: <swipe up>
Action: Collapse Status Bar
With this one fix, the Redmi Note 7 can be just as convenient to use one-handed as any other modern phone. Enjoy.
does not even recognize my fingerprint sensor when applying for the trigger action
Alifirdaus said:
does not even recognize my fingerprint sensor when applying for the trigger action
Click to expand...
Click to collapse
Hi Alifirdaus. I'm sorry to hear that it's not working for you. Please list the steps you took so that I might help you. Thanks.
I have enabled all app requests (fixes) including root permission but the app does not recognize the fingerprint actions.
Mine doesnt work either... i just updated to MIUI 12... I'm not rooted. does this require root? thanks!
Gosh I've been looking for an app like this for so looooooong !! Thanks !! Working on my pocophone x3 Surya running arrow os android 11
Unfortunately I'm getting this on my Poco X3 NFC with custom rom. Any other solutions? Xposed edge pro doesn't recognize the fingerprint sensor.
Check the latest news about FW here:
Release Notes
zentalk.asus.com
Anyone found the .raw firmware for Zenfone 8?
Asus android 12 beta
Android-12-Beta | ASUS Global
www.asus.com
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/OPEN-ZS590KS-31.01.2.7-BSP-user_20210513-release.zip
Android 11 raw image
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW__ZS590KS_30.11.51.41_MR0_20210513_release-user.raw.zip
NisseGurra said:
Android 11 raw image
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW__ZS590KS_30.11.51.41_MR0_20210513_release-user.raw.zip
Click to expand...
Click to collapse
This zip file contains boot_debug.img that enables adb root access. Is it possible to flash/boot that boot img without unlocking the bootloader?
No idea, i stuck at edl mode right now, need bit help from asus tech
Source codes global (WW):
Zenfone 8｜Phones｜ASUS Global
A new compact powerful choice: Flagship 5G processor · 120Hz AMOLED display · 4000mAh battery · Pro-grade dual rear and front camera · IP68 water resistant
www.asus.com
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/zenfone8_zs590ks.MR0-30.11.51.41.zip
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/zenfone8_zs590ks.mp-30.10.46.36.zip
Zenfone 8｜Phones｜ASUS Global
A new compact powerful choice: Flagship 5G processor · 120Hz AMOLED display · 4000mAh battery · Pro-grade dual rear and front camera · IP68 water resistant
www.asus.com
How to update it manually? In case of bootloop we needs the raw image?
Version WW-30.11.51.44
2021/05/21 2.76 GBytes ZenFone 8 software Image：WW_30.11.51.44 for WW/EU/RU/MS Improved Item:
1 Improved system stability
2 Improved system performance
3 Added one-hand mode and guidance instructions
4 Improved fingerprint unlock animation
5 Added Document mode to the ASUS Camera
6 Added capsule-style icon in the status bar for specific scenarios such as phone call, sound recording, etc.
7 Adjusted the opening animation of the front camera
8 Improved camera quality
9 Added priority mode in ASUS Settings
10 Added search function in Force Dark Mode.
11 Enabled VoLTE on Telia (Lithuania)
12 Enabled VoLTE & VoWifi on ICE (Norway) 13 Updated Android security patch
14 Enabled VoLTE on Vodafone (Spain)
15 Fixed issue where ultra durable notification could not be removed
16 Fixed thumbnails issue in 3rd party camera.
Click to expand...
Click to collapse
There is no raw firmware out (yet) and ASUS do not provide it.
NisseGurra said:
There is no raw firmware out (yet) and ASUS do not provide it.
Click to expand...
Click to collapse
The downgrade firmware in Android 12 Beta page actually is a raw firmware
Here is direct link
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW__ZS590KS_30.11.51.41_MR0_20210513_release-user.raw.zip
And here are the screenshot what inside the zip file and firmware folder
mickey36736 said:
The downgrade firmware in Android 12 Beta page actually is a raw firmware
Here is direct link
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW__ZS590KS_30.11.51.41_MR0_20210513_release-user.raw.zip
And here are the screenshot what inside the zip file and firmware folder
Click to expand...
Click to collapse
But the actual .raw file is not included so no go to fix bricked zenfone 8
So I can't play with it in case of bootloops we aren't able to restore it back :/
New Update:
[210524]ZenFone 8_WW_30.11.51.50
【Release Note】
Optimized Phone call quality
Improved camera quality
Improved system stability
Enabled VoLTE on Telekom (Germany)
Enabled VoLTE on Tele2 (Russia)
Enabled VoLTE & VoWiFi on O2 (Czech Republic)
It looks like artifacts in HDR are gone and it looks close to gcam now.
[210603]ZenFone 8_EU_30.11.51.57
【Version】 30.11.51.57 【Model Name】 ZenFone 8 (ZS590KS) 【Release Date】 2021/06/07 Since the server pushes update notice to different serial numbers by batches, it may take some days for you to receive the FOTA notice. Thanks for your patience. You may tap “System updates” in [Settings]...
zentalk.asus.com
【Release Note】
Optimized call quality
Enhanced wide camera contrast and improved ultra-wide camera Night mode for ASUS Camera.
Optimized system stability
Added gesture detection sensitivity in one-handed mode
Added SMS type QR code support in ASUS Camera app
Fixed the problem that some apps cannot be set to full screen mode
Fixed issue which could cause Gboard settings to periodically change back to default values
Fixed Status bar display issue
Enabled VoLTE & VoWiFi on Telia (Norway & Finland)
Enabled VoLTE on MTS (Russia)
Enabled VoLTE on Orange (Spain)
Improved issue where playback of Netflix HDR videos would stutter after a short while.
NisseGurra said:
[210603]ZenFone 8_EU_30.11.51.57
【Version】 30.11.51.57 【Model Name】 ZenFone 8 (ZS590KS) 【Release Date】 2021/06/07 Since the server pushes update notice to different serial numbers by batches, it may take some days for you to receive the FOTA notice. Thanks for your patience. You may tap “System updates” in [Settings]...
zentalk.asus.com
【Release Note】
Optimized call quality
Enhanced wide camera contrast and improved ultra-wide camera Night mode for ASUS Camera.
Optimized system stability
Added gesture detection sensitivity in one-handed mode
Added SMS type QR code support in ASUS Camera app
Fixed the problem that some apps cannot be set to full screen mode
Fixed issue which could cause Gboard settings to periodically change back to default values
Fixed Status bar display issue
Enabled VoLTE & VoWiFi on Telia (Norway & Finland)
Enabled VoLTE on MTS (Russia)
Enabled VoLTE on Orange (Spain)
Improved issue where playback of Netflix HDR videos would stutter after a short while.
Click to expand...
Click to collapse
Anyone else experiencing significant delay in screen waking up then pressing power button after this update?
raimis78 said:
Anyone else experiencing significant delay in screen waking up then pressing power button after this update?
Click to expand...
Click to collapse
My settings: fingerprint > screen off unlock > hide
Pick up phone to show indicator > off
Tap screen to show > off
After update to the new FW, I can unlock the phone with my right thumb, but not with the left one. This worked before the update. I tried adding a new fingerprint, but it did not help.
epaladin said:
My settings: fingerprint > screen off unlock > hide
Pick up phone to show indicator > off
Tap screen to show > off
After update to the new FW, I can unlock the phone with my right thumb, but not with the left one. This worked before the update. I tried adding a new fingerprint, but it did not help.
Click to expand...
Click to collapse
That's not exactly what I mean, you can see video below that pretty much explains my issue:
What I noticed, that delay is about halfed if I use standard Asus launcher, but it's still too slow. With Nova launcher it is as in the video.
ZenFone 8_RU_30.11.51.60
【Release Note】
Optimized system stability
Optimized fingerprint stability
Improved system power consumption
So it took me a couple of days but I developed a rear screen mirroring app called Mirror2RearUltra. It consists of a quick setting tile and nothing more.
Try it out for yourself, see what happens. I don't know how to squash the bugs but the source (and APK) is available on GitHub if anybody wants to take a peek.
Yes, it does mirror the display onto the rear display.
GitHub - tpkarras/Mirror2RearUltra: Rear screen mirroring plugin/app for Xiaomi Mi 11 Ultra.
Rear screen mirroring plugin/app for Xiaomi Mi 11 Ultra. - GitHub - tpkarras/Mirror2RearUltra: Rear screen mirroring plugin/app for Xiaomi Mi 11 Ultra.
github.com
Nothing happens when I start it. I see the headline, but the app interface is blank.
I'm not supposed if that's the expected behavior, but it doesn't seem to do anything regardless.
GuyWithRootedPhone said:
So it took me a couple of days but I developed a rear screen mirroring app called Mirror2RearUltra. It consists of a quick setting tile and nothing more.
Click to expand...
Click to collapse
Thank you.
But please specify which are the requirements:
- root ?
- Android version ?
- ROM ?
These info are not available also on your github repository.
munky-head said:
Nothing happens when I start it. I see the headline, but the app interface is blank.
I'm not supposed if that's the expected behavior, but it doesn't seem to do anything regardless.
Click to expand...
Click to collapse
you're supposed to start it from the quick tile.
themissionimpossible said:
Thank you.
But please specify which are the requirements:
- root ?
- Android version ?
- ROM ?
These info are not available also on your github repository.
Click to expand...
Click to collapse
it should be usable without root.
11 min (since that's what the Mi 11 Ultra) shipped with.
MIUI (developed with Xiaomi.eu) but should work with any MIUI version.
nasıl yükleyeceğimi anlamadım
I don't understand how to install it
frelinnn said:
I don't understand how to install it
Click to expand...
Click to collapse
release I uploaded didn't work, fixing it asap.
GuyWithRootedPhone said:
release I uploaded didn't work, fixing it asap.
Click to expand...
Click to collapse
and... fixed!
Great. Works a treat. Thank you.
@GuyWithRootedPhone I was just reviewing your code on github and as a casual android developer with no experience with this kind of thing (dealing with extra screens) it doesn't look TOO hard. I was wondering though, do you think it'd be possible to build an application that could read notifications and display them to the subscreen? I just absolutely hate that Xiaomi only allows it's default messaging and dialer app to display actual details to the subscreen. I love Google's implementation of Messenger and that's my preferred texting app, but with that as default, nothing appears like the Xiaomi messenger. Same situation with Google's dialer application.
If you have any ideas/tips you could throw my way, I'd be very interested in working on such an app that would allow selected applications to display their contents on the subscreen.
beta 2 is out... it takes methods from the subscreen app installed on the Mi 11 Ultra in an attempt to keep the screen on.
if anybody has any ideas or suggestions on how to keep the screen on full brightness without modifying the settings, that would be super helpful.
Release 1.0-beta2 · tpkarras/Mirror2RearUltra
added code to wake screen up upon launch/wake.
github.com
beta 3 is out, did some tweaks to get it to work on older devices.
if anybody can help me figure out how to keep the screen brightness on the rear display to max. I'd buy you a coffee, I'm struggling to figure out how this all works.
Release 1.0-beta3 · tpkarras/Mirror2RearUltra
Minor fixes. Fixed bug involving face down sensor.
github.com
This app isn't doing a thing
I actually had an idea about using rear screen as an input surface while gaming. For example you can map touches/swipes on rear screen onto an action/touch on front screen area and get another functionality. Your app is quite promising to start with. Thanks for this.
droidDHD said:
This app isn't doing a thing
Click to expand...
Click to collapse
can you logcat the app? i need to know if it's crashing or not.
Works fine on mine. Once installed, just swipe from the top, turn it on, click start now and when you tap rear screen to start, it shows main screen. Sorry can't take rear screenshot.
Rotation doesn't work.
Try put camera in video mode and you will end up upside down on rear display.
I would like this to work, because this is my missing feature from Android 12. That all camera options are seen in rear display.
I can't use android 12 and mui 13 because of one sim not able to do call forwarding.
Otherwise works, would be better if it was written in advance that you need to place it in quick launch.
不错 很好用
fixed the brightness to keep the screen bright at all times.
this is the final release, hoping it works for everybody.
Release 1.0-final · tpkarras/Mirror2RearUltra
includes fix to keep screen bright and prevent touch inputs.
github.com