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.

Zte blade Randomly rebooting while making calls

Hello ,
I am facing a weired problem as my Blade aka San Francisco is rebooting randomly while making a call.This happens randomly a few times in a day .It has the stock android 2.1with all orange apps removed .
Some user are facing similar problems as reported in Modaco forum but there is no clue .
Is there any provision of checking system log files in Android ?
Any help will be highly appreciated .
With regards ,
Somak

I have the same problem. On stock rom with all range crap removed and now on Japanese Jellyfish as well.
However it is happening not while i am making calls but absolutely randomly.
Please help.

It could be your battery since more mA used during calls, flash stock to clear nand then test if still problem take back to provider and request exchange.
Sent from my BladeVillain using XDA App

Thanks stylez,
I have bought it from Ebay so replacement can be ruled out as I am in India .It also happens once or twice a day ,have to live with it
regards,
Somak

Are you using an overclocked kernal? If so step it down and see if that helps.

An interesting thing has happened .after I did a factory reset the problem has thankfully gone away .
I had loaded a ZEAM and also tried Go launcher after which the problem started .the rom is the standard oled orange rom with all the orange apps removed.
With regards ,
Somak

TO ANYONE WHO IS FACING THIS PROBLEM
I too have the same issue, my Blade restarts randomly (and only) when on call or when phone rings. This was happening with all 2.1 and 2.2 ROM. I did extensive research and it turned out that it was crashing DUE TO SIMULTANEOUS DATA+CALLING. It is easily reproducible, just run SpeedTest app on Blade and call on Blade from another cell at the same time while data access is going on.
I was really freaked out by the idea that why didn't they take care of this in kernel, but it turned out the be my provider. I tried the same test with 2 more providers and no crash! So I guess my provider might be internally sending some screwed up code to Blade. But anyways, I was happy to know that it was not my hardware's fault.
PS: you can try "Sanity" app which disables data access while on call, it was able to reduce the number of crashes for me, but not eliminate it.

gameSTICKER said:
TO ANYONE WHO IS FACING THIS PROBLEM
I too have the same issue, my Blade restarts randomly (and only) when on call or when phone rings. This was happening with all 2.1 and 2.2 ROM. I did extensive research and it turned out that it was crashing DUE TO SIMULTANEOUS DATA+CALLING. It is easily reproducible, just run SpeedTest app on Blade and call on Blade from another cell at the same time while data access is going on.
I was really freaked out by the idea that why didn't they take care of this in kernel, but it turned out the be my provider. I tried the same test with 2 more providers and no crash! So I guess my provider might be internally sending some screwed up code to Blade. But anyways, I was happy to know that it was not my hardware's fault.
PS: you can try "Sanity" app which disables data access while on call, it was able to reduce the number of crashes for me, but not eliminate it.
Click to expand...
Click to collapse
Thank you very much! That seems to be it.

gameSTICKER said:
TO ANYONE WHO IS FACING THIS PROBLEM
I too have the same issue, my Blade restarts randomly (and only) when on call or when phone rings. This was happening with all 2.1 and 2.2 ROM. I did extensive research and it turned out that it was crashing DUE TO SIMULTANEOUS DATA+CALLING. It is easily reproducible, just run SpeedTest app on Blade and call on Blade from another cell at the same time while data access is going on.
I was really freaked out by the idea that why didn't they take care of this in kernel, but it turned out the be my provider. I tried the same test with 2 more providers and no crash! So I guess my provider might be internally sending some screwed up code to Blade. But anyways, I was happy to know that it was not my hardware's fault.
PS: you can try "Sanity" app which disables data access while on call, it was able to reduce the number of crashes for me, but not eliminate it.
Click to expand...
Click to collapse
You wouldn't belive it but I had the same bug and I hope it's gone.
This saturday I moved my phone to Gen2 and since than phone didn't reboot while makeing/receiving calls and EDGE/GRS was on

I believe that occurs because the phone can't allocate enough resources for both the call and data so it just reboots instead.

I don't think so, as i know all phones under Android drop data session while calling, so this is nothing to do with enough resources.

so the solution would be to turn all Blades/SFs to Gen 2 ?

gloc33 said:
so the solution would be to turn all Blades/SFs to Gen 2 ?
Click to expand...
Click to collapse
at least for me it works

Screen blinks sometimes..

It seems that, almost randomly, you can see the screen blink on/off very very fast.
You can notice this especially on white colours.
Me and other 3 members of a greek forum (myphone.gr) have noticed this issue so far.
If this happens with your X5, please share your experience !
Perhaps we can fix it -if we find what triggers this

my u8800 has the same problem in Australia.
I think it is a backlight flicker.
Huawei told me in Email,we had never same problems yet.
and the shop where I bought 2weeks ago,couldn't feel this problem.so they told me to repair only,but to use much time to repair than I stay AUS.
Sent from my u8800 using XDA App

THANKS GOD, I never had this so far.. had it over a weak, never noticed it..

xeirwn said:
It seems that, almost randomly, you can see the screen blink on/off very very fast.
You can notice this especially on white colours.
Me and other 3 members of a greek forum (myphone.gr) have noticed this issue so far.
If this happens with your X5, please share your experience !
Perhaps we can fix it -if we find what triggers this
Click to expand...
Click to collapse
I think mine is not random. It will start flickering if the phone standby for a long time (a night). And it will stop after some usage, and will start again if you standby this phone for a long time.
BTW it's Indonesia B137.
Will bring it to service center ASAP. . And will let you know what the problem if they tell me.
Sorry for my bad English, hope you understand what I write.

The service center in my city is hopeless. Trying other ROM, and the problem is still there. So, I think this is hardware problem.

[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.

Soft touch buttons unresponsive

I have a Nexus 4 and I am on Android 4.4. I recently encountered the issue of my soft touch buttons (back, home, recent apps) being unresponsive, the rest of the screen works but my buttons don't respond to touch. I can still slide ip for Google now though.
I tried restarting my device and even upgraded to a newer build of 4.4, no luck.

R u on stock or custom rom? Try to flash stock rom from developer google site.. If nt solved thn go to lg service centr it seems touch problm
Sent from my Nexus 4 using XDA Premium 4 mobile app

parveen75 said:
R u on stock or custom rom? Try to flash stock rom from developer google site.. If nt solved thn go to lg service centr it seems touch problm
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After some digging, there's a whole Google products forum post on this issue. It's disgusting that Google won't acknowledge it, looks like it's a hardware issue associated with overheating and the 4.4.2 update.
Temporary solution is to use another soft keys app, but I'll have to ditch this phone ASAP, I'm out of warranty and Google will not fix something they caused.

soulcedric said:
After some digging, there's a whole Google products forum post on this issue. It's disgusting that Google won't acknowledge it, looks like it's a hardware issue associated with overheating and the 4.4.2 update.
Temporary solution is to use another soft keys app, but I'll have to ditch this phone ASAP, I'm out of warranty and Google will not fix something they caused.
Click to expand...
Click to collapse
That heat thing sounds odd to me. Do the home buttons work in landscape (With the earpiece to your right)?

lopezk38 said:
That heat thing sounds odd to me. Do the home buttons work in landscape (With the earpiece to your right)?
Click to expand...
Click to collapse
Yes, it does, but the touch input isn't recognized in the developer options. It's all documented here:
https://productforums.google.com/forum/m/#!topic/nexus/7SNIT8xPYzc

soulcedric said:
Yes, it does, but the touch input isn't recognized in the developer options. It's all documented here:
https://productforums.google.com/forum/m/#!topic/nexus/7SNIT8xPYzc
Click to expand...
Click to collapse
As said by many peolple in the thread you posted, it clearly seems to be a software issue :
- problem appeared after an update
- screen zone is fully functionnal with touch input (immersive mode or landscape tests proves it)
as said by parveen75, try to flash stock rom from developer google site (with a version on wich you know didn't have the problem, ie 4.2 ?)

popinterfaces said:
As said by many peolple in the thread you posted, it clearly seems to be a software issue :
- problem appeared after an update
- screen zone is fully functionnal with touch input (immersive mode or landscape tests proves it)
as said by parveen75, try to flash stock rom from developer google site (with a version on wich you know didn't have the problem, ie 4.2 ?)
Click to expand...
Click to collapse
I will try that, but it seems odd that other people would have the problem fixed after a screen replacement, which would identify it as a hardware issue.

maybe the screen replacement method (used by repair services/centers) came with a reset/flash of the rom.
What is even more strange is that some people seem to encounter the same bug again even after a screen replacement.
Please, keep us informed if the flash method solved the bug.
I'm currently still on 4.4.2 (for development needs) and i'm worried i could face the same problem !

I've confirmed that it's a hardware issue and has affected a lot of users who updated. I cannot touch the area of the screen in full screen apps.
Google should be warned and issue a statement about this, this is very bad news for us users.

The fact that it works after a screen replacement with no software modifications is proof enough. Time to vow to never buy a Google product again...

Temporary solution
any one has this problem should download any soft key app
BUTTON SAVIOR IS A good APP
it solved my problem
i advice you to try it
you can try any other app it's not advertisement you can use any soft key app i wrote this name just because i have tried it
good luck every one