Database Develop

screen calibration

Is there any programme to for screen calibration? So part of the screen seems not responsive.

That is a hardware issue not a Calabration issue..

does somebody know if this "hardware issue" is present at all note's?
i found that my screen is a bit unresponsive at the top right corner. i cant draw about 2mm to the border of the screen (with the pen)!

lolcat12 said:
That is a hardware issue not a Calabration issue..
Click to expand...
Click to collapse
However when I flash a new rom the screen get responsive for a short while. After that I need to press the screen harder. On the bottom right hand corner has this problem.

helmetbox said:
However when I flash a new rom the screen get responsive for a short while. After that I need to press the screen harder. On the bottom right hand corner has this problem.
Click to expand...
Click to collapse
Did you ever solve this problem? Mine started doing it after it updated KL7 OTA.

Well guys I'd like for someone to chime in on this. I thought for sure this was a hardware issue. I'm on my second note now. My first note seemed like it was having issues with the lower right corner of the touch screen. I thought maybe it was a rom issue. I flashed clean KL7 and it seemed to suddenly be better then after a little bit it got worse. I have my second note and I flashed KL7 right away on it. Now after a little bit it seems to be getting less responsive, still better than my first, but I'm beginning to think this is a software issue. Any of you having these issues what Rom are you on? Should I try changing out this note for a third and see what happens? I may flash to some other firmwares to see too.

my top right is a bit unresponsive as well. . it works but seems a bit off. .

I used swipepad , really useful taskswitcher
It does not work when phone is connected any charger.

I've definitely noticed the phone being less responsive when on the charger, but this seems to lose responsiveness over time off charger and on battery.
I've had other phones that from time to time would act a little wonky when using them while charging.

Hey,
I've had some display problems, both with regards to calibration and also when it's charging.
I have made this video to demonstrate a problem I have of calibration. Watch how the display detects a signal at a point offset from where I press with the pen.

For me the problem I saw using the *#*#2664#*#* test is that the last 10 pixels or so on the 2 end sides of the screen don't respond.
For the pen offset is cause of the left or right handed settings, I find that holding the pen and rotating it so that my thumb presses the button of the pen instead of the indicator finger gives pretty good accurate results.

I'm definitely thinking this is at least more software related than hardware. I don't remember noticing any problems when on KJ1 or KK1. So I flashed back to KK1. It started it up and then I did a quick factory reset. This is completely stock/unrooted. Anyway bottom right corner seems to be having no problems detecting my touch now. I'll leave it on this for a few days and play around and see if it seems to lose sensitivity again. If it does I'll let you guys know, but for this to be a hardware problem I can't imagine it being this intermittent. Any of you on KL7 that mentioned this issue, are you guys completely stock KL7 or using the CF-Root Kernel? I know someone mentioned losing functionality in music player and torch and it seemed to be an issue with an alternate kernel.

trumpetboy101 said:
Hey,
I've had some display problems, both with regards to calibration and also when it's charging.
I have made this video to demonstrate a problem I have of calibration. Watch how the display detects a signal at a point offset from where I press with the pen.
Click to expand...
Click to collapse
That´s normal - pen is calibrated to use it at a certain angle - try to change the setup from right handed to left handed and you will see a different offset if you make the same test again.
The offset should be the same on each area. Only if this is not the case i would say, there is an issue with the screen.

Hey, ok so it is a deliberate software decision. Kinda sucks- I'd think I'd sooner like to have it type directly below where I write. I'm guessing it is an attempt to account for the fact that the glass has a finite thickness. Sooooo does anybody fancy writing a kernel alteration for this...?

i also find it more annoying than useful

Couple days on KK1 and what I thought was a hardware problem still seems to be fine. It's detecting much better in the bottom right corner where I was having issues on KL7.

I am having the same issue with the reduced responsiveness of the bottom right corner. I've noticed it after updating to KL7. Maybe is the driver of the screen.
Is there any way we could report this back to Samsung?
Sent from my GT-N7000 using XDA App

Hello.
I have the same problem ate bottom right side of the screen. I am ate LA4.
what should I do?

Although the problem was nearly imperceptible some days ago, while the note was connected to the charger, I've noted a very small area near the bottom right side of the screen where it was difficult to write using the stylus with SMemo. On the opposite side the loudspeaker is present; and so I've thought it might be correlated with the magnetic field of the loudspeaker. Today I've performed the *#*#2664#*#* test with and withouth the charger, but the problem is not occurred. Because of these devices are always more complex I prefer snap closures for my cases.

Purple/pink tint camera, what exactly is the fault with?

Is it the camera module or some kind of motherboard?
I'm confused it works well from the freezer and I want to replace the faulty part but don't know what the faulty part is.
Opened it up earlier today only damaged the case slightly and it took 10 mins.

vrsdroid said:
Is it the camera module or some kind of motherboard?
I'm confused it works well from the freezer and I want to replace the faulty part but don't know what the faulty part is.
Opened it up earlier today only damaged the case slightly and it took 10 mins.
Click to expand...
Click to collapse
The problem is with the Camera Module. HTC confirmed this as a manufacturing defect, they would have fixed it for free.
Anyway to the best of my knowledge the problem was inadequate heat shielding for the Camera Module. Over time heat from the phones internal components (Processor, Battery etc) damages the lens inside the Camera Module producing the purple hue you see in your images. The warmer the device the worse it looks hence the reason it works ok after being in the freezer.
I sent my to HTC for repair I don't know exactly what they did but it came back good as new and so far the problem has not returned. Maybe they replaced it with an upgraded camera module or the same module but improved the heat shielding. Or maybe they just put the same module back in and the problem will return although I've never heard of it coming back after a HTC repair, only time will tell I suppose.

if you removed the back you can lift the camera and insert a thermal insulator , without having
to take apart everything ; you can put a thin plastic .
i could put a small circular magnet behind the camera myself when i was trying to fix the focus problem ,
there is some room.
Also put your phone in power saver it could help for the high temps.

Thanks for the replys, I did try lifting the camera even inserted something to the back of it and left it hanging out it still had the problem so I guess it just needs replacing May aswell replace the battery while I'm at it!
Thanks again

Quick update, I jjust replaced the camera module and it still has the pink tint now I'm lost anyone have any idea what's going on?

Does anyone know what is going on? perfect camera during the day but still pink/purple at night or dark I thought this would have been fixed after changing the module but obviously not is there anything else i can try?
And for those who have taken apart the camera module whats with the little sensor type thing on the camera modules ribbon? is that where the problem lies? a little square box lies beneath the copper heatshield it looks just like a megapixel sensor but is completely covered up.

[Q] Htc one m7 screen problem

Part of my m7 touch screen isnt working .. its kinda crazy cuz the phone never got dropped .. i saw that many people had that problem its between this two parts of screen that doesnt work theres a line that working..sometimes the touch isnt working at all !!
(when people call me sometimes).
its really disappointing cuz i like htc very much !
another problem that im having and saw that many people has it too : screen brightness always go maximum ! auto off for sure but still the brightness making problem tryed to reset the phone didnt help( not hard reset) it sucks to have a bunch of problems in a new phone ..
please please help me !
post.img.org/image/6naksobvx/
delete the dot in postimage ! sorry but this photo will help you understand and i have to share it !

Areas of the screen not registering touch input in most cases is a hardware issue with the digitizer. Loose digitizer connector may cause similar issues, but the only way to check is to open the phone. Opening is not easy and there is a high risk to damage the body. If you decide to go this way, my suggestion is to get new front and back panels + screen kit and to transplant the rest into the new housing. It's also a good time to replace a worn battery or a faulty camera module.

Val D. said:
Areas of the screen not registering touch input in most cases is a hardware issue with the digitizer. Loose digitizer connector may cause similar issues, but the only way to check is to open the phone. Opening is not easy and there is a high risk to damage the body. If you decide to go this way, my suggestion is to get new front and back panels + screen kit and to transplant the rest into the new housing. It's also a good time to replace a worn battery or a faulty camera module.
Click to expand...
Click to collapse
some times the screen back to full funcanlity
and please help about the other problem with the brightness .. its look like one of the sensors is broken in the phone .. maybe its the problem ?

When Auto Brightness is set to Off, the phone is not using the light sensor.
You'll have better chance to get help if you provide some basic information about your phone:
- What OS version? (KK, LP, stock, custom)
- Was the phone factory reset after the last OS update? (highly recommended)
- Do you use any applications that control screen brightness? (like some picture viewers, barcode display apps, etc.)
You may fix the brightness issue (most likely software related), but non working digitizer on parts of the screen is hardware related and no app will fix this.

Val D. said:
When Auto Brightness is set to Off, the phone is not using the light sensor.
You'll have better chance to get help if you provide some basic information about your phone:
- What OS version? (KK, LP, stock, custom)
- Was the phone factory reset after the last OS update? (highly recommended)
- Do you use any applications that control screen brightness? (like some picture viewers, barcode display apps, etc.)
You may fix the brightness issue (most likely software related), but non working digitizer on parts of the screen is hardware related and no app will fix this.
Click to expand...
Click to collapse
lollipop not root and other .. i deleted everything , did a soft reset not the hard type . no but i download lux to see if its help and it doesnt help either

The only thing left to try on a software side is factory reset the device. Many users report it clears various OTA Lollipop update bugs. The process takes about 10-15min, the OS will go through Android system update process again and the device will be reset to factory default state (don't forget to backup all your data). During the initial setup process don't restore your online account backup, make clean setup. Test the screen and digitizer before installing any 3rd party apps. Make sure your screen protector (if you have one) is not bugging the digitizer. If you have the same issues, then it's definitely hardware related (screen/digitizer assembly or connecting ribbon cables).

Battery overheating tips

Soo I have a faulty battery on my Z3c and I do not have the time or money to replace it right now,and I would love to have a phone which wouldn't overheat and thermal throttle after watching a YouTube video and opening Snapchat.
As well because the battery overheated the back glass's adhesive has weakened and the glass unsticked so I use the phone with the battery exposed which actually did help a bit.
I do get better results when using "conservative" governor and at least trying to set the clock to 1500MHz(it maxes at 1500MHz for some time and then starts peaking at 2400MHz again). I also tried undervolting,didn't notice a difference unfortunately.
So now,what can I do to cool down the battery,because it is starting to get very very annoying. Maybe putting some aluminum plate over the battery(maybe a dumb suggestion,don't really know) or something like that? Thanks to anyone who helps in advance.

Mpdecision becoming re-enabled causes frequency's not to stick. I found using init.d to set kernel CPU settings and having Kernel Adiutor apply as normal again prevents issues.
See the last photo of my battery mod gallery for a thermal mod https://imgur.com/a/8Ceha. It still heats up, though taking longer to and a little less. You could also apply new CPU thermal paste, it wears out with age. Of two devices I've opened up one had no paste.
A metal back will dissipate heat better but will probably affect wireless signal. An interesting observation I've noticed is with the battery separated outside of the device the CPU tends to run a little hotter. As poor design as having a battery attached to the opposite side of a CPU acting as a heatsink is, it still does dissipate heat over more surface than without. More so I think with the battery removed there's not enough pressure against the back of the board to push the thermal contact flush with the front display body. With the back panel removed there's not enough pressure. With the air gap separation mod the extra ~1mm lets an external case create some pressure, getting better results than with an original glass back and hard plastic back case on top.
I never really ran my phone case-less so can't report differences there. However it should be noted that glass is an insulator and isn't good for dissipating heat.

Infy_AsiX said:
Mpdecision becoming re-enabled causes frequency's not to stick. I found using init.d to set kernel CPU settings and having Kernel Adiutor apply as normal again prevents issues.
See the last photo of my battery mod gallery for a thermal mod https://imgur.com/a/8Ceha. It still heats up, though taking longer to and a little less. You could also apply new CPU thermal paste, it wears out with age. Of two devices I've opened up one had no paste.
A metal back will dissipate heat better but will probably affect wireless signal. An interesting observation I've noticed is with the battery separated outside of the device the CPU tends to run a little hotter. As poor design as having a battery attached to the opposite side of a CPU acting as a heatsink is, it still does dissipate heat over more surface than without. More so I think with the battery removed there's not enough pressure against the back of the board to push the thermal contact flush with the front display body. With the back panel removed there's not enough pressure. With the air gap separation mod the extra ~1mm lets an external case create some pressure, getting better results than with an original glass back and hard plastic back case on top.
I never really ran my phone case-less so can't report differences there. However it should be noted that glass is an insulator and isn't good for dissipating heat.
Click to expand...
Click to collapse
Soo first the Mpdesicion thing,I have installed a new kernel which removes Mpdesicion and puts Intellithermal instead,I don't know if that affects anything with clock changes but we'll see. I am gonna switch to Oreo soon so we'll see how it is there.
Second,I will take the phone apart definitely when I get some time to do so. And for the third thing,no I am not really into modding cases and the insides of the phone and similar so I will be probably avoiding that.
Thanks for the help though.

Dinkec27 said:
Soo first the Mpdesicion thing,I have installed a new kernel which removes Mpdesicion and puts Intellithermal instead,I don't know if that affects anything with clock changes but we'll see. I am gonna switch to Oreo soon so we'll see how it is there.
Second,I will take the phone apart definitely when I get some time to do so. And for the third thing,no I am not really into modding cases and the insides of the phone and similar so I will be probably avoiding that.
Thanks for the help though.
Click to expand...
Click to collapse
Intellithermal is for thermal throttling. A hotplugging replacement for Mpdecision is something else.
So nothing is covering the battery? Be careful not to puncture it. A case doesn't require modding but I think some thickness is required to create pressure. In other words I think the back panel without a case is better than no back panel with just a case and no pressure modification.

Infy_AsiX said:
Intellithermal is for thermal throttling. A hotplugging replacement for Mpdecision is something else.
So nothing is covering the battery? Be careful not to puncture it. A case doesn't require modding but I think some thickness is required to create pressure. In other words I think the back panel without a case is better than no back panel with just a case and no pressure modification.
Click to expand...
Click to collapse
Okay I will try something today or tomorrow.
As for the Mpdecision,I turned it off and my clock still peaks at 2500MHz. You mentioned something with init.d.
Could you tell me what to do?

Dinkec27 said:
Okay I will try something today or tomorrow.
As for the Mpdecision,I turned it off and my clock still peaks at 2500MHz. You mentioned something with init.d.
Could you tell me what to do?
Click to expand...
Click to collapse
Your ROM needs to have init.d support. If it does there should be a folder in /system/etc/init.d/. This used to be easier to add on MM stock. Since N AOSP it seems to be disabled. I've got it working via a workaround on Magisk, it's not straightforward.
Maybe try enabling shell script to apply settings in Kernel Adiutor settings first. If that fails maybe search and ask to see how anyone else gets edited frequencies to stick in your kernel thread. If you still can't get a fix i'll recommend my ideas.

Infy_AsiX said:
Your ROM needs to have init.d support. If it does there should be a folder in /system/etc/init.d/. This used to be easier to add on MM stock. Since N AOSP it seems to be disabled. I've got it working via a workaround on Magisk, it's not straightforward.
Maybe try enabling shell script to apply settings in Kernel Adiutor settings first. If that fails maybe search and ask to see how anyone else gets edited frequencies to stick in your kernel thread. If you still can't get a fix i'll recommend my ideas.
Click to expand...
Click to collapse
So I did most of what you said,so first with Oreo it is actually much better with battery and heat management,but how do you now fix the volume down button when you tried to make the buttons go to place for 1 hour?

Dinkec27 said:
So I did most of what you said,so first with Oreo it is actually much better with battery and heat management,but how do you now fix the volume down button when you tried to make the buttons go to place for 1 hour?
Click to expand...
Click to collapse
So what have you done? Useful to know what's worked for you. Or do you mean Oreo is cooler by itself?
Do you mean your volume button is stuck? It shouldn't be. Check inside if it's aligned and properly placed. If you had removed the board try reinstalling it again taking care with button alignment.
Sent from my Z3 Compact using XDA Labs

Infy_AsiX said:
So what have you done? Useful to know what's worked for you. Or do you mean Oreo is cooler by itself?
Do you mean your volume button is stuck? It shouldn't be. Check inside if it's aligned and properly placed. If you had removed the board try reinstalling it again taking care with button alignment.
Click to expand...
Click to collapse
Nah button alignment is completely fine it just isn't registiring a key press,maybe I have damaged the flex cable or the board.
And what I have done is apply thermal paste,leave 1mm between the motherboard and the battery so it has some air to breathe and Oreo seems to be cooler itself.

You must disable Thermal Core Control for your settings to be applied, can do it with Kernel Adiutor

Well I managed to get a new battery and with new settings that I set on Oreo there is almost no heat sooo yeah,this thread can be closed.

I've changed screen and after sometimes phone goes crazy

Hi mates, I need you help and suggestons,
unfortunately my phone felt down and I needed to change screen, the service which installed it asked me to choose one of the available (chinese) screens I I select the most expensive one. In the beginning all was ok, but time by time (about 1,5months) the usage gests worst, when the screen start to be a bit dirty it start recognize touches anywhere (moslty in the up side of screen), itself does commands, it's not possible to do nothing. WHen this happens I need to keep press the power button for 10 seconds tille ht ephone reboots, after reboot all become regular.
My considerations:
1) it doesn't seams a defective screen or a bad assembly, because after reboot all is good, if there were such problems a simple reboot can't fix them.
2) it looks like an incompatibility between OS and the touchscreen firmware, and probably it's something Xiaomi does with intention to create problems for cloned spare parts. Maybe the OS is "instructing" the touch screen controller how much sensibility to use, how much it can be dirty, etc.etc? the protocol of the latest OS isn't at all compatible with the cloned device and it result on crash of functioning. A reboot solves the problem.
If that is right, will a ROM update to another OS (not IMOU, as I have now) can fix the problem? Or there is any app that can perform a touch screen reset? Or any other trick to solve my problem? Than you for answers

Hi mates I need help, with cold weather coming it got crazy as soon it feels cold. WHat can I do to solve problem?
Updating ROM to a non official can solve it? The display isn't broken! A reboot fixes always the problem..

It is not original screen from xiaomi vendors, just a oem part with lower quality (chinese sell it alot on aliexpress with many type amoled, oled and LCD panel too).
Ghost touch easy happen on oem screen no matter how expensive it is.

Thank you for your kind answer, this is a really big issue.. it's very annoying using the phone like that, I've noticed it suddelny starts when the phone is exposed to cold temperature: lowering the screen temperature quite suddenly means it goes crazy, when it's crazy the only way to fix the proble is reboot the phone, with reboot it calibrates again and works ok, till next event. MY question are:
1) Can I forse myself a calibration?
2) Does other ROMs, not MUI, manage and fix this problem? (using another touch driver may solve the problem, chances are MUI introduced updates and become more selective to work with only original displays, to disancurage the OEM parts, so using another ROM wuth an older driver may solve the problem)
3) If I buy and add a protective glass on display, does it behave better?
Your experience is essential for me, thank you for posting!

Barabba11 said:
Thank you for your kind answer, this is a really big issue.. it's very annoying using the phone like that, I've noticed it suddelny starts when the phone is exposed to cold temperature: lowering the screen temperature quite suddenly means it goes crazy, when it's crazy the only way to fix the proble is reboot the phone, with reboot it calibrates again and works ok, till next event. MY question are:
1) Can I forse myself a calibration?
2) Does other ROMs, not MUI, manage and fix this problem? (using another touch driver may solve the problem, chances are MUI introduced updates and become more selective to work with only original displays, to disancurage the OEM parts, so using another ROM wuth an older driver may solve the problem)
3) If I buy and add a protective glass on display, does it behave better?
Your experience is essential for me, thank you for posting!
Click to expand...
Click to collapse
imo
1. you can not
2. Roml sorfware can not
3. Protective glass make lower touch experience.
- Not all oem part come with defect, some working fine, it is just random.
- To repair you need replace new one, or buy original screen for sure.

Thanks for answer, I do believe that the problem can be managed by drivers, "resettig" the touch chip wil correct the problem. Probably the defect is on the firmware of the touch panel, it gots errors from touch.. ok, but it doesn't understand it's just revealing mre and more ghost touches. These FW have the task to filter out the ghost,, maybe they don't do it well.
A second chance is the comuinication between this chip and the MUI OS, the connection goes broken by some mistakes, "unalligned" and MUI got any touch position from nothing.
I don't believe the screen is defective, because after reboot it works perfectly, thil the next strong environment conditions change..
What is Roml software?