Database Info

[Q] Samsung Galaxy SL i9003 screen unresponsive

the touchscreen of my samsung galaxy SL i9003 stops responding about 5 seconds after i unlock the screen.
I have done factory reset but problem still persists. Please help.

PTMensah said:
the touchscreen of my samsung galaxy SL i9003 stops responding about 5 seconds after i unlock the screen.
I have done factory reset but problem still persists. Please help.
Click to expand...
Click to collapse
Is your phone in warranty?

can you give us some basic information? such like rom & kernel version, wether you rooted and ade using cputuningtools or something like that.
if you are under stock rom(original samsung & all further updates over kies) and u have done nothing unnormally so far i would recommend use the warranty too; )
Sent from my GT-I9003 using XDA

thanks guys
i have not rooted or changed the stock rom
i only factory reset it when the problem started
i just discovered that when i plug in the charger the touch screen works normally but does not respond to touch when not charging

PTMensah said:
thanks guys
i have not rooted or changed the stock rom
i only factory reset it when the problem started
i just discovered that when i plug in the charger the touch screen works normally but does not respond to touch when not charging
Click to expand...
Click to collapse
I had the same issue. I got my touch panel replaced by the Samsung guys. That's why I was asking whether your phone is under warranty or not.
Sent from my SIII looking SL
....
...
I'm more on XDA than FB...

Here we go, this proves this has nothing to with CM9, this guy is on stock.
Many people are blaming CM9 for this and claiming it caused the problem.
It's a hardware defect.

Skander1998 said:
Here we go, this proves this has nothing to with CM9, this guy is on stock.
Many people are blaming CM9 for this and claiming it caused the problem.
It's a hardware defect.
Click to expand...
Click to collapse
Agree. :good:
I'll wait for a few weeks or till the phone is usable for the kernel 3.0. :fingers-crossed:
If not then no other option but create a Rs.5000 hole in my pocket. :crying:

Same case with me... Bought the i9003 March 2011.
I'm on DDKP3 and around the same time as the OP, my touchscreen started to act strange... responsive only when charger is plugged in. Tried factory reset, but problem came back after some hours!
If this is a product-wide issue, then I guess sammy should replace it for free, even if it's out of warranty... too busy to go to the nearest service cenrter, will check later.
Till then, please keep me updated how it goes for you.
---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------
Just wondering, if a reflash of DDKP3 via ODIN or any custom ROM would solve the issue... please suggest.

I guess the sensitivity settings (or something like that) has changed without you knowing. Don't know if it is the same as s2 but in s2, sensitivity of the phone not plugged in the charger and plugged in has different settings. So maybe the settings for it in your case (unplugged) has changed but not on the plugged in settings. It's all in the kernel btw.
Sent from my GT-I9100 using xda premium

^^^ So what do you suggest?

agnivo007 said:
^^^ So what do you suggest?
Click to expand...
Click to collapse
Maybe asking a kernel dev if the values changed or what not. If i'm correct then it's a software problem, if not then maybe a hardware problem.
Sent from my GT-I9100 using xda premium

Same problem!!!
It happened last week when my phone surprisingly started showing this problem. After unlocking the phone the screen becomes unresponsive. In my case it is just 1-2 secs after unlocking the phone.
It lasted for a day, I tried flashing different ROMs. I was on XXKPE when it happened. And than suddenly my phone started working fine until yesterday when this thing again happened and the problem still persists (I am still on KPE). I dont know what to do.
I think it can be some software problem as the screen and touch keys do work for some time before becoming unresponsive and even the logcat shows no problems for the touch screen. I am going to try more ROMs now. Will keep you posted.

Possible solution !!!
Friends, I think I found a possible solution for this issue. Though it seems to work for me... I have to keep the phone under observation for some days until I can say it's the final solution.
A similar thread: http://forum.xda-developers.com/showthread.php?t=1695149
The possible cause for the touch screen going unresponsive seems not to be a hardware/software glitch; but environmental issue! And it doesn't depend on the ROM your'e running.
I noticed that most people from India having this issue say that this problem started in June, when the rainy season starts and it gets humid and damp.
In fact my phone showed this issue when it had rained for the last 2 days and it was very damp and humid inside the house.
You can do the following:
1. Take out the back cover, memory card, SIM and battery.
2. Place the backside of the phone near a hot air source (on top of a running CRT TV/monitor, hairdryer, laptop fan vent) for sometime.
3. Reassemble and check if the problem has gone away.
Do not panic if the handset gets a bit hot in the process!
In my case, I left it on the top grille of a CRT TV for a day which ran for 8hrs.
Do let me know if this works for you...

Flashing the ROM does not solve the problem
neetinnagap said:
It happened last week when my phone surprisingly started showing this problem. After unlocking the phone the screen becomes unresponsive. In my case it is just 1-2 secs after unlocking the phone.
It lasted for a day, I tried flashing different ROMs. I was on XXKPE when it happened. And than suddenly my phone started working fine until yesterday when this thing again happened and the problem still persists (I am still on KPE). I dont know what to do.
I think it can be some software problem as the screen and touch keys do work for some time before becoming unresponsive and even the logcat shows no problems for the touch screen. I am going to try more ROMs now. Will keep you posted.
Click to expand...
Click to collapse
I've sent the phone to the samsung guys who have flashed the phone twice but the problem still persists.

PLs keep us updated
agnivo007 said:
Friends, I think I found a possible solution for this issue. Though it seems to work for me... I have to keep the phone under observation for some days until I can say it's the final solution.
A similar thread: http://forum.xda-developers.com/showthread.php?t=1695149
The possible cause for the touch screen going unresponsive seems not to be a hardware/software glitch; but environmental issue! And it doesn't depend on the ROM your'e running.
I noticed that most people from India having this issue say that this problem started in June, when the rainy season starts and it gets humid and damp.
In fact my phone showed this issue when it had rained for the last 2 days and it was very damp and humid inside the house.
You can do the following:
1. Take out the back cover, memory card, SIM and battery.
2. Place the backside of the phone near a hot air source (on top of a running CRT TV/monitor, hairdryer, laptop fan vent) for sometime.
3. Reassemble and check if the problem has gone away.
Do not panic if the handset gets a bit hot in the process!
In my case, I left it on the top grille of a CRT TV for a day which ran for 8hrs.
Do let me know if this works for you...
Click to expand...
Click to collapse
Thanks.
Pls keep us updated

Problem Solved!!
Thanks to agnivo007.
I guess the climate is the only reason. I used his method to heat up my phone a little bit by charging it enough. Than it started working fine. No problems since then. Lets see.

ephraim033 said:
I guess the sensitivity settings (or something like that) has changed without you knowing. Don't know if it is the same as s2 but in s2, sensitivity of the phone not plugged in the charger and plugged in has different settings. So maybe the settings for it in your case (unplugged) has changed but not on the plugged in settings. It's all in the kernel btw.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
But changing the panel solves the issue..
The kernel won't reset itself if you change the screen.

Skander1998 said:
But changing the panel solves the issue..
The kernel won't reset itself if you change the screen.
Click to expand...
Click to collapse
ephraim033 said:
Maybe asking a kernel dev if the values changed or what not. If i'm correct then it's a software problem, if not then maybe a hardware problem.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Sent from my GT-I9100 using xda premium

Touch Screen non-responsive Problem
I had the same issue and when i dismantlement the thing, came across a small batter. could this be the reason? Cos while charging this battery is not used but when running with battery, this small dry typed batter can be in use.

Found Any Solution
Could any 1 find a solution for this matter?
If so pls. update. Mine is still there.
I can't get rid of it.

Messed-Up Display

Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.

Saad S. said:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Click to expand...
Click to collapse
Has this happened after you flashed a rom or.. ??

semirr said:
Has this happened after you flashed a rom or.. ??
Click to expand...
Click to collapse
Yes after I flashed the rom but not directly after. But after a good 1 month.

Saad S. said:
Yes after I flashed the rom but not directly after. But after a good 1 month.
Click to expand...
Click to collapse
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.

semirr said:
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
Click to expand...
Click to collapse
Is it possible that a driver update could fix this, if so then how?

Saad S. said:
Is it possible that a driver update could fix this, if so then how?
Click to expand...
Click to collapse
Hmm i dont think that a driver could be the problem. And if it is i dont know how you could fix it Google it

I hate to be the bringer of bad news - but your screen is toast. Fortunately you can replace the touch and display components all at once.
http://www.amazon.com/Skiliwah-Digitizer-Assembly-Google-nexus5/dp/B00HN0U168
Here is what you need to perform the repairs - and here are the procedures for disassembly.
https://www.ifixit.com/Teardown/Disassembling+Nexus+5+Display+Teardown+-+liquid+damage/32410
Trust me, it's not that difficult. Unfortunately, it's a bit pricey ($60 for the screen and digitizer), nevertheless much cheaper than a new device or sending your device in for repairs.

Rma

Problem Solved
The screen isn't toast, neither is the digitizer. I have 2 of these phones. The parts which cause problems like this are the main board and the ribbon with the USB connector on it, which also attaches the screen & digitizer to the main board. One was showing lines exactly like this, & also no touch. I put a replacement main board in. Works great now. The other, wouldn't even turn on. I put the main board from the first phone in the second one, it still wouldn't turn on. I replaced the ribbon cable, it turns on and perfectly replicates the issue from the first phone. So now, I have one fully functioning LG Nexus 5, and another which turns on with the same problem as yours. This is good, I started out with 2 of them that were useless to me. So, it appears that your display and touch issues are caused solely by a bad main board. A replacement main board costs somewhere around $75. After swapping stuff around, I have 2 bad main boards, 1 bad USB ribbon & 1 working phone of 2. Not bad, not bad at all.

Digitizer not responsive sometimes

My U11 is having problems recognizing touches. The digitizer itself is fine when I check with testing apps or the developer options. However in normal everyday use, I find myself having to repeat actions quite often, maybe once every 20 touches. It's not really consistent... sometimes it's like the phone expects you to be REALLY precise when tapping a button or text label. In other cases light touches are not recognized until I try a 2nd time. And sometimes I try to open the navigation drawer by swiping from the left edge of the screen and again I have to try a second time.
The phone works perfect if I am really careful when using the screen, but in my previous HTC phones (M8, 10) using the screen was completely effortless so this is a bit odd.
Anyone experiencing something similar?

I've noticed the same thing. thought it was me. I get it sometimes moving icons around and other times. I'll keep track of when and how and report.

I may be able to test with a 2nd unit in a few days, I'll see if I get the same issues.
It does feel like a software calibration issue rather than a hardware one though. I have the "show taps" option enabled in dev tools now and the taps are definitely being registered, it's just that the actions are sometimes not triggered.

Same here. Sometimes have to tap 2 or 3 times.
Sent from my SM-G950U using Tapatalk

The same problem here
Odesláno z mého Pixel C pomocí Tapatalk

I have the same problem; most prominent when my hands are too dry, and worst at navigation buttons under the screen. Maybe use the glove mode?

Just updating the thread to say that the phone is now working a lot better. I still get the odd tap that is not recognized but it's not nearly as common as it used to be, the phone is perfectly usable most of the time now.
Not sure what changed, I came from a M8 so maybe it was just a matter of getting used to the new size of the device (the way you type does change quite a bit with these larger screens), or maybe there were improvements in the software, I went from 1.03 to 1.13 a few days ago.

Same issue on 2 household U11

I just got the phone about 2 hours ago. I agree sometimes touches don't register. Very annoying.
Sent from my HTC U11 using XDA-Developers Legacy app

Same here as well, thought I was losing my mind. Also I can be typing something and it will trigger the pull down notification tray up top, weird. But it's very inconsistent. I don't recall seeing this before the latest update.
Sent from my SM-G955U using XDA-Developers Legacy app

Same for me, hopefully some update will fix it.

I don't think an update will fix this. The issue was so bad I asked for a replacement. Unfortunately, it will take over week to get a replacement. HTC Customer Service takes forever to respond, then shipping phone back, and then getting replacement.
Sent from my G8142 using XDA-Developers Legacy app

martinezma99 said:
I don't think an update will fix this. The issue was so bad I asked for a replacement. Unfortunately, it will take over week to get a replacement. HTC Customer Service takes forever to respond, then shipping phone back, and then getting replacement.
Click to expand...
Click to collapse
Well I don't think a replacement will fix it either then.

My second unit has the same problem so I would say replacement is not a solution. I hope they can fix it by some SW update.

Same problem here. I just did a factory reset last night to fix a different issue though so I'll see if it's still happening.

Have also touch issues and will now repair this from HTC.

techboy10 said:
Same problem here. I just did a factory reset last night to fix a different issue though so I'll see if it's still happening.
Click to expand...
Click to collapse
I was going to hard reset this morning as well but didn't feel like setting everything back up so I will deal with it for now. But if it fixes the problem then I will for sure. So let us know how it goes for you.

techboy10 said:
Same problem here. I just did a factory reset last night to fix a different issue though so I'll see if it's still happening.
Click to expand...
Click to collapse
Any improvements since the hard reset?

themuffinman said:
Any improvements since the hard reset?
Click to expand...
Click to collapse
Maybe a little bit. Seems to be less frequent now but I still notice it every once in a while. Really weird/annoying.

techboy10 said:
Maybe a little bit. Seems to be less frequent now but I still notice it every once in a while. Really weird/annoying.
Click to expand...
Click to collapse
Are you using a screen protector?

SOD (sleep of death)

I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?

60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.

Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.

60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.

Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.

60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.

Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.

60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?

Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.

60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!

to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?

Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.

I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...

Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.

60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!

well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...

No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg

60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?

I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem

a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.

P30 fingerprint picture showing up often

When my P30 is placed on the table (I don't notice when in my pocket, duh ) it lights up the "Place finger here" in the bottom.
Does anyone have an idea why that happens?
It's not like the table is moving or anything to trigger a read, so why is it showing?
Could it result in burn-in?

I have same problem, it could result in burning, but i have no idea why it shows up

It is annoying! I've turned it off in favor of a PIN to prevent burn-in

I wrote and email to Huawei and the replied rhat IT shouldnt result in burn-in.
And if I didn't want to risk it, I could turnering it off.
Not really a valid answer...

ZigmaDK said:
I wrote and email to Huawei and the replied rhat IT shouldnt result in burn-in.
And if I didn't want to risk it, I could turnering it off.
Not really a valid answer...
Click to expand...
Click to collapse
I'm surprised their IT is not aware of the latest OTA from last night, which is version 9.1.0.124(C431E3R2P2) and fixed the problem. The annoying fingerprint symbol no longer randomly appears but only if I move my phone (and in the pocket it would not show as the proximity sensor prevents that from happening, which I have tested).

ifonuser78 said:
I'm surprised their IT is not aware of the latest OTA from last night, which is version 9.1.0.124(C431E3R2P2) and fixed the problem. The annoying fingerprint symbol no longer randomly appears but only if I move my phone (and in the pocket it would not show as the proximity sensor prevents that from happening, which I have tested).
Click to expand...
Click to collapse
That didn't solve it for me. It still shows up.
I still use the screen protector that was on the phone when I bought it. Did you remove yours?

ZigmaDK said:
That didn't solve it for me. It still shows up.
Click to expand...
Click to collapse
What's the interval like?
ZigmaDK said:
I still use the screen protector that was on the phone when I bought it. Did you remove yours?
Click to expand...
Click to collapse
I've kept it on. Normally I'm not the kind of guy who uses one, but this was placed on very well I still find the screen to be excellent, it does not bother me. Have you immediately pulled yours off or can you describe a before/after experience?

ifonuser78 said:
What's the interval like?
I've kept it on. Normally I'm not the kind of guy who uses one, but this was placed on very well I still find the screen to be excellent, it does not bother me. Have you immediately pulled yours off or can you describe a before/after experience?
Click to expand...
Click to collapse
I just tested at my desk and it came up 9 times in a minute.
I still have the protector on. Never removed it as it is placed nicely.

ZigmaDK said:
I just tested at my desk and it came up 9 times in a minute.
I still have the protector on. Never removed it as it is placed nicely.
Click to expand...
Click to collapse
I have version 9.1.0.124(C431E3R2P2) and this problem is solved. Fingerprint symbol shows up only when i move the phone.

I have 9.1.0.124(C431E4R2P2) and the symbol sporadically lights up for me as well

matjazzzz said:
I have version 9.1.0.124(C431E3R2P2) and this problem is solved. Fingerprint symbol shows up only when i move the phone.
Click to expand...
Click to collapse
Is that the standard P30 you have on .124? My P30 is on .113.
I have this issue too, the symbol shows up several times a minute. I have seen others mention elsewhere that this could well be a hardware issue?
I'd just assumed this was a software issue but if it is hardware then it may be time to return it?

arsenal74 said:
Is that the standard P30 you have on .124? My P30 is on .113.
I have this issue too, the symbol shows up several times a minute. I have seen others mention elsewhere that this could well be a hardware issue?
I'd just assumed this was a software issue but if it is hardware then it may be time to return it?
Click to expand...
Click to collapse
Yes, it's standard version... After I bought it (first day), phone was updated with this version ...
After I switch off the phone (and put it on the table), symbol shows up for a few seconds, then disappear until I move the phone ..
Maybe you should try first with .124 version .. ?

Hi
My p30 is on 115 update and still has the same problem

Anyone try without or with a different screen protector?

I have found some kind of solution, but by some reason it does not work all the time. Settings- Smart assistance- Shortcuts & gestures - wake screen - Double-tap screen to wake. Activate that option and reboot the device.
But as I can see, that light might be used as some kind of notification light since it blinks when there is something, like e-mail, message and other things that need attention. When there is no internet connection it is not blinking until you move it.
All of the above are just my personal observations and I don't insist that they are 100% correct.

Having this act as a notification indicator isn't a bad theory, although the frequency of it appearing seems wrong for that kind of use.
Personally, I'm bummed at the lack of notification light, something I had been relying on for years with all my previous phones. I might end up taking advantage of the OLED screen and just make it keep the screen on instead.
My phone updated from 111 to 121 today (I guess we have different build numbers in North America), I still see it flashing from time to time while it sits on my desk.

Update: I tried with a tempered glass screen protector and now it doesn't show up unannounced anymore.
I think it is an issue with sensitivity of the screen.