Xiaomi Redmi Note 5 Pro - Marriage and Repair | Smartphone, 5.99 "
katya_acid faded screen. Read in the branch redmi 5 plus, ) (... Assassin'S ...) ( , ) Post has been editedeugeniub - 12.05.18, 22:45
Reason for editing: Modified
Eugeniub @ 05/12/18, 22:44
burned out the screen.
Nitsche he did not burn out. It is defective, the p5 + has a lot of complaints about such screens from the box. People do not soar, enjoy further. More precisely soars but there is no place to go. took in china ...
On account of the burnt screen. These are the jambs of the tianma matrix. Especially seen on a gray background. This is on rn4x, and on mi5s, now and here. (this is kst on LG g4 often)
I think this is a marriage. Have to put up with it
I think this is a marriage. Have to put up with it
Zooui @ 05/12/18, 22:46
Nitsche he did not burn out. He is defective
So fart the seller will take care and send a new one for replacement.
Rather than marriage, and feature matrices or firmware may internal wiring. Digging in Google, it is possible to find the cause, which is the appearance of a parasitic component of the controlled supply voltage and a constant electromagnetic field. As a result, ions in the matrix according to its polarity handful on a static image. At most this hat on the laptop (X230 matrix ips lp125wh2slb3) a year 4 and the screen is alive. It does not burn, just longer than a static picture on the screen, the longer it will depart. Perhaps the standard treatments missed first trimester pixels accelerate. For example:https://www.youtube.com/watch?v=ZjdrMuKpaCICAUTION EPILEPTICS.
Post has been editedhansel7 - 13.05.18, 00:27
Post has been editedhansel7 - 13.05.18, 00:27
hansel7 @ 05.13.18, 00:19
Rather, not a marriage, but a feature of the matrices or their firmware, possibly internal wiring
no marriage when all matrices behave this way. Another thing a couple of people out of 100. Regardless of the firmware. The memory effect remains physically and not soft. This does not exclude the possibility of killing the screen with an alpha version of the firmware, on which the people got burned ...
Post has been editedZooui - 13.05.18, 01:31
Zooui @ 05.13.18, 01:30
Regardless of the firmware. The memory effect remains physically and not soft. This does not exclude the possibility of killing the screen with an alpha version of the firmware, on which the people got burned ...
Speech about the firmware of the matrix itself. In the notebook / desktop version is EDID. It defines quite a lot of software parameters, such as color balancing, supported modes, resolution, and roughly speaking describes what the display can do and within what limits.
EDID 1.3 structure
Bytes Description
0–19 Header information
0–7 Fixed header pattern: 00 FF FF FF FF FF FF 00
8–9 Manufacturer ID. These IDs are assigned by Microsoft, they are PNP IDs "00001 = A"; "00010 = B"; ... "11010 = Z". Bit 7 (at address 08h) is 0, the first character (letter) is located at bits 6 → 2 (at address 08h), the second character (letter) is located at bits 1 → 0 (at address 09h), and the third character (letter) is located at bits 4 → 0 (at address 09h).
Bit 15 (Reserved, always 0)
Bits 14–10 First letter of manufacturer ID (byte 8, bits 6–2)
Bits 9–5 Second letter of manufacturer ID (byte 8, bit 1 through byte 9 bit 5)
Bits 4–0 Third letter of manufacturer ID (byte 9 bits 4–0)
10–11 Manufacturer product code. 16-bit number, little-endian.
12–15 Serial number. 32 bits, little endian.
16 Week of manufacture. Week numbering is not consistent between manufacturers.
17 Year of manufacture, less 1990. (1990–2245). If week = 255, it is the model year instead.
18 EDID version, usually 1 (for 1.3)
19 EDID revision, usually 3 (for 1.3)
20–24 Basic display parameters.
20 Video input parameters bitmap
Bit 7 = 1 Digital input. If set, the following bit definitions apply:
Bits 6–1 Reserved, must be 0
Bit 0 Signal is compatible with VESA DFP 1.x TMDS CRGB, 1 pixel clock, up to 8 bits per color, MSB aligned,
Bit 7 = 0 Analog input. If clear, the following bit definitions apply:
Bits 6–5 Video white and sync levels, relative to blank: 00 = + 0.7 / −0.3 V; 01 = + 0.714 / −0.286 V; 10 = + 1.0 / −0.4 V; 11 = + 0.7 / 0 V
Bit 4 Blank-to-black setup (pedestal) expected
Bit 3 Separate sync supported
Bit 2 Composite sync (on HSync) supported
Bit 1 Sync on green supported
Bit 0 VSync pulse must be serrated when composite or sync-on-green is used.
21 Maximum horizontal image size, in centimeters (max 292 cm / 115 in at 16: 9 aspect ratio)
22 Maximum vertical image size, in centimeters. If either byte is 0, undefined (e.g. projector)
23 Display gamma, datavalue = (gamma * 100) -100 (range 1.00–3.54)
24 Supported features bitmap
Bit 7 DPMS standby supported
Bit 6 DPMS suspend supported
Bit 5 DPMS active-off supported
Bits 4–3 Display type (digital): 00 = RGB 4: 4: 4; 01 = RGB 4: 4: 4 + YCrCb 4: 4: 4; 10 = RGB 4: 4: 4 + YCrCb 4: 2: 2; 11 = RGB 4: 4: 4 + YCrCb 4: 4: 4 + YCrCb 4: 2: 2
Bits 4-3 Display type (analog): 00 = Monochrome or Grayscale; 01 = RGB color; 10 = Non-RGB color; 11 = Undefined
Bit 2 Standard sRGB color space. Bytes 25–34 must contain sRGB standard values.
Bit 1 Preferred timing mode specified in descriptor block 1. For EDID 1.3. In this case, this bit specifies the preferred timing mode.
Bit 0 GTF supported with default parameter values.
25–34 Chromaticity coordinates.
10-bit CIE xy coordinates for red, green, blue, and white. [0–1023 / 1024].
25 Red and green least-significant bits
Bits 7–6 Red x value least-significant 2 bits
Bits 5–4 Red y value least-significant 2 bits
Bits 3–2 Green x value least-significant 2 bits
Bits 1–0 Green y value least-significant 2 bits
26 Blue and white least-significant 2 bits
27 Red x value most significant 8 bits. 0–255 encodes 0–0.996 (255/256); 0–0.999 (1023/1024) with lsbits
28 Red y value most significant 8 bits
29–30 Green x and y value most significant 8 bits
31–32 Blue x and y value most significant 8 bits
33–34 Default white point x and y value most significant 8 bits
35–37 Established timing bitmap. Supported bitmap for (formerly) very common timing modes.
35 Bit 7 720 Г— 400 @ 70 Hz
Bit 6 720 Г— 400 @ 88 Hz
Bit 5 640 Г— 480 @ 60 Hz
Bit 4 640 Г— 480 @ 67 Hz
Bit 3 640 Г— 480 @ 72 Hz
Bit 2 640 Г— 480 @ 75 Hz
Bit 1 800 Г— 600 @ 56 Hz
Bit 0 800 Г— 600 @ 60 Hz
36 Bit 7,800 Г— 600 @ 72 Hz
Bit 6 800 Г— 600 @ 75 Hz
Bit 5 832 Г— 624 @ 75 Hz
Bit 4 1024 Г— 768 @ 87 Hz, interlaced (1024 Г— 768i)
Bit 3 1024 Г— 768 @ 60 Hz
Bit 2 1024 Г— 768 @ 72 Hz
Bit 1 1024 Г— 768 @ 75 Hz
Bit 0 1280 Г— 1024 @ 75 Hz
37 Bit 7 1152x870 @ 75 Hz (Apple Macintosh II)
Bits 6–0 Other manufacturer-specific display modes
38–53 Standard timing information. Up to 8 2-byte fields describing standard display modes.
Unused fields are filled with 01 01
Byte 0 X resolution, divided by 8, less 31 (256–2288 pixels, value 00)
Byte 1 bits 7–6 X: Y pixel ratio: 00 = 16: 10; 01 = 4: 3; 10 = 5: 4; 11 = 16: 9.
(Versions prior to 1.3 defined 00 as 1: 1.)
Byte 1 bits 5–0 Vertical frequency less than 60 (60–123 Hz)
54–71 Descriptor 1 Descriptor blocks. Detailed timing descriptors, in decreasing preference order. After all the detailed timing descriptors, the additional descriptors are permitted:
Monitor range limits (required)
ASCII text (monitor name (required), monitor serial number or unstructured text)
6 Additional standard timing information blocks
Color point data
72–89 Descriptor 2
90–107 Descriptor 3
108–125 Descriptor 4
126 Number of extensions to follow. 0 if no extensions.
127 Checksum. Sum of all 128 bytes should equal 0 (mod 256).
0–19 Header information
0–7 Fixed header pattern: 00 FF FF FF FF FF FF 00
8–9 Manufacturer ID. These IDs are assigned by Microsoft, they are PNP IDs "00001 = A"; "00010 = B"; ... "11010 = Z". Bit 7 (at address 08h) is 0, the first character (letter) is located at bits 6 → 2 (at address 08h), the second character (letter) is located at bits 1 → 0 (at address 09h), and the third character (letter) is located at bits 4 → 0 (at address 09h).
Bit 15 (Reserved, always 0)
Bits 14–10 First letter of manufacturer ID (byte 8, bits 6–2)
Bits 9–5 Second letter of manufacturer ID (byte 8, bit 1 through byte 9 bit 5)
Bits 4–0 Third letter of manufacturer ID (byte 9 bits 4–0)
10–11 Manufacturer product code. 16-bit number, little-endian.
12–15 Serial number. 32 bits, little endian.
16 Week of manufacture. Week numbering is not consistent between manufacturers.
17 Year of manufacture, less 1990. (1990–2245). If week = 255, it is the model year instead.
18 EDID version, usually 1 (for 1.3)
19 EDID revision, usually 3 (for 1.3)
20–24 Basic display parameters.
20 Video input parameters bitmap
Bit 7 = 1 Digital input. If set, the following bit definitions apply:
Bits 6–1 Reserved, must be 0
Bit 0 Signal is compatible with VESA DFP 1.x TMDS CRGB, 1 pixel clock, up to 8 bits per color, MSB aligned,
Bit 7 = 0 Analog input. If clear, the following bit definitions apply:
Bits 6–5 Video white and sync levels, relative to blank: 00 = + 0.7 / −0.3 V; 01 = + 0.714 / −0.286 V; 10 = + 1.0 / −0.4 V; 11 = + 0.7 / 0 V
Bit 4 Blank-to-black setup (pedestal) expected
Bit 3 Separate sync supported
Bit 2 Composite sync (on HSync) supported
Bit 1 Sync on green supported
Bit 0 VSync pulse must be serrated when composite or sync-on-green is used.
21 Maximum horizontal image size, in centimeters (max 292 cm / 115 in at 16: 9 aspect ratio)
22 Maximum vertical image size, in centimeters. If either byte is 0, undefined (e.g. projector)
23 Display gamma, datavalue = (gamma * 100) -100 (range 1.00–3.54)
24 Supported features bitmap
Bit 7 DPMS standby supported
Bit 6 DPMS suspend supported
Bit 5 DPMS active-off supported
Bits 4–3 Display type (digital): 00 = RGB 4: 4: 4; 01 = RGB 4: 4: 4 + YCrCb 4: 4: 4; 10 = RGB 4: 4: 4 + YCrCb 4: 2: 2; 11 = RGB 4: 4: 4 + YCrCb 4: 4: 4 + YCrCb 4: 2: 2
Bits 4-3 Display type (analog): 00 = Monochrome or Grayscale; 01 = RGB color; 10 = Non-RGB color; 11 = Undefined
Bit 2 Standard sRGB color space. Bytes 25–34 must contain sRGB standard values.
Bit 1 Preferred timing mode specified in descriptor block 1. For EDID 1.3. In this case, this bit specifies the preferred timing mode.
Bit 0 GTF supported with default parameter values.
25–34 Chromaticity coordinates.
10-bit CIE xy coordinates for red, green, blue, and white. [0–1023 / 1024].
25 Red and green least-significant bits
Bits 7–6 Red x value least-significant 2 bits
Bits 5–4 Red y value least-significant 2 bits
Bits 3–2 Green x value least-significant 2 bits
Bits 1–0 Green y value least-significant 2 bits
26 Blue and white least-significant 2 bits
27 Red x value most significant 8 bits. 0–255 encodes 0–0.996 (255/256); 0–0.999 (1023/1024) with lsbits
28 Red y value most significant 8 bits
29–30 Green x and y value most significant 8 bits
31–32 Blue x and y value most significant 8 bits
33–34 Default white point x and y value most significant 8 bits
35–37 Established timing bitmap. Supported bitmap for (formerly) very common timing modes.
35 Bit 7 720 Г— 400 @ 70 Hz
Bit 6 720 Г— 400 @ 88 Hz
Bit 5 640 Г— 480 @ 60 Hz
Bit 4 640 Г— 480 @ 67 Hz
Bit 3 640 Г— 480 @ 72 Hz
Bit 2 640 Г— 480 @ 75 Hz
Bit 1 800 Г— 600 @ 56 Hz
Bit 0 800 Г— 600 @ 60 Hz
36 Bit 7,800 Г— 600 @ 72 Hz
Bit 6 800 Г— 600 @ 75 Hz
Bit 5 832 Г— 624 @ 75 Hz
Bit 4 1024 Г— 768 @ 87 Hz, interlaced (1024 Г— 768i)
Bit 3 1024 Г— 768 @ 60 Hz
Bit 2 1024 Г— 768 @ 72 Hz
Bit 1 1024 Г— 768 @ 75 Hz
Bit 0 1280 Г— 1024 @ 75 Hz
37 Bit 7 1152x870 @ 75 Hz (Apple Macintosh II)
Bits 6–0 Other manufacturer-specific display modes
38–53 Standard timing information. Up to 8 2-byte fields describing standard display modes.
Unused fields are filled with 01 01
Byte 0 X resolution, divided by 8, less 31 (256–2288 pixels, value 00)
Byte 1 bits 7–6 X: Y pixel ratio: 00 = 16: 10; 01 = 4: 3; 10 = 5: 4; 11 = 16: 9.
(Versions prior to 1.3 defined 00 as 1: 1.)
Byte 1 bits 5–0 Vertical frequency less than 60 (60–123 Hz)
54–71 Descriptor 1 Descriptor blocks. Detailed timing descriptors, in decreasing preference order. After all the detailed timing descriptors, the additional descriptors are permitted:
Monitor range limits (required)
ASCII text (monitor name (required), monitor serial number or unstructured text)
6 Additional standard timing information blocks
Color point data
72–89 Descriptor 2
90–107 Descriptor 3
108–125 Descriptor 4
126 Number of extensions to follow. 0 if no extensions.
127 Checksum. Sum of all 128 bytes should equal 0 (mod 256).
Probably in the telephone displays have an analog, or use the same standard. I do not delve into the essence. I admit that in the alpha version of the phone firmware settings of interaction with the output device have been changed. Perhaps frequency pixelization or something like that. As a result, the effect of fading images appears faster and more clearly. Android is still Linux, as the latter is able to turn a lot less than in native mode, for example pop "left" edid to display used or override some of its parameters.
Zooui @ 05.13.18, 01:30
no marriage when all matrices behave this way. Another thing a couple of people out of 100.
I will reveal a big secret, but even displays from one batch have discrepancies in physical characteristics, such as color gamut or white point balance. There are no two completely identical matrices. Its parameters are the aggregate component of the hardware + software parts. Where exactly is the jamb can answer only the person involved in the production. Most likely the screens of different hardware / software revisions. Some are influenced, others are not.
Post has been editedhansel7 - 13.05.18, 03:17
hansel7, The argument right now is a little niochem. In fact, we have "spoiled screens" with firmware, in the sense of "once and ready" back in no way. And the defective screens came such initially. Soft, too, was not cured by anyone. The rest of everything works and everyone is happy.
What you are saying right now would be the place to be right after the flashing, literally after the boot logo, the problem would have appeared. And the people still manage to do it. And the residual effect is not the most deplorable outcome that was.
Zooui @ 05/13/18, 02:35
The argument right now is a little niochem. In fact, we have "spoiled screens" with firmware, in the sense of "once and ready" back in no way. And the defective screens came such initially. Soft, too, was not cured by anyone. The rest of everything works and everyone is happy.
I did not argue. "Spoiled screens" from the manufacturer's position will be established only after the examination, but I think it will not come as in the user agreement to the same firmware version alpha certainly have a postscript to the disclaimer, as in other matters, and in the tolerances of the matrix itself to be the point that the memory effect is not a critical flaw, and therefore not covered by warranty. You can link to a discussion of who gets what and how treated? There are some doubts about the therapeutic methods.
Zooui @ 05/13/18, 02:35
What you are saying right now would be the place to be right after the flashing, literally after the boot logo, the problem would have appeared. And the people still manage to do it. And the residual effect is not the most deplorable outcome that was.
Not. I'm talking about the fact that the firmware could strengthen the already existing defect matrix. How and in what direction unfortunately I do not know.
Post has been editedhansel7 - 13.05.18, 03:00
Does anyone have such a problem that the eye of the upper chamber is not in the center?
Offset left of fingerprint sensor ...
Offset left of fingerprint sensor ...
Katya_acid @ 05/12/18, 10:15
Good day. I bought a global version of the phone yesterday. Today I noticed that if you use one application for a long time, and then open the camera or call. That residual picture remains on the screen. Should I go to change the phone or is it a feature of the screen? Maybe someone noticed something like that. Attaching photo.
Spoiler
In the microphone area you can see the line from Votsap. Then she disappeared. But there are doubts that it can only get worse
Spoiler
In the microphone area you can see the line from Votsap. Then she disappeared. But there are doubts that it can only get worse
Today I went to the service center. I reset the phone to the factory settings, but as expected, the problem did not dare. In general, I changed the phone
Post has been editedkatya_acid - 13.05.18, 15:46
Reason for editing: Supplement
Dimanovih @ 05/13/18 11:30
Does anyone have such a problem that the eye of the upper chamber is not in the center?
Naskat @ 05/10/18, 3:09
Does anyone play a SIM card slot in the inserted position?
Post has been editedsuper.cat - 13.05.18, 16:43
Katya_acid @ 05/13/18, 15:45
Today I went to the service center. I reset the phone to the factory settings, but as expected, the problem did not dare. In general, I changed the phone
I did not see that the phone was changed. Pretty weird. With a new tricks there?
Post has been editedhansel7 - 13.05.18, 17:23
hansel7 , If the problem persists then I will write it off here. For now, everything is fine
Post has been editedkatya_acid - 13.05.18, 17:25
Reason for editing: Interlocutor changed the question
I do Xiaomi phone sales to China, and so I have quite a lot of them bylo.I almost all seen this residual izobrazhenie.Tak here I had never noticed within six months of use Redmi Note 4, And I'm pretty picky about quality. so far I have about it (image Sticking) said one of customers.We only almost with a magnifying glass I could see it on his copy, and other tozhe.I it well, does not believe in marriage, because marriage is not well, can meet virtually in each of the 100 phone, just someone sees it, it is a residual image and someone net.Ya think so
©savagemessiahzine.com2005-2020 All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement