Database Users

Touch display serious problem!

Ho all,
I am having a serious problem with touch display alligning. It happened two times, on resuming it from stand by, touch screen lost its configuration. So that display becomes unusable becouse finger touch doesn't have a correct corrispondance. I had to restart device to have it working again.

Have you installed any custom ROMs? If not...
You'll want to contact HTC as this sounds like it may be a hardware issue. http://www.htc.com/www/support/nexusone/

kozm0naut said:
Have you installed any custom ROMs? If not...
You'll want to contact HTC as this sounds like it may be a hardware issue. http://www.htc.com/www/support/nexusone/
Click to expand...
Click to collapse
No, I still haven't rooted it. It's with stock rom. HW problem? I wish in a SW issue..

I've seen this issue crop up on my rooted N1 as well. A reboot fixes it, as does waiting it out. For some reason I seem to notice it happening when I'm in the browser. There's a thread here about it (which evidently I can't link to since I'm new). Check the second page of the general section, the subject is "touch screen issues".
Seems like a software issue to me, but who knows.

The first thing to do if you have these types of obvious software issues is a hard reset (Settings>Privacy>Factory Reset). If that doesn't work, then it's time to call HTC.

uansari1 said:
The first thing to do if you have these types of obvious software issues is a hard reset (Settings>Privacy>Factory Reset). If that doesn't work, then it's time to call HTC.
Click to expand...
Click to collapse
Thank you all! I found the post where this is being discussed.

This is an issue many people are experiencing on google support forums, in fact it is the second longest thread after the 3g issues. It has also finally been pinned. Here is the link: http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en#all
Anyone experiencing the same problem please post in that thread, the more people that post the more chance for google to acknowledge this and remedy.
BTW I also experince issues with the touch screen which happen quite randomly and can normally be cleared with a power on/off. When the screen goes bad the touch is no longer registered in the correct spot on the screen.

[Q] Knock on just stopped working?

I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.

GHII said:
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
Click to expand...
Click to collapse
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it

tiguy99 said:
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
Click to expand...
Click to collapse
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply

I'm having the same issue with knock on not working. i've wiped a few times and have flashed diferent roms but it wont turn the phone back on. i'm also having this strange issue where i cant pull the notification bar down.
EDIT: I figured it out. did you install TWRP Recovery? i did and mine was messed up. i flashed back to stock and re-rooted and everything works again. I'm not sure if TWRP is the reason since im on a t-mobile G2 but reflashing to stock definitely worked. also i think you have to do a reset after flashing rom because the changes wont take effect unless you do

GHII said:
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
Click to expand...
Click to collapse
Wow that's a relief, I'm having the same pull down issue too.. Even scrolling here is a dead spot on the screen if I'm scrolling a page or list as I get in that area it "slows". I thought my digitizer was going bad. I found my knock on works but I have to do it extremely slow... Tap... Pause 1-2...tap.
Edit yes to twrp.
Sent from my VS980 4G using xda app-developers app

well i re-rooted and it doesnt work anymore. i deleted stuff so i need to see if its something that is being removed that causes it to not work

I just flashed the stock rom back..shows unrooted again, and it is still doing the same thing. Im still under my 30 days, Im going to return it, hope for the Nexus 5 on verizon by the weekend and if not I guess buy a new G2.

mine still says rooted so i'm kinda screwed right now

Same issue
Same thing with my T Mo G2. Using Nova launcher. Knock on worked flawlessly since new, about 2 months,use Nova gesture for knock off. Suddenly knock on stopped working. Too bad, because I like the feature, got used to using it. Did a restore and wipe using TWRP, kept root access, but still no knock on. Next I'll try going back to stock ROM, but I'd rather go an easier route. Has anyone successfully restored knock on?

Hi i have a dead spot somewhere app in the screen and when i pull down the notification bar it doesnt goind down.Also i tryed to draw with quick memo and i can see that it is a dead spot somewhere near the top of the screen
Does anyone has the probleme and have you fixed it

The only solution is returning the phone

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped

rastigo said:
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
Click to expand...
Click to collapse
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
ankurcshah said:
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
Click to expand...
Click to collapse
I read the following posts on some other forum...so essentially its a hardware issue....try stock jb rom kdz, then factory reset and reboot. If this helps solve the problem you are lucky. If not, try getting your phone replaced with 802 model. That is practically most stable with a lot of devlopment and tons of ROMS stable and working.
I will still keep looking for a solution and let you know consulting a few senior xda devs I know... sorry man, it hurts to see a fellow indian in distress.....:crying:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
That's odd, I have not seen much on this... if running stock
Quote:
Originally Posted by Burkettacb View Post
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Or againg, a ROM you may be using.
More detail would be helpful

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
Good luck with that if the phone is a D800. I took my G2 to the local AT&T store just a couple of hours ago with the same "no knock on" bug. But the sales person (who had bad breath) told me that because there was another way to get the phone to function (the back button), they won't even look at it. The fact that the knock off/on feature was a MAJOR selling point when the phone was released is apparently irrelevant.

He has a ls980 so it might not be the same for him. He can ask for a replacement
Sent from my LG-D802 using XDA Premium 4 mobile app

This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us

Andrew_han said:
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Click to expand...
Click to collapse
Did you try the "Hidden Menu" "Touch firmware update" option? I had this issue and it got fixed with it.
try 3845#*modelnumber# eg: 3845#*800# change model number 800 with your phones model number, then tap on "Settings" and scroll down to "Update Touch Firmware"
I have a few more suggestions to make it work, let me know how it goes.

Galaxy S5 black screen upon wake up

Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?

snazer said:
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
Click to expand...
Click to collapse
I would reflash the stock rom you have atm and data factory reset afterwards or try a data factory reset first and see if that fixes your issue.

Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
.

gee2012 said:
I would reflash the stock rom you have atm and data factory reset afterwards or try a data factory reset first and see if that fixes your issue.
Click to expand...
Click to collapse
I have tried factory resetting my phone but it doesnt help. Thanks anyways
fffft said:
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
I have added mot.proximity.delay=0 but i couldnt find ro.lge.proximity.delay=25. Is there any other way to fix this problem. I have to pull my battery out couple of times a day and its starting to get to me.
.
Click to expand...
Click to collapse

and now my mulitasking buttons are not working. any idea why?

snazer said:
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
Click to expand...
Click to collapse
I have the same issue... do you still get this issue? For me, sometimes, the screen does not wake up only the capacitive keys... I have to press the power button again to turn it off and then press power again to turn it on.

me too
Hi,
I'm having the same problem.
It was intermittent for a short while and a battery pull would fix it, now it's permanent.
I get capacitive buttons, I can boot into recovery or download.
I can hear touches on the screen and the annoying at$t boot sound is back since I used Odin to reflash to stock.
I think I have to take this phone to a service center and see if they will exchange it.
I'm worried that there may be traces of towelroot but from the thread that provides stock firmware and instructions for Odin it would seem that I'm good.
Has anyone had any luck with this issue or have any other tips to try?
I'm bummed because I just applied a glass protector and it looks like I'll have to get another.
Not to mention having to drive to the center.
Thanks.

With the new 1.100 motherboard version the problem is solved. It's a hardware defect. Maybe it will be fixed in next fw versions with some voltage or timing setting changes but a mobo change will definitely solve it.

For the record:
The at$t service center reflashed my phone and the screen works again.
IDK why flashing stock with odin did not work for me.
I can see from the post above mine that the problem might come back, I'll insist on a replacement if it does.

still getting the issue but for me I just need to press power 3 times for it to wake up; no need to remove battery
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
Levus said:
With the new 1.100 motherboard version the problem is solved. It's a hardware defect. Maybe it will be fixed in next fw versions with some voltage or timing setting changes but a mobo change will definitely solve it.
Click to expand...
Click to collapse
how can i find out what mobo I have?
---------- Post added at 06:51 PM ---------- Previous post was at 06:05 PM ----------
fffft said:
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
.
Click to expand...
Click to collapse
just rooted going to try this one thx

You can use the samsung phone info app from the market...

I haven't solved this issue as well... Please,did anyone of u guys solve this problem? If u did,please,tell me what to do... My screen stays black,only capacitive buttons lights,and I must press power button 5,6 times to wake up the screen. It's really annoying... :/

No solutions yet ???? I have this problem too...

walidhiphop said:
No solutions yet ???? I have this problem too...
Click to expand...
Click to collapse
It is lollipop 5.0 memory leak bug!
Also on CM12 (based on lollipop 5.0.2) problem occurs sometimes.

qubbus said:
It is lollipop 5.0 memory leak bug!
Also on CM12 (based on lollipop 5.0.2) problem occurs sometimes.
Click to expand...
Click to collapse
I'm having issue even using Kitkat 4.4.2

ZaKaTRoN said:
I'm having issue even using Kitkat 4.4.2
Click to expand...
Click to collapse
I also have the same problem, after lots of struggling I found little solution (it worked for me...), Just disable ur S-Health App, this app cause blank screen issue(this app uses sensors). Respond here if it worked for you.

knightrider558 said:
I also have the same problem, after lots of struggling I found little solution (it worked for me...), Just disable ur S-Health App, this app cause blank screen issue(this app uses sensors). Respond here if it worked for you.
Click to expand...
Click to collapse
Thanks for your reply, but it didn't work.
No problem, tomorrow i'm buying s6, Phone House give me 210€ for my s5.

ZaKaTRoN said:
Thanks for your reply, but it didn't work.
No problem, tomorrow i'm buying s6, Phone House give me 210€ for my s5.
Click to expand...
Click to collapse
Great decision just get rid of these sam devices -_- , last try did you change the runtime system?

knightrider558 said:
Great decision just get rid of these sam devices -_- , last try did you change the runtime system?
Click to expand...
Click to collapse
I have upgrade every new software phe (spain), even lastest btu (united kingdom) because is newer than phe.
Also i sent twice to technical service.
One more time... I hate my s5!!!, hehe.

ZaKaTRoN said:
I have upgrade every new software phe (spain), even lastest btu (united kingdom) because is newer than phe.
Also i sent twice to technical service.
One more time... I hate my s5!!!, hehe.
Click to expand...
Click to collapse
hahah... but this solution worked for me

[Q] phone does not wake up

Sometimes, when i try to wakeup my phone using home or power button, the capacitive keys light up but the screen is black.. I have to press power button to "sleep" and wake it up again... any idea? It was like this since I got it.... I updated recently and the problem still persists... it's not a big deal but a bit annoying at times.

..

yeahman45 said:
Sometimes, when i try to wakeup my phone using home or power button, the capacitive keys light up but the screen is black.. I have to press power button to "sleep" and wake it up again... any idea? It was like this since I got it.... I updated recently and the problem still persists... it's not a big deal but a bit annoying at times.
Click to expand...
Click to collapse
It may be due to firmware bug or some installed app.
You didn't tell what rom you are using (stock or custom). And also check for installed apps that you suspect.

vndnguyen said:
It may be due to firmware bug or some installed app.
You didn't tell what rom you are using (stock or custom). And also check for installed apps that you suspect.
Click to expand...
Click to collapse
It's a hardware defect. Mine was like this too since 11th april. After changing the motherboard to the newer, 1.1100 version, the problem is competeley gone away. It's waking up every time correctly.
We had a topic about this earlier...

Hardware defect? Are you sure? I dont have a warranty. Bought it abroad. I was hoping it was just a software glitch. I am on stock unrooted

yeahman45 said:
Hardware defect? Are you sure? I dont have a warranty. Bought it abroad. I was hoping it was just a software glitch. I am on stock unrooted
Click to expand...
Click to collapse
I'm totally sure because i had this bug from the beginning. I was trying all firmware updates, factory reset, etc. It's not related to the fingerprint sensor or any app installed or not.

Ok i have no choice. Will try the solutions i read from google, seems to he a common issue

yeahman45 said:
Ok i have no choice. Will try the solutions i read from google, seems to he a common issue
Click to expand...
Click to collapse
All i can say is that the old motherboard was 0.800 according to the phone info app, and the new one is 1.100 .

Levus said:
All i can say is that the old motherboard was 0.800 according to the phone info app, and the new one is 1.100 .
Click to expand...
Click to collapse
anyone else can confirm it's a hardware issue? does it get worse with time? I still get it (but seems worse sometimes, where i need to press power button several times to wake it up) and i have tried a lot of suggestions

anyone with a non-touchwiz rom have this problem? maybe it is related with touchwiz?

yeahman45 said:
anyone with a non-touchwiz rom have this problem? maybe it is related with touchwiz?
Click to expand...
Click to collapse
anyone can report if it also happens with a non touchwiz rom?? I can't flash one as my phone is still under warranty

no one can't reply? so this issue is not common after all?

guys i am going to void my warranty to flash cm12... does it solve this issue??

adit said:
Re-activation lock only works when knox is 0x0 but that too can be bypassed by installing custom rom so...
Click to expand...
Click to collapse
I can not install custom in my own phone ...0x1...after install xtrolite 2.2....f...

Have someone solved the problem by flashing a custom kernel? Still getting the issue on latest lollipop rom

Audio Bug -During calls with latest lock screen update

I guess many of us have been stuck up with issues where during calls people are not able to hear voice from either side in last couple of days.
Reading playstore reviews of "HTC lock screen" it looks like its HTC who goofed up, lot of people have reported this regression issue.
BTW uninstalling this update did not even solve the issue.
This is just FYI to help folks who are not yet affected.
https://play.google.com/store/apps/details?id=com.htc.lockscreen&hl=en

i called HTC after reading this and they told me that there was no reports of this. I suggested checking out the reviews on the play store. No resolution offered though

Hello
My wife has exactly the same problem with her HTC One !
Any workaround someone ??
I asked her to uninstall the HTC lockscreen update but she says it did not help.
Will we have to re-install ROM ?
Hope HTC will correct this really ugly bug.

LeGrosMario said:
Hello
My wife has exactly the same problem with her HTC One !
Any workaround someone ??
I asked her to uninstall the HTC lockscreen update but she says it did not help.
Will we have to re-install ROM ?
Hope HTC will correct this really ugly bug.
Click to expand...
Click to collapse
Well when I posted it , it looked to me a lockscreen bug(may be its not , i am really not sure).. Some people on play store also said that its a problem with HTC service pack (check out its reviews)
Annoyed and reading more figured out that lot of people said that freezing google play services helped them.
Would suggest you check this thread
http://forum.xda-developers.com/htc-one/help/wip-sound-block-auto-update-play-t2969715
Hope this helps.

LeGrosMario said:
Hello
My wife has exactly the same problem with her HTC One !
Any workaround someone ??
I asked her to uninstall the HTC lockscreen update but she says it did not help.
Will we have to re-install ROM ?
Hope HTC will correct this really ugly bug.
Click to expand...
Click to collapse
Update to the latest Google play services with this version, released yesterday https://play.google.com/store/apps/details?id=com.google.android.gms. Or download apk from here http://www.apkmirror.com/apk/google.../google-play-services-6-5-99-1642632-038-apk/ Problem is solved for me. Also clear cache and data for Google Play Services and Google Play Services Framework.

Every time I get this issue,I used to put the phone on Airplane mode and restart it once or twice
Problem got solved for me

The audio bug from installing an update is new to me but I've uninstalled all new updates weather service pack clock etc due to weather not updating and battery drain issues. As far as audio bug where no one can hear you properly this has been a known issue from the phone being launched and relates to noise cancelling microphone on back of phone. My phone is like this all the time but will try anything to get it working again instead of covering mic on back.
Sent from my Nexus 7 using xda premium

The issue is not just on HTC. It is affecting people with Xiaomi and Nexus phones, at least.
This thread on Nexus 4 seems to be the most up-to-date.
http://forum.xda-developers.com/nexus-4/help/audio-call-nexus-4-cm11-t2924589/page3

For everybody who is experiencing no audio/voice during calls HTC is sending OTA's. I'm not experiencing any problem because I've already updated to 6.09.401.11. And the fix was included in it. <br />
For more info, see this venom rom thread. http://venomroms.com/venomhub-fix-no-sound-calls-htc-one-m7/<br/>

abdulwakil said:
For everybody who is experiencing no audio/voice during calls HTC is sending OTA's. I'm not experiencing any problem because I've already updated to 6.09.401.11. And the fix was included in it. <br />
For more info, see this venom rom thread. http://venomroms.com/venomhub-fix-no-sound-calls-htc-one-m7/<br/>
Click to expand...
Click to collapse
Your lucky I've got this update and its still broke tested the microphones and there working. Having been looking around it seems to be affecting m8 and m8 mini 2 as well. I think this problem has something to do with Qualcomm as its there tech that's used for noise cancellation or whatever it is that's not working properly anyway won't be getting another HTC until this has been fixed I think a known problem that was addressed on m7 then continued on too two other handsets just isn't on.
Sent from my Nexus 7 using xda premium

cokey77 said:
Your lucky I've got this update and its still broke tested the microphones and there working. Having been looking around it seems to be affecting m8 and m8 mini 2 as well. I think this problem has something to do with Qualcomm as its there tech that's used for noise cancellation or whatever it is that's not working properly anyway won't be getting another HTC until this has been fixed I think a known problem that was addressed on m7 then continued on too two other handsets just isn't on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
The 6.09.401.11 update must fix this issue. If your phone is stock/non rooted, update your phone, if problem still occurs go into bootloader, select recovery, wait until a red warning sign or triangle appears on the screen (takes a while) then press volume up and the power button. That will take you to the recovery menu. There select wipe cache partition. That might fix your problem.

Yes I am fully stock but this problem has been there since i have had the phone and this is the third handset it has done this on so wiping cache isn't going to do it even though I have done this already I am just unlucky. However there should be more information on this from HTC but there isn't and there isn't any real fix which is annoying will just have to wait until my next phone so I can be heard properly
Sent from my Nexus 7 using xda prem