Database Info

Is there a ghost in my phone?[CASE SOLVED]

OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?

..

Sent from my sending thing.

I had the same problem. LG Service Center said, that they need to change the touchscreen. Try to flash another ROM, if you get the same problem, then unroot and flash stock firmware and go to LG Service Center or change the screen yourself
But I hope it's your ROM, good luck!

on my sgs i have this weird ghost while charging.. are you running ics?

sweettaniyaa said:
OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
Click to expand...
Click to collapse
this one was the best query I have ever read tania hope u are not watching fear files these days

sweettaniyaa said:
OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
Click to expand...
Click to collapse
It is surely a hardware problem i had the same problem. My screen had got damaged as it wud get wet regularly. I changed the touch screen and it is now as good as new
Running Ginger Snap v1.3 Best gaming rom ever

A developer told me that sometimes on some devices, it happens while charging, becaude of charger errors..

sweettaniyaa said:
OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
Click to expand...
Click to collapse
Change your kernel, these may be kernel panicks.
Sent from my LG-P500 using xda app-developers app

myawan said:
Change your kernel, these may be kernel panicks.
Click to expand...
Click to collapse
This could be a reason cause it all began when I flashed DJNoXD's Kernel 2.5.2. But then I re flashed the latest CM 7 nightly over it and it continued to show the symptom's. Also I did not over clock, never did.
Today when it showed the same possessed behavior, I pressed the power button and it at once came back to my control. So I guess its a temporary solution to it.
dafabsl said:
A developer told me that sometimes on some devices, it happens while charging, becaude of charger errors..
Click to expand...
Click to collapse
It never happened during charging.

Found the Culprit
It was being caused by a pair of external speakers, which has it own power source, which I connected to the phone. I am guessing the speaker was sending some kind of charge to the phone. When I connected the speaker, the touchscreen completely stopped working. and even after I disconnected the speaker the touchscreen would continue to behave the way I described in my first post. Probably stored that charge somewhere. Bottom line, now that I have stopped connecting the speakers its stopped that behavior. There case solved. Feel like Scooby Doo. There was no Ghost after all.

Lolzz..

[Q] [HELP] Phone suddenly freeze and show weird screen

Hi, I have been looking all over the internet and search the xda thread but I couldn't find anything related to my problem.
So this morning when I wake up, I turned on my phone and after I used it for awhile suddenly my phone stopped working (freeze/hang) and started to reboot itself. After it reboots my phone's screen as per attached below.
The problem lasted for a day and started to driving me nuts!
Anyone experienced same problem?
I am running KK4.4.2 fyki.
Thank you very much for your kind help!

are you unlocked, rooted, custom recovery, rom, kernel, anything? can you access the bootloader?

xBeerdroiDx said:
are you unlocked, rooted, custom recovery, rom, kernel, anything? can you access the bootloader?
Click to expand...
Click to collapse
Nope, I am all stock without any modification nor and fancy stuffs.
Just pure android 4.4.2
I am thinking that the hardware might be faulty..

hellyeahdykk said:
Nope, I am all stock without any modification nor and fancy stuffs.
Just pure android 4.4.2
I am thinking that the hardware might be faulty..
Click to expand...
Click to collapse
If you're stock, it could be hardware. Though have you ever attempted to root?
Is it just randomly happening?

Definitely hardware

teh roxxorz said:
If you're stock, it could be hardware. Though have you ever attempted to root?
Is it just randomly happening?
Click to expand...
Click to collapse
Yes, it just randomly happening. It started yesterday morning until now..
The phone started to not responding at all and then my screen goes broken (same screen as broken TV I might say).
If I let it cool for 15-20 minutes the phone is usable, but then after 1 hour of normal usage the phone started to freeze again.
Just curious, none of you experienced the same?

this kinda looks like the static i was getting on screen on my n7 2012 when i let the battery get too low. charging it up and a few reboots fixed it. but im not sure if that's what is going on with yours

hellyeahdykk said:
Yes, it just randomly happening. It started yesterday morning until now..
The phone started to not responding at all and then my screen goes broken (same screen as broken TV I might say).
If I let it cool for 15-20 minutes the phone is usable, but then after 1 hour of normal usage the phone started to freeze again.
Just curious, none of you experienced the same?
Click to expand...
Click to collapse
I just got mine, 32gb from the playstore, a few days ago, and nothing like that.
If it's happening when your device is hot | overheating, you may wana see if you get it replaced.

It happened to me once. The phone was with his screen off and when I try to turn it on that exact same screen came. But it just happened once, also I experienced random poweroffs and reboots. I did a factory reset and power off issues and freeze stops, but had one reboot once I start installing my apps. I think its a software issue but I'm not sure.
Sent from my Nexus 5 using Tapatalk

I'm glad (and kinda of sad) to know that I'm not the only one with this issue.
The problem started about two weeks after I bought mine(Telus). It's done this about 5 or 6 times,randomly.
I found that having someone call me will "unfreeze" the device and the screen gets back to normal.
The first couple times it happened, I was running stock 4.4.2. I since rooted it and installed Xpposed/GravityBox and I'm still getting the problem...
I think that I'll have to return it...

Idk if i need RMA the phone. Its a great phone and the reboot issues has stopped. What should i do?
Sent from my Nexus 5 using Tapatalk
Edited: Nevermind my phone have defective gpu. i will RMA it

Same problem
jakov.90 said:
Idk if i need RMA the phone. Its a great phone and the reboot issues has stopped. What should i do?
Sent from my Nexus 5 using Tapatalk
Edited: Nevermind my phone have defective gpu. i will RMA it
Click to expand...
Click to collapse
Hi, I have the exact same problem, I posted a video on youtube /watch?v=m0EkC_ak01g but I got to the same conclusion that it might be a GPU issue. So there is nothing I can do right?, the worst thing is Im in Argentina and LG dont take my warranty because I bought it in Germany. So there is absolutely nothing I can do?, I know how to avoid the flickering a little bit, when I hit "Ok Google" button it seems responsive and as long as I touch the screen it works (you can see it in the video) but as soon as I stop touching it, after 2-3 seconds it becomes unresponsive again, and when I say unresponsive Im saying the screen doesnt reflect what Im doing, I can still push the buttons and all. So Im not 100% sure its a GPU issue, but a software too. Thanks.

Oneplus one screen touching itself.

I have had my oneplus one for about a month now. And for the first time I dropped it. About 2 feet. And my friend kicked it about a foot to prevent it from hitting the tile and It landed on flat carpet. The phone has a small dent on the lower left corner and screen has 2 small scratches that I only can see in sunlight. So I've been using my phone and every once and awhile it will go insane and the touchscreen will move on its own and press things. I hope this isn't an issue cause of dropping it.. I have a warranty but have alot on this opo already. Is there a possibility it's software?

TeChNoC4AzY said:
I have had my oneplus one for about a month now. And for the first time I dropped it. About 2 feet. And my friend kicked it about a foot to prevent it from hitting the tile and It landed on flat carpet. The phone has a small dent on the lower left corner and screen has 2 small scratches that I only can see in sunlight. So I've been using my phone and every once and awhile it will go insane and the touchscreen will move on its own and press things. I hope this isn't an issue cause of dropping it.. I have a warranty but have alot on this opo already. Is there a possibility it's software?
Click to expand...
Click to collapse
The Touchscreen failure you have sounds a lot like the problem I had from time to time with mine (without dropping).
There are also other bugs with the screen:
- unresponsive screen (-> reboot fixes temporarily)
- weird behavior like you descrive (ghost touches)
- fast typing not getting recognised
These problems will be fixed with the next 2 OTAs (both in august).
Wait if the fixes do work for you. If not it has definatly something to do with the accident.

keileruno said:
The Touchscreen failure you have sounds a lot like the problem I had from time to time with mine (without dropping).
There are also other bugs with the screen:
- unresponsive screen (-> reboot fixes temporarily)
- weird behavior like you descrive (ghost touches)
- fast typing not getting recognised
These problems will be fixed with the next 2 OTAs (both in august).
Wait if the fixes do work for you. If not it has definatly something to do with the accident.
Click to expand...
Click to collapse
OTA Announced today. Change log has a fix for turning on in pocket, but not for the unresponsive screen.

Actually I have had similar behavior and I'm using slimkat 7 now. This morning I couldn't enter even pin code as my phone didn't allow some presses. Numbers 1,2,4&5 weren't registered at all. Same time I couldn't use pull-down menu as it bounced back up after 1cm pull. Also when trying use power menu all options were unable to register. I force shut down phone twice and still same thing. Then I just wiped whole screen with moist cloth. And problem solved.
So there was something invisible holding my screen like finger or something.
I have had similar incident couple times earlier. When writing or so on....
Sent from my Oneplus One via Tapatalk

keileruno said:
The Touchscreen failure you have sounds a lot like the problem I had from time to time with mine (without dropping).
There are also other bugs with the screen:
- unresponsive screen (-> reboot fixes temporarily)
- weird behavior like you descrive (ghost touches)
- fast typing not getting recognised
These problems will be fixed with the next 2 OTAs (both in august).
Wait if the fixes do work for you. If not it has definatly something to do with the accident.
Click to expand...
Click to collapse
How much longer do you think it will be before the new Ota releases.

TeChNoC4AzY said:
How much longer do you think it will be before the new Ota releases.
Click to expand...
Click to collapse
search the forum the ota is out if you know how to use adb sideload

The ghost touches lasted for 30 seconds today.. Anyone else having this to?

Yes it's annoying the crap out of me, seem to have the least amount of issue running slimkat with sensei kernel. Every other kernel seems to either leave the screen completely unresponsive a min after boot, or touch becoming increasingly less as time/process load increases. Really hope this issue is fixed soon.

Chris.fowler said:
Yes it's annoying the crap out of me, seem to have the least amount of issue running slimkat with sensei kernel. Every other kernel seems to either leave the screen completely unresponsive a min after boot, or touch becoming increasingly less as time/process load increases. Really hope this issue is fixed soon.
Click to expand...
Click to collapse
Best thing is to go back to the XNPH22R Kernel. For me it fixed the frozen screen completly.
http://forum.xda-developers.com/showthread.php?t=2780725
It won't work with 30O though. 25R is working with 22R Kernel.
All other kernels are not working very smooth for my device. The OTA fixing this issue is anounced for August. No releasedate has been set though.

Is that kernel compatible with an aosp ROM lime slim or am I going to have to put a cm ROM bck on the phone

Chris.fowler said:
Is that kernel compatible with an aosp ROM lime slim or am I going to have to put a cm ROM bck on the phone
Click to expand...
Click to collapse
CM 11S kernels are only for CM 11S. 22R is a CM 11S kernel.

My phone has been alright today. Except for afew freezes. But I Wana Stay with cyanogenmod 11s. I think it will be updated soon. I really can't wait for Android L. Will android L be with cyanogenmod as well?

Great now the middle of my screen us touch dead........ Ughh

Well now all seems fine.. But earlier screen in center was dead and phone was non stop Ghost touching... Even after restarts. Sigh. This update needs to release already....

Hello

playya said:
search the forum the ota is out if you know how to use adb sideload
Click to expand...
Click to collapse
It won't update itself?

It's a known issue.. Vote it on Jira!https://jira.cyanogenmod.org/browse/BACON-145

I'm about to throw my phone, this is VERY irritating.........

It keeps Ghost touching non stop. I should of never got one.

TeChNoC4AzY said:
It keeps Ghost touching non stop. I should of never got one.
Click to expand...
Click to collapse
Install the 22R OTA and Kernel.... then you can easily wait for the fix...

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.

Screen non-responsive when using Smart Display - Hardware or Software Issue?

Hi
Just got my U12+ today. I've noticed that quite often if I unlock the phone by fingerprint, it shows the home screen but the screen is totally unresponsive. I can't click/touch anything.
It remains unresponsive, even if the screen times out (1min later) and then I reunlock.
The only way to fix it is to use the power button to switch off the screen and then it will work immediately afterwards when I unlock.
I have done multiple restarts, and 1 hard reset and it is still happening.
Any thoughts on what is causing/how to fix?
UPDATE:
I've spent quite a few hours googling and testing different setting options, and the issue seems to only occur when "Smart Display" is turned on.
If the Smart Display is on (either motion or always on) gets engaged, if I then unlock via Fingerprint, it shows the home screen, but the touch screen is totally unresponsive. It doesn't register any taps/touches (I turned on Dev options).
Is this a hardware or software issue? Anyone else experience this?
Thanks

leginag said:
Hi
Just got my U12+ today. I've noticed that quite often if I unlock the phone by fingerprint, it shows the home screen but the screen is totally unresponsive. I can't click/touch anything.
It remains unresponsive, even if the screen times out (1min later) and then I reunlock.
The only way to fix it is to use the power button to switch off the screen and then it will work immediately afterwards when I unlock.
I have done multiple restarts, and 1 hard reset and it is still happening.
Any thoughts on what is causing/how to fix?
UPDATE:
I've spent quite a few hours googling and testing different setting options, and the issue seems to only occur when "Smart Display" is turned on.
If the Smart Display is on (either motion or always on) gets engaged, if I then unlock via Fingerprint, it shows the home screen, but the touch screen is totally unresponsive. It doesn't register any taps/touches (I turned on Dev options).
Is this a hardware or software issue? Anyone else experience this?
Thanks
Click to expand...
Click to collapse
Phone model and current software build.
Are you rooted? Any root based mods, kernel, room, etc.

Hi
Thanks
U12+ running 1.21.454.3
Totally stock. Only got the phone on Saturday.
Did one hard reset and issue still there.
In usage since my last update, it is 100% related to the Smart Display. Absolutely no issues when it is turned off. When I enable Smart Display, then it starts freezing again on unlock.

Hi,
I'm having the same problem too..
I got my set on the 15/09/18, Hong Kong Set.
Mine is currently on 1.25.708.3. But prior to the update, I am already having the same problem described by leginag.
I even tried to do a factory reset but the problem still surface. It will become unresponsive after waking up after a period of screen off (not sure how many minutes).
After turning off Smart Display ( thanks leginag!) , I'm able to use it flawlessly. I was about to unlock the bootloader and flash a custom rom though..
I think this problem is quite disruptive, especially when a call comes in, or when launching the camera app through the edge sense. I can only snap using the squeeze.
Nonetheless, I hope there are other alternatives to Smart Display though..

Hi, I've been having the same issue. Thanks for looking into it hopefully it gets fixed in the next update.

شیرخدا said:
Hi, I've been having the same issue. Thanks for looking into it hopefully it gets fixed in the next update.
Click to expand...
Click to collapse
I hope it does get fixed. I reported it to HTC and they said they would forward it to their engineers. That was 2+ weeks ago, and nothing else heard back.
Best thing for you to do may be to submit a support ticket to HTC. If everyone who has the issues sends it in, this will flag it with their engineers that it is a wider problem.
Could you let us know your model/firmware?

leginag said:
I hope it does get fixed. I reported it to HTC and they said they would forward it to their engineers. That was 2+ weeks ago, and nothing else heard back.
Best thing for you to do may be to submit a support ticket to HTC. If everyone who has the issues sends it in, this will flag it with their engineers that it is a wider problem.
Could you let us know your model/firmware?
Click to expand...
Click to collapse
I have contacted HTC and am awaiting a reply. My current software version is 1.25.708.3

Thanks.
Hoping this issue is software related. So far, only people with Asia models have reported it (only 3, but at least I'm not going crazy by myself!)
ASIA HK - x2
ASIA JP - x1

Got a response from HTC, saying it is a software issue and should be fixed in next update - around mid-October.
Today, I got information about that this issue will be solve by software update.
Moreover, it is arranged on around middle of October.
Click to expand...
Click to collapse

leginag said:
Got a response from HTC, saying it is a software issue and should be fixed in next update - around mid-October.
Click to expand...
Click to collapse
Thank you for this. I just got my u12+ and thought it was faulty.
Turned off smart display.

I'm having this problem as well, Asia HK.
Curious, is anyone also having problems with TWRP? I almost always get a nonresponsive screen when fastboot booting.

Just a heads up that the 1.30 update has fixed the issue for me.
Which is a relief. Not that I was missing using Smart Display, but just feel better not having an issues with my phone

Hi there,
I am using Asia HK and have the same problem with you.
But I still didnt receive any update patch for 1.30. May I ask which area did your phone belong to?

raymondlo88 said:
Hi there,
I am using Asia HK and have the same problem with you.
But I still didnt receive any update patch for 1.30. May I ask which area did your phone belong to?
Click to expand...
Click to collapse
Asia TW and Asia JP have already received the 1.30 update (I had to manually check for it though). Hopefully HK will be soon!

leginag said:
Just a heads up that the 1.30 update has fixed the issue for me.
Which is a relief. Not that I was missing using Smart Display, but just feel better not having an issues with my phone
Click to expand...
Click to collapse
I've had this issue twice, once on 1.25 and once on 1.30 so I do not think it is fixed yet but it has been very rare for me. Only twice since the phone launched but it is very inconvenient when it happens. I could only fix mine with a reboot.

Removing my original reply as I don't believe it relates to this bug after all!
(A Factory Reset sorted out my device, incidentally)