So I just recently updated to Nut 's .136 firmware. Sadly the touch screen issue is still there. I have found a temporary solution though. For me, the problem is surely software based. When the touch screen gets buggy, a reboot will always fix it.
I have an app call Fast Reboot Pro installed, which restarts your system without actually restart your phone. I set the app to automatically do a "reboot" every time I unlock the screen. Whenever my screen starts acting buggy, I would just turn off the screen and unlock it.
This seems to fix the problem momentarily. I still hope someone can find a way to fix this for real though.
Sent from my C6902 using xda premium
Josh.L.Wang said:
So I just recently updated to Nut 's .136 firmware. Sadly the touch screen issue is still there. I have found a temporary solution though. For me, the problem is surely software based. When the touch screen gets buggy, a reboot will always fix it.
I have an app call Fast Reboot Pro installed, which restarts your system without actually restart your phone. I set the app to automatically do a "reboot" every time I unlock the screen. Whenever my screen starts acting buggy, I would just turn off the screen and unlock it.
This seems to fix the problem momentarily. I still hope someone can find a way to fix this for real though.
Sent from my C6902 using xda premium
Click to expand...
Click to collapse
This was what I've done to my past Z1... But it's still annoying so I decided to sell it and waiting for Sirius or Z2.
This issue is exactly same as Xperia SP... But SP's issue is worse than Z1.
Josh.L.Wang said:
I have an app call Fast Reboot Pro installed, which restarts your system without actually restart your phone. I set the app to automatically do a "reboot" every time I unlock the screen.
Click to expand...
Click to collapse
It's called Hot Reboot, it reboot UI only.
eclyptos said:
It's called Hot Reboot, it reboot UI only.
Click to expand...
Click to collapse
I use Fast Reboot Pro excluding almost all the apps..
I reboot system UI only
It's better to reboot locking the screen than unlocking (so you don't wait the reloading micro-time after you unlock)
Josh.L.Wang said:
So I just recently updated to Nut 's .136 firmware. Sadly the touch screen issue is still there. I have found a temporary solution though. For me, the problem is surely software based. When the touch screen gets buggy, a reboot will always fix it.
I have an app call Fast Reboot Pro installed, which restarts your system without actually restart your phone. I set the app to automatically do a "reboot" every time I unlock the screen. Whenever my screen starts acting buggy, I would just turn off the screen and unlock it.
This seems to fix the problem momentarily. I still hope someone can find a way to fix this for real though.
Sent from my C6902 using xda premium
Click to expand...
Click to collapse
May I ask what is wrong with the touchscreen on your phone? Although I dread to ask hehe.
The place I touched is not necessarily where the sensor "thinks" I touched. Or sometimes the screen just goes crazy without me touching anything.
Sent from my C6902 using xda premium
My phone stops recognizing touches and restarts at same spot (thats why swype shows trail, but write scrumbled letters) I get really pisssed. I hope they fix it in 4.4 or I will never buy sony again. (looks like anyway only nexus devices or similar. Cause of all the "anti-modding" attitude of producers)
I update to stock .136 and I can't reproduce it anymore. The issue was there on .290 today, I updated and I don't know what to do to get it back, I miss my favorite problem.
BTW, I receive yesterday the phone and in Sony Center they couldn't find the problem and they scratched my phone everywhere, I tested typing *#*#7378423#*#* and it was there again, the worst service I ever had.
eclyptos said:
I update to stock .136 and I can't reproduce it anymore. The issue was there on .290 today, I updated and I don't know what to do to get it back, I miss my favorite problem.
BTW, I receive yesterday the phone and in Sony Center they couldn't find the problem and they scratched my phone everywhere, I tested typing *#*#7378423#*#* and it was there again, the worst service I ever had.
Click to expand...
Click to collapse
on mine(136) it happens on normal usage, like web surfing(scroll up n down), gaming(dead trigger 2).
mayb u use it normally like wat i mention n report back?
chunlianghere said:
on mine(136) it happens on normal usage, like web surfing(scroll up n down), gaming(dead trigger 2).
mayb u use it normally like wat i mention n report back?
Click to expand...
Click to collapse
I will try some games like N.O.V.A 3 or H.A.W.X, both of them give me problems with .290, and I will report later.
i get the same problems. It happens during writing on keyboard and browsing on facebook app, imgur app ...
I already play N.O.V.A and some games and still not have the problem after update to .136. I also can put my phone on the bed and use it with one finger. I hope it will stay in this way forever.
i havent been able to reproduce it with .136 since i changed screen protector, no ASF, can't use bare screen because problem is maximized, happier than ever with this phone
Sent from my C6906 using xda app-developers app
eclyptos said:
I already play N.O.V.A and some games and still not have the problem after update to .136. I also can put my phone on the bed and use it with one finger. I hope it will stay in this way forever.
Click to expand...
Click to collapse
is yours using the default ASF?
chunlianghere said:
is yours using the default ASF?
Click to expand...
Click to collapse
You mean Anti-Shatter Film, Yes, I got the phone with that one and I put on it another one, so I got double screen protector and it's very responsive and working fine, at the moment.
Tried this app and so far it works as far as I know...
Btw Im on it for 2 days..
Sent from my C6903 using xda app-developers app
Related
hey guys, I´ve been having some strange behavior on my M2 lately, everything was normal till last week but now the phone started registering random inputs on all over the screen... its like I am touching the screen madly... I´ve already tried flashing the retail brazil SBF and everything still the same... I can´t even answer the phone straight!!!
any ideas? maybe my digitizer has gone crazy...
Take a look at this vid. It's mine. It is happening when i'm scrolling fast. I think I will send it to a service.
I get this when my phone is on the lockscreen connected to my pc.
Sent from my A953 using XDA App
This happens for me, when is connected to USB, PC or Dock.
Sent from my Milestone 2 XDA App
ddoubt said:
hey guys, I´ve been having some strange behavior on my M2 lately, everything was normal till last week but now the phone started registering random inputs on all over the screen... its like I am touching the screen madly... I´ve already tried flashing the retail brazil SBF and everything still the same... I can´t even answer the phone straight!!!
any ideas? maybe my digitalizer has gone crazy...
Click to expand...
Click to collapse
this happened to me a few times before. once was when i typed a really long email using my keyboard. when i shut the qwerty it started behaving crazy. a few other times was also after i used the keyboard.
then i realized something in common. the problem only occurred when i had 'words' running in the background. i uninstalled 'words' and i have never had the problem since
perhaps u have a really buggy software. try uninstalling one of ur buggy softwares and u would be grand.
if u cant locate the buggy software, turn off the screen (short press of power button), turn it on again, and unlock, and things should be back to normal
well... it look like I gonna have to send it to service too... I´ve already wiped it clean... I´ve done a clean flash of the brazil retail SBF and everything is the same... random issues all over... bad luck right?
thanks for the support guys!
I have not experienced this problem...maybe because I'm running stock ROM?
MegaBubbletea said:
I have not experienced this problem...maybe because I'm running stock ROM?
Click to expand...
Click to collapse
im running stock ROM too but i experienced it. somehow i think its a software bug.
dangpzanco said:
This happens for me, when is connected to USB, PC or Dock.
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
the same with me, the touch screen become a way too sensitive (everytime I want to scroll the drawer, I ended up in running the app I touch) and this is sucks..
This happens everytime I connect my MS2 to PC via USB..
Hope it can be fixed..
elhariz said:
the same with me, the touch screen become a way too sensitive (everytime I want to scroll the drawer, I ended up in running the app I touch) and this is sucks..
This happens everytime I connect my MS2 to PC via USB..
Hope it can be fixed..
Click to expand...
Click to collapse
Yeah...somehow turn down sensitivity?
MegaBubbletea said:
Yeah...somehow turn down sensitivity?
Click to expand...
Click to collapse
how do you turn down the sensitivity? i dont recall seeing any option to adjust the screen sensitivity. unless u could do this after rooting the phone perhaps?
In the past few days, my keyboard has been acting up. I've been using Smart Keyboard pro since the day I got my phone and LOVED it, but for the past few days, it's been acting the bollix. Basically, I could be pressing the delete button for maybe 4 or 5 times, and it would enter 2 z's and delete 3 charachters?
I thought that it might just be the keyboard, so I switched to the default one, and it did happen, but not as much. I have just installed the Gingerbread Keyboard from the market, and it seems to be working ok, but it's still annoying. Anyone else had any problems with their keyboard entering random letters?
Nhialor said:
In the past few days, my keyboard has been acting up. I've been using Smart Keyboard pro since the day I got my phone and LOVED it, but for the past few days, it's been acting the bollix. Basically, I could be pressing the delete button for maybe 4 or 5 times, and it would enter 2 z's and delete 3 charachters?
I thought that it might just be the keyboard, so I switched to the default one, and it did happen, but not as much. I have just installed the Gingerbread Keyboard from the market, and it seems to be working ok, but it's still annoying. Anyone else had any problems with their keyboard entering random letters?
Click to expand...
Click to collapse
Mine always put full stops outta nowhere its.like.its gone nuts or something..
Sent from my R800i using XDA Premium App
Nhialor said:
In the past few days, my keyboard has been acting up. I've been using Smart Keyboard pro since the day I got my phone and LOVED it, but for the past few days, it's been acting the bollix. Basically, I could be pressing the delete button for maybe 4 or 5 times, and it would enter 2 z's and delete 3 charachters?
I thought that it might just be the keyboard, so I switched to the default one, and it did happen, but not as much. I have just installed the Gingerbread Keyboard from the market, and it seems to be working ok, but it's still annoying. Anyone else had any problems with their keyboard entering random letters?
Click to expand...
Click to collapse
Try removing the factory installed screen protector... it does wonders for touch sensitivity and brightness of the screen. I highly recommend it.
Frogybloop said:
Try removing the factory installed screen protector... it does wonders for touch sensitivity and brightness of the screen. I highly recommend it.
Click to expand...
Click to collapse
already done that
I too have had this problem twice now.
The first fix was to install Gingerbread Keyboard and it seemed to fix.
Then i had the same problem again (If i pressed "p" it would also press "t" and pressing "delete" would also press "c") and fixed it by cleaning the screen with a wet wipe.
The problem for me when it happens is basically when you press the right hand side of the screen in landscape mode, it also think you are pressing the middle of the screen at the same time.
Its only happened twice so im not all that bothered.
Try cleaning the screen with wet wipe and see if it fixes.
I've been using swype...and as cool and innovative as it is...I'm always having to double our triple check my text msgs and posts...lately I've been having to correct my corrections..its a bit ridiculous so I'm trying to get into the habit if reading what I type every few words..
Sent from my R800x using XDA App
I just posted a thread about a multitouch issue on the xperia play. I think it may be causing your problems. It may not make sense what I am saying right now but if you read my thread it might make sense.
Basically when you are typing fast you will definitely have 2 touch points on the keyboard. and the Xperia Play is counting more than 2 touch points. So your third touch maybe registered as a 3rd finger.
Here is my post if you want to take a look
OK. I've just cleaned the screen with a wet wipe. I'm going to post this message and leave it if it makes any incorrect entries.
Seems to have worked. I will now try landscape orientation.
OK, so portrait seems to have worked well enough. I'm trying out the landscape input now. Seems to be working. I was kinda worried about this problem, but cleaning the screen seems to have sorted it out.
Also, I have installed swype, but I do not really like it. Its awkward. I used to love it on my WinMo 6.1 phone (Omnia) however, I do not feel that i should be restricted to what keyboard I can use because of the phone not responding to input properly.
Back to portrait, OK. Seems to have worked. Nope, its doing it again now. Dunno why?
Stress
Sent from my R800i using XDA App
I have a question.
Is this problem consistent like it happens every single time or does it come and go?
I personally use swype and I love it. I have not had this problem yet.
It's not a software problem, it is hardware.
When mine has had the problem, it does it on stock keyboard, chinese keyboard and gingerbread keyboard.
Basically, for me, when i touch the furthermost right hand side of the screen in landscape mode, it also registers as touching in the middle of the screen too.
Well it only started happening in the past few days. I'm gonna reflash back to 2.3.3 stock and see does that fix the issues. If not what's everyone's suggestions?
Sent from my R800i using XDA App
RacecarBMW said:
I just posted a thread about a multitouch issue on the xperia play. I think it may be causing your problems. It may not make sense what I am saying right now but if you read my thread it might make sense.
Basically when you are typing fast you will definitely have 2 touch points on the keyboard. and the Xperia Play is counting more than 2 touch points. So your third touch maybe registered as a 3rd finger.
Here is my post if you want to take a look
Click to expand...
Click to collapse
Tried to replicate this problem using the stock keyboard, and couldn't get the problem to happen.
So i'm not the only one who is having this problem?
dsswoosh said:
Tried to replicate this problem using the stock keyboard, and couldn't get the problem to happen.
Click to expand...
Click to collapse
Well that was just my theory to the OP. The multitouch problem does exist but I thought the problems with the OP's keyboard was related to this. Turns out its not.
I flashed CM7 and haven't experienced this problem yet, but I'm sure I will at some stage... *sigh*
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
a67543210 said:
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I can't believe this ! Is this a SAMSUNG or an Android/ICS problem ?
My version is:
4.0.3
IM74K.XXLPQ
Any custom ROMs addressed this issue or how can you avoid this on ICS? Is the only solution to go back to Gingerbread ?
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Its a bit like continual posting in the wrong forum nobody knows why ??
jje
rumz82 said:
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Click to expand...
Click to collapse
No overheating (yet) you can help if you can keep logcatting through usb cable till it lock/standby freezes and your screen won't come on when pressing power ..
Install SDK + Drivers, write in commandprompt:
adb shell logcat > save.txt
Wait for the error / freeze where screen won't come on.
Then paste here or upload somewhere might contain a lead to a solution!
Double - sry - galaxy forgot login
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
thedadio said:
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nah!
It's there on all the kernels. I myself am a Siyah user.
I moved back to GB for this weird and terribly serious issue, but that time i didn't know it was a common problem.
This is ICS' best feature for sure.
I really CAN NOT believe how this issue is NOT yet known well and haven't brought in to front line. Google knows about it and yet I haven't seen any official statements about it. How ****in unbelievable or not perhaps? Google way?? Well **** it.
Utter Nonsense. What i wonder is, really, does any Android user actually use the phone but show off only??
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
gtcardwhere said:
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
Click to expand...
Click to collapse
Do the logcat as I provided the correct command to extract it to a file.
Then do your torrent thing, and make it crash- so we can debug !
Used to happen, since I installed latest hydrog3n-ICS rom (13-05) never had those again!
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
sunshean said:
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
Click to expand...
Click to collapse
uv?
ultra-violet ? is my phone in danger of skincancer ?
dezzadk said:
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
Click to expand...
Click to collapse
Hi,
It happened to me as well after the ICS update and I tried to plug the AC charger to see what happens, and surprise...the screen turned on .
It's not a fix (especially when away with no accessories) but it's better than nothing, hope this helps; also you should try plugging the USB cable. Tell me if it helps.
Thanks,
dezzadk said:
uv?
ultra-violet ? is my phone in danger of skincancer ?
Click to expand...
Click to collapse
Haaaaahahah! He means under volting. I don't know if you was serious lol but just saying. I'm on cm9 but don't have this problem :-/.
Sent from my GT-I9100 using xda premium
Yep,I mean under volting, you need to look your kernel, and I think it doesn't work fine because your kernel has under volting so much.
Sent from my GT-I9100 using Tapatalk
Reading around and installing load monitor from play store should fix this until a better solution is found
Sent from my GT-I9100 using Tapatalk 2
Best solution is to stay on GB because is more stable, until ICS gets better cooked!
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.
hi guys..
Got my new phone at the launching day.. everything runs perfect..
But yesterday and today i encounter a small issue..
please note that i have fingerprint scanner lock on my phone..
when i pressed the home button just to wake the screen, the screen didn't respond.. only the side buttons lid..
the screen remained black after the second press too.. then i pressed the power button once and the screen woke..
the thing was that when i pressed the power button after this incident the home screen game me a third option, apart from emergency calls (left) and alternative password (right), Unlock via Google placed to the middle..
this happened also today twice..
Any suggestions on this ?? did anyone encounter this ??
please note that i didn't use any other locking method except fingerprint scanner and the home button responds fine in any other case.. Thanx..
I randomly get unresponsive touches when trying to open an app in the app drawer folders. Haven't had the home button issue though
-Sent from Tapatalk
I'm having the exact same problem. Very disappointing for a new device. Not sure if I'm going to return it yet. I've tried factory reset and it didn't fix it.
Guy in the shop said he'll have to send it back to Samsung for testing.
I've gone back to using my old phone !!!!!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
BigAl1044 said:
I'm having the exact same problem. Very disappointing for a new device. Not sure if I'm going to return it yet. I've tried factory reset and it didn't fix it.
Guy in the shop said he'll have to send it back to Samsung for testing.
I've gone back to using my old phone !!!!!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
S-Voice is causing the problem on the home button lag, go trun off the open with home key in the svoice settings....
TheAxman said:
S-Voice is causing the problem on the home button lag, go trun off the open with home key in the svoice settings....
Click to expand...
Click to collapse
I turned it off when I first got the phone and still have it, although not as noticeable
-Sent from Tapatalk
eyecon82 said:
I turned it off when I first got the phone and still have it, although not as noticeable
-Sent from Tapatalk
Click to expand...
Click to collapse
same here I also switch this off and still same problem and format wipe data and cashe don't help
im having similar issues while on a call, i cant type in the extension, i touch the number pad and it does nothing. I turn off screen and now it doesnt want to turn back on. Like anything new, there will be a few hiccups, but samsung are usually fast for that first firmware push. I remember for the S4, i got it on launch day and the same day a new firmware was available, the note 3 took about 10 days before that initial firmware that fixed the few most obvious issues. Dont bring it back, just be patient.
polish_pat said:
im having similar issues while on a call, i cant type in the extension, i touch the number pad and it does nothing. I turn off screen and now it doesnt want to turn back on. Like anything new, there will be a few hiccups, but samsung are usually fast for that first firmware push. I remember for the S4, i got it on launch day and the same day a new firmware was available, the note 3 took about 10 days before that initial firmware that fixed the few most obvious issues. Dont bring it back, just be patient.
Click to expand...
Click to collapse
I've randomly noticed I can't click on an app to open it if it is in a folder I created in the app drawer
-Sent from Tapatalk
I heared some new firmwares have been pushed... Anybody got one?
Sent from my SM-G900W8 using Tapatalk
polish_pat said:
I heared some new firmwares have been pushed... Anybody got one?
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
It gets pushed out in waves, so it may be a few days to a few weeks till you get it. Kind of a bummer
-Sent from Tapatalk
TheAxman said:
S-Voice is causing the problem on the home button lag, go trun off the open with home key in the svoice settings....
Click to expand...
Click to collapse
Did that now and will test it through all day .. so far so good..
will let you know you guys..
hopefully it will get fixed.. if not we wait for an firmware update..
UPDATE
I used my phone all day using the settings above.. (no s-voice at home button and fingerprint lock) I encounter the problem 3-4 times.. other than that all is ok..
Now im going to use all day the pin to lock the screen and see what happens..
thanx
UPDATE
still the same issue with pin lock screen.. So probably an update will solve this..
thanx
z89x23 said:
Did that now and will test it through all day .. so far so good..
will let you know you guys..
hopefully it will get fixed.. if not we wait for an firmware update..
UPDATE
I used my phone all day using the settings above.. (no s-voice at home button and fingerprint lock) I encounter the problem 3-4 times.. other than that all is ok..
Now im going to use all day the pin to lock the screen and see what happens..
thanx
UPDATE
still the same issue with pin lock screen.. So probably an update will solve this..
thanx
Click to expand...
Click to collapse
Hey man,
Had the same issue with my S5, I think the wait for the fix is easier to handle if you know there are other guys having the same issue rather than having something wrong with your specific device. So imho it'd be great if some other guys would reply just to know it's a common issue.
To me SGS5 is a great phone even with all the rants and reviews against buying it, there will be updates, we just need to be patient.
Thanks for the post!
rciochin said:
Hey man,
Had the same issue with my S5, I think the wait for the fix is easier to handle if you know there are other guys having the same issue rather than having something wrong with your specific device. So imho it'd be great if some other guys would reply just to know it's a common issue.
To me SGS5 is a great phone even with all the rants and reviews against buying it, there will be updates, we just need to be patient.
Thanks for the post!
Click to expand...
Click to collapse
I can confirm that i have similar issues too.
Sometimes (2-3 a day) the screen is not waking up from sleep state when i press the home or the power button.
The solution is that i need to press the power button to sleep the device and then press again or press the home button to wake up.
Not a big deal but i hope that this issue is not hardware related and a firmware fix will solve it.
Apart from this, it's really a great smartphone.
Hi,
Just a small update, the issue replicates also when using the Samsung S View case, just bought one and I still get the same behaviour as with the home and power button (i.e. only the softkeys light up, the screen doesn't wake up).
I haven't been able to consistently replicate though, but it seems to happen after long sleep periods.
All the best!
rciochin said:
Hi,
Just a small update, the issue replicates also when using the Samsung S View case, just bought one and I still get the same behaviour as with the home and power button (i.e. only the softkeys light up, the screen doesn't wake up).
I haven't been able to consistently replicate though, but it seems to happen after long sleep periods.
All the best!
Click to expand...
Click to collapse
Hi !
One question.
Which ROM version do you have ?
The ...ANCE, or ANCF ?
thank you all for your replies.. its good to know that its not my device..
Hopefully with the new update they will fix it..
by the way yesterday i missed a call, do to that problem.. the phone was ringing but the screen was sleeping..
So i decided to chance my ROM, from EUR-Greece to NEE-Norther Countries.. Also did a hard factory reset after that.. Volume up + Power + Home.. Also deleted the cache partition..
I used odin.. No problems found.. and Kies recognizes the phone..
So i will check how this goes and get back to you..
Levus said:
Hi !
One question.
Which ROM version do you have ?
The ...ANCE, or ANCF ?
Click to expand...
Click to collapse
Hi
My build number is KOT49H.G900FXXU1ANCE
Levus said:
Hi !
One question.
Which ROM version do you have ?
The ...ANCE, or ANCF ?
Click to expand...
Click to collapse
Was using my original one which got an OTA update as soon i got it open..
SM-G900F EUR G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
Now as i posted above, i m using
SM-G900F NEE G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
I saw an ANCF
SM-G900F TTR G900FXXU1ANCF Android 4.4.2 31.03.2014 1186806
but i dont know the TTR which region is so i decided not to apply..
rciochin said:
Hi
My build number is KOT49H.G900FXXU1ANCE
Click to expand...
Click to collapse
i have the same.. on the NEE ROM
I dont think that was different on my EUR ROM..
z89x23 said:
Was using my original one which got an OTA update as soon i got it open..
SM-G900F EUR G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
Now as i posted above, i m using
SM-G900F NEE G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
I saw an ANCF
SM-G900F TTR G900FXXU1ANCF Android 4.4.2 31.03.2014 1186806
but i dont know the TTR which region is so i decided not to apply..
Click to expand...
Click to collapse
I have the XEH G900FXXU1ANCE...
I was just thinking that the G900FXXU1ANCF is maybe a little bit newer, as the build number is higher (1186806) So that's a different rom for sure.