Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
yanouch said:
Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
Click to expand...
Click to collapse
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
xbad1 said:
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
Click to expand...
Click to collapse
Yeah that's what i expected but wanted just to know if others had the same problem and if there was already a workaround for this
Many people have this problem, including a number of reviewers.
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
The customer is left in the cold!
Some people have a return policy - what if one waits for a software update, the return period expires, the update comes, but it doesn't fix the problem and it turns out to be a hardware problem??
The information politics of Sony and other companies (yes, Google, you too!) is an absolute PILE OF S**T!!
Yup, me too. The annoying thing it is difficult to document. Yesterday my tablet was charging and I turned the screen on using power button - lock screen didn't react at all to my inputs. Tried switching screen on/off a few times but it didn't help. Also tried double-tap to wake with no success. Went to get my camera to document, then of course it started working...
I've written this elsewhere, but this is how I notice the touch screen problems:
For me the tablet randomly doesn't recognize touches during the below instances. In all cases either going to the home screen and relaunching the app or turning the screen off/on will solve the problem. The problems occur several times per day but not constantly.
Sometimes opening apps will cause everything but the bottom android-buttons to be non-responsive. This can happen in any app it seems, including native ones such as Google Play.
Sometimes the lockscreen doesn't recognize touches at all.
While charging I've had issues getting the touchscreen to recognize touches, disconnecting the charger has helped.
Double-tap to wake seems to be very moody, sometimes working sometimes not. Sometimes it turns the screen on even by me just holding the tablet with my palm resting against the screen.
While not a bug per se, also the android-buttons seem very picky that you have to hit them right on the spot to work.
Other threads on same topic:
http://talk.sonymobile.com/t5/Xperia-Z2-Tablet/Touch-screen-problem/m-p/620325
http://community.sony.fi/t5/Tablets/Xperia-Z2-tablet-touch-screen-issue/td-p/1582051
http://www.android-hilfe.de/sony-xp...screen-reagiert-nicht-immer-zuverlaessig.html
Damn ! i'm not alone....
One forumer said he thinks that switching OFF Stamina mode helped a little bit...
I don't have my tablet with me, can someone test this ?
"A little bit" help is NOT enough.
The touchscreen MUST work perfectly, whether with Stamina Mode on or off or whether with Mode XY on or off. No discussion.
Sony HAS to fix this.
Already solved in .55 firmware
hasenbein1966 said:
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
Click to expand...
Click to collapse
The same experience with Z1 compact and support. Told them the camera is really broken - they told me there is absolutely nothing wrong with the camera and I'm the first one who got this problem. That was some weeks before, now they officialy added that maybe some devices are defect.
But that´s Sony, they give a **** about u, don't even try to contact the support.
I'm also having this issue, if I'm using the Sony sleve it's impossible to use the touchscreen as it will tip over when I press hard enoug for the screen to actually register it.
No problem here.
Only early days yet. The only prob I've got atm is Dropbox isn't showing up in the Album.
Edit: Fixed the Dropbox problem by using the Dropsync app.
I also seem to get this. The tablet works fine when tilted at an angle but for some reason can be completely unresponsive when it's laid flat. Would this suggest a hardware issue or a software bug?
I also get this, sometimes it's like I just need to press harder (so hard the tablet falls over when using the cover as a stand), but other times it seems that no matter how hard I press or how many fingers I apply it doesn't register a thing for periods at a time.
I'm lead to believe that this is either software or firmware considering the intermittent nature. Are there any custom ROMs out yet that we could flash to eliminate the software aspect?
I have same problem, most noticeable in Chrome, switching tabs fails to register 10% of time. I can only think Sony have a hardware quality control issue with the digitizer as if it was firmware related, surely everyone would be suffering. Strange none of the reviews have picked this up, but I'm going to have to return mine.
No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.
Interesting theory, just gave it a go, inclusive, but does seem worse in case. However if Sony aware, why have they not rushed out firmware as otherwise initial user experience is ruined.
QUOTE=hasenbein1966;52005720]No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.[/QUOTE]
POTENTIAL FIX FOUND (ROOTED ONLY)!
Rooted users can try this fix, works for me! Touch seems to work perfectly now, also when tablet not in hands and lying on non-conducting surface!
Edit the file
/system/usr/idc/clearpad.idc
and alter these two lines:
Code:
touch.pressure.scale = 0.0001
(original value: 0.1)
and
Code:
touch.filter.level = 1
(original value: 2)
Don't forget a nandroid before
Please report whether it helped! :good:
P.S.: just for the curious - on the first Tablet Z, the two values are also lower: touch.pressure.scale is 0.0074, and touch.filter.level is also only 1.
Thanks for suggestion but dont wish to root (I use it to watch Sky which wont work if rooted) - seems there is more assistance on this forum to the issue than from Sony. I'll give it another week for a firmware fix before returning it.
elaborate...
nos1609 said:
Already solved in .55 firmware
Click to expand...
Click to collapse
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
---------- Post added at 09:17 PM ---------- Previous post was at 09:11 PM ----------
homme_fromage said:
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
Click to expand...
Click to collapse
My bad, didn't read all the way through, ignore me.
Now after a few days I can say:
With the root fix described above, my tablet works like butter. Simply perfect. :good:
Only instance where I have still problems is when the tablet was lying around for a while and I try to operate the touchscreen without taking it in my hands. Then sometimes (not always) the screen doesn't react, but only for a short time.
The problem seems to be related to static electricity.
Related
Hi to everyone in this forum. I've recently received as a present a new toshiba folio 100, but, since I'm experiencing an annoying menu button flashing, I've thought of it as a software problem so I upgraded the folio using the foliomod1.3c and applied the rotate patch and also the 1.3c fix patch. The menu still flash with no apparent logic. I've tried to kill all applications running and it's still there. It seem to come up and down at random. I ask to all in this forum: do you believe it's a hardware issue or is a software issue? Because if it's a hardware issue I'm going to try to have a new folio from toshiba. I'm overall very pleased with the work that Dexter made to make the folio an usable machine but this flashing is driving me crazy. I use the folio basically as a portable scientific pdf reader so I need to concentrate on what I read and this flashing is really annoying. I would like very much to thank you all in this forum in advance for all the suggestion/help you could provide.
use my "foliobuttons" app
teknoraver said:
use my "foliobuttons" app
Click to expand...
Click to collapse
I have a request that serve All those who suffer MENU crazy button .
Is it possible to prepare application you can setting ON/OFF the MENU button
Most of the time useless button.
sometimes button jump after 10 minutes, sometimes after an hour
Usually I fix the problem by changing the settings with FolioButtons 1.1.
If you could add to FolioButtons on/off operation for menu Buttons was the best.
Hi teknoraver,
Can you add enabled/disabled menu button in foliobuttons application ?
flashing on...
teknoraver said:
use my "foliobuttons" app
Click to expand...
Click to collapse
I am pretty desperate about this issue, because none of the methods seem to help...
Right now the buttons work opposite- Menu button flashes mad and none of the other 3 responds...dont know how it happened
Just a thought- while the folio is booting up the menu button ALREADY flashes! I have zero understanding in there but isn't it a process that loads / starts early in the line?
I appreciate everyone's effort trying to solve this bug as it makes this handy tool a useless pile of crap.
I was wondering how many folio users are suffering of this crazy buttons madness.
Mine was crazy from the very beginning; I sent it back for repair and toshiba only did a firmware restore... Nothing changed at all!
It makes my folio almost unusable!
bye bye crazy buttons
After two weeks of testing and a complete breakdown of my folio100, I finally find the problem or just crazy buttons and freezing of the screen.
I drag a thickness in the screen in the bottom right corner of the screen to isolate the audio connector and it works better than a miracle again.
The only downside is that the screen comes out slightly from the slot but nothing really bad.
The thickness I put slightly too big or-1.4 mm I'll Demount next week to put a finer and I'll try to take pictures in passing.
Note however that the loss of waranty is innevitable.
Sorry for my bad english ;-)
I think it's a hardware issue and even a build quality issue.
If i hold my folio at the side of the buttons, i get the flashing buttons problem (even the foliobuttons app will not help), if i hold it at the other side, i've got no problems at all.
Do you have an animated background? Because I saw that some people had this issue with an animated background...
Hi Mshr73, nice first post indeed
Could you post some pictures of what you did?
Mshr73 said:
After two weeks of testing and a complete breakdown of my folio100, I finally find the problem or just crazy buttons and freezing of the screen.
I drag a thickness in the screen in the bottom right corner of the screen to isolate the audio connector and it works better than a miracle again.
The only downside is that the screen comes out slightly from the slot but nothing really bad.
The thickness I put slightly too big or-1.4 mm I'll Demount next week to put a finer and I'll try to take pictures in passing.
Note however that the loss of waranty is innevitable.
Sorry for my bad english ;-)
Click to expand...
Click to collapse
seems to get better...
I really don’t want to be too quick on this, but Dexter’s 1.4 seems to bring relief to this issue - for 2 days I have been running this mod the menu button stopped flashing!!
Any similar impressions on this?
vietnamibalzsam said:
I really don’t want to be too quick on this, but Dexter’s 1.4 seems to bring relief to this issue - for 2 days I have been running this mod the menu button stopped flashing!!
Any similar impressions on this?
Click to expand...
Click to collapse
No way pal, I guess I'm in the opposite situation. It still happens to me, and sometimes I think it even got worse... well, I can always look at crazy keys as a "special feature" that no other tablet will have!!!
I just tested without thickness under the screen, with foliomod 1.4 and after a few hours I again the problem of crazy buttons.
Mshr73 said:
After two weeks of testing and a complete breakdown of my folio100, I finally find the problem or just crazy buttons and freezing of the screen.
I drag a thickness in the screen in the bottom right corner of the screen to isolate the audio connector and it works better than a miracle again.
The only downside is that the screen comes out slightly from the slot but nothing really bad.
The thickness I put slightly too big or-1.4 mm I'll Demount next week to put a finer and I'll try to take pictures in passing.
Note however that the loss of waranty is innevitable.
Sorry for my bad english ;-)
Click to expand...
Click to collapse
Well, I just finished dismantling e reassembling my Folio. Following your hint, I cut a piece of paper and put it between the audio connector and the back of the screen (yes, it was metal vs metal). I'll see whether it's gonna work or not. Crossing fingers for now.
Not that I'm so confident in leaving a piece of paper stuck right where the DC input is .
BTW, did you try with a smaller thickness? Even if this is the problem, I'm wondering whether a piece of paper would be enough or not.
thyself can someone. post pictures of before and after details?
we will be much appreciated
i didn't have the crazy buttons issue this far in 2 weeks, just my home butten needs to be pressed harder. I'm pretty sure it's hardware related, i read often that users experience it when changing from an warm room to a colder one, or in regions where its verry humid(some circuit closes maybe...). so Mshr73 is on the right way as far as i can tell.
Dexter's 1.4
^Sbk79^ said:
No way pal, I guess I'm in the opposite situation. It still happens to me, and sometimes I think it even got worse... well, I can always look at crazy keys as a "special feature" that no other tablet will have!!!
Click to expand...
Click to collapse
Really sorry mate, I hope it will solved this for others too...
Anyhow, it is so disturbing, that I was already considering to send the tablet back to Toshiba...
I'll try to do this weekend if I do not have too many customers. I post the result Monday.
Mshr73 said:
I'll try to do this weekend if I do not have too many customers. I post the result Monday.
Click to expand...
Click to collapse
I'm looking forward to your pictures, too... because my trial simply didn't work.
I tried with both a single piece of paper and then with 2 pieces wrapped in tape. I put these spacers between the back of the display and DC/audio connector.
In both cases, the crazy keys phenomenon started to happen after 15-20 minutes of usage.
In most cases, it starts to show when I unlock the device. As soon as I unlock it, home and menu buttons light up with no apparent reason and go crazy for 10-30 seconds.
Then, I even tried to loosen just a little the screws (I read, somewhere in the forum, of a guy who said that he solved his crazy keys and screen lag problems this way). I mean, all screws are now locked but not too tight. Well, I have to say that I don't have any screen lag anymore (I even removed the piece of paper, from the battery area, which used to solve the issue before) but crazy keys still happen. I'm going slightly mad
^Sbk79^ said:
I'm looking forward to your pictures, too... because my trial simply didn't work.
I tried with both a single piece of paper and then with 2 pieces wrapped in tape. I put these spacers between the back of the display and DC/audio connector.
In both cases, the crazy keys phenomenon started to happen after 15-20 minutes of usage.
In most cases, it starts to show when I unlock the device. As soon as I unlock it, home and menu buttons light up with no apparent reason and go crazy for 10-30 seconds.
Then, I even tried to loosen just a little the screws (I read, somewhere in the forum, of a guy who said that he solved his crazy keys and screen lag problems this way). I mean, all screws are now locked but not too tight. Well, I have to say that I don't have any screen lag anymore (I even removed the piece of paper, from the battery area, which used to solve the issue before) but crazy keys still happen. I'm going slightly mad
Click to expand...
Click to collapse
Well ... with a piece of paper the problem Come back.
I handed a piece of cardboard and the problem disappears.
I think that to raise the screen to solve them but I'm still not 100% sure.
Hi, i have had my tablet for about 1 week, straight after starting it up i had a fw update which is 17.1.1.A.0.402 which i am assuming is the latest?
anyway i have read a lot about the new fw was supposed to fix the touch issues?
I also have the z1 which i still have and is perfect. ive recently updated to 4.4.2 on that and all my issues are fine on there.
my z2 is acting very strange, if i leave it alone for a while sometimes i will go on it and everything on the screen will be frozen, i can't tap anything, i have to press the power button and then swipe to open it again, it is then fine after that.
also i have noticed, and i think its happening a lot when my tablet is a little angled using the case, the screen will be a bit jittery, where as my z1 is really smooth, and i also sometimes have to really tap icons a few times before they register.
i play clash of clans a lot and its been a bit difficult to play as troops aren't selecting as i am tapping on them.
has anyone got any advice?
I have done a factory reset to see if that would fix any issues from the fw update but its still exactly the same.
Thanks
James
anyone?
james_lpool said:
anyone?
Click to expand...
Click to collapse
I installed the new firmware yesterday. While I notice an improvement with the touch problem it's still present. Just install an multitouch app (like this one: https://play.google.com/store/apps/details?id=com.easylabs.multitouch), let your finger trail on the screen and it's definitely obvious (the number on the top right should be the number of fingers touching the screen and it's often not). I tried the same thing on my old Iconia A500 and that's the one thing where it's WAY better than the Z2.
I don't experience anything as strange as you do though, it's mostly usable and I hardly notice it with the new firmware.
I did experience something very strange just BEFORE updating with one specific charger and one specific USB cable , the tablet wouldn't register any touch at all while it's was plugged in. As soon as I unplugged it it would work. The cable was fine with another charger and vice versa;
Weirdest of it all:
This happened while I was testing the output current for each combination of cable/charger and this particular couple was the one giving the "best" results; consistently between 1.1A and 1.2A
I can't reproduce this behaviour with the new firmware. All in all, it's usable for me. Biggest bug would be it not charging while playing power consuming games.
I have found mine goes more weird when it goes to sleep and i then wake it up, the screens sensitivity seems to be terrible, i have topress the off button and then start it again then its fine.
it will then mostly stay fine until the screen times out again then the same thing will happen when i wake it.
James: Same with my 521...
Touchscreen response was REAL BAD after updating to .402, then it went better and better day by day; strange phenomenon.
I also occasionally experience some touchscreen "numbness" after waking up the table with a double-tap, sometimes touch sensitivity suddenly becomes quite low just without any reason; touchscreen has problems detecting touches near the screen corners or doesn't react to touches at all. Solution: Switch to standby, and back on.
At the same time, the Android symbols (Back, Home, last apps) again become difficult to hit.
You can test this by slowly swiping your finger up from the lower bezel towards one of the symbols: If the touchscreen is ok, symbols get highlighted right after your finger reaches the lower edge of the symbol. If the touchscreen malfunctions, you need to move your finger up to the center of the symbols to get them highlighted.
So it smells like a software issue.
Touchscreen problems usually occur two to three times a day of normal use; so I regard it as acceptable - but the problem still isn't fully solved.
I would say it's a hardware issue which Sony attempts to counterbalance with software patches.
Just like on the Nexus7 (2013). There sfhub released a touchscreen fix which made the problem bearable for most users (with some experimenting with different versions of the fix, because each device is different).
I wrote a PM to sfhub asking him whether he could disclose how his fix works so that Z2 Tablet users perhaps could apply a similar, variable, tailor-made fix to their individual device.
No response, unfortunately.
Perhaps some of you could send the same request to him, and perhaps then he reacts?
every now and then, after double tap to wake, the tablet is extremely unresponsive.
I also just sleep/wake up again via power button and it's fine after that.
So my but feeling it's a software issue, not hardware issue.
- Frank
I never had touch problems but after updating to the latest firmware, the tablet is unusable from time to time
what's annoying me is that Sony wont seem to admit that there is an issue, i was talking on their live chat to support and they said that's the first time anyone's mentioned that and isn't on any list of any known issues
Which doesn't fill me with confidence on how quick this may get fixed.
The speed in which is gets fixed may determine if i just send the tablet back to Amazon for a full refund, unfortunately i have bought the Sony case and magnetic charger now as well
I'm just really puzzled what to do, what can i do apart from sent it back if Sony wont even acknowledge they are aware of the problem and will release a fix soon
The only thing is because i have now bought the charger and case, i kinda want to keep it.
It was a direct replacement for my Z1 which i still have, and that is also updated to 4.4.2 now, but that shows no touch issues at all.
What's very interesting and revealing:
When Sony was addressed a few days ago regarding battery problems on Tablet Z and a few phones after the Kitkat update, they immediately reacted!
They readily explained that it is a problem with the Google Play Services running amok and that a fix will come.
But it seems that just because this here is a Sony problem (and not one for which another company can be blamed like in the above one), Sony simply doesn't react at all and obviously orders the service employees to lie and say that they haven't heard at all of a touch problem.
Boooo, Sony, shame on you!
james_lpool said:
what's annoying me is that Sony wont seem to admit that there is an issue, i was talking on their live chat to support and they said that's the first time anyone's mentioned that and isn't on any list of any known issues
Click to expand...
Click to collapse
HAHA ! Exactly the same in Germany. Even after talking about that issue with the SAME person three days in a row, I still was told the problem was totally unknown.
Later, I had a more private talk with one of the support guys. He revealed to me there was an order from Sony to tell callers exactly that.
Ah, as I thought.
This is abysmal behavior by Sony, period.
Also on the Sony support forum, none of the official support staff has replied to any of the topics about touch screen issues. It seems they are just completely burying their heads in the sand...
FW .402 didnt fix the touch screen issue. It is noticeably better than any FW from before.
Gosh, the touchscreen keep going back to home when i'm in a middle of fb conversatuion.
I was testing with chromecast +youtube: those swibe action to enlarge or fade out afe 99% imprecise...
Really wondering if I can return the item to amazon to fix this problem...
Diomorgan said:
Gosh, the touchscreen keep going back to home when i'm in a middle of fb conversatuion.
I was testing with chromecast +youtube: those swibe action to enlarge or fade out afe 99% imprecise...
Really wondering if I can return the item to amazon to fix this problem...
Click to expand...
Click to collapse
Are you sure you're not just accidentally touching the home button while typing? That happens to me from time to time, which is a downside of having the navigation buttons centered compared to having them in the corner like on pre-4.4 Android tablets. I actually think Google should add a setting to choose if the navigation buttons on tablets are in the left corner, centered, or in the right corner. Having them centered also makes it awkward to reach these buttons when holding the tablet with two hands.
So some of you with white Z5 compact phones might have had this touch sceen bug with repetitive key presses and unstable touch screen behaviour bug which was previously "fixed" by a software upgrade:
http://www.xperiablog.net/2015/10/21/white-xperia-z5-compact-touch-screen-fix-arriving-next-week/
Lo and behold. This bug is back in MM, and there is another guy in the thread which I can see also have the bug come back
It is not always there, but sometimes its just there. I dont know what triggers it. A restart seems to help until it comes back again.
For those of you not familiar with this bug, it usually shows by repetitive touches, and highly unstable touch screen.
For example when i press the key "s", it usually put in "sssssss" like i have pushed that key 5-6 times.
Also the bugs shows, when for example you are scrolling in facebook/internet, it will not let you scroll. Whenever you touch the screen, it will enter, whereever you lay your finger on screen.
Lastly it also shows by the screen becoming completely unresponsive when you press anywhere.
I have clean installed MM and restored my apps via Sony Backup/restore app.
I am so pissed how a phone color (white) can somehow decide the behavior of the phone touch screen, and I believe sony is hiding something.
In the beginning I was thinking that maybe they made different builds for the different Z5 colors, so they might not have included the "newest" touch screen drivers for at launch time for the white version.
But the same bug appearing AGAIN in MM i have a very hard time understanding that should be the case that it was a software bug. I believe there are some hardware bug, they have somehow omitted by a software circumvention, and they forgot to add it to the white version for the MM launch.
Personally I have always had a problem with the "return" key when the phone is placed. Patch or not, this button works once out of 10.
For information, I just bought this phone. I also think there is a hardware problem. This is average for a manufacturer like Sony. I thought for a moment it back in service but when I see the number of dissatisfied with the service Sony in France, I preferred to keep my phone in the hope that a solution comes a day. We have the right to expect in my opinion ...
I did clean install via flastool also and i have/had this problem. Yesterday i did software repair via pc companion and restores apps after that and so far problem has not occured.
I also made a repair with PC Companion but nothing changed.
So there are other people here with this annoying problem.
You all have a white xperia yes?
This bug is so annoying I feel sometimes like tossing the phone into a wall.
If there was an alternative to this phone in this form factor and specs, I would have bought it yesterday.
But unfortunately there isn't
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
hipsterfont said:
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
Click to expand...
Click to collapse
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
I also have Sony Z5 compact white version which had the touch problem from start. Now after the Marshmallow update its back. As said above, it could happen while browsing (or on home screen) e.g. Entering links instead of scolling i.e. It triggers multi click. In these situations all menu keys will also be none responsive. Its starts acting normal again after a quick push of the power button, i.e. puttning the screen to sleep.
As a former developer for mobile software, both for apps and the android platform, i thinking i would agree with the above conclusion that the problem is hardware based, and not due to a difference in the delivery software version, as i was hopping. So the question is; will this always be a problem for these versions of Z5c white, i.e. they are forgotten in new builds?
Unfortunately I'm having the same problem with my white z5 compact...
mcmanuf said:
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
Click to expand...
Click to collapse
it happens that for different colors are used different materials.. probably white ones have different properties..
i can confirm that using bad cable/chargers this kind of bug happens with every device, with random touches and impossible scrolling.. if you have a well-known bad adapter and you note no differences with your white z5c, that's definitively the answer..
i think sony should recall all white z5cs and replace them with newer or different release
What revision of compact Z5 are you? Personally I have a revision 3 (that is written on the box).
I also had a touch of problem before moving to the latest version of Android (6).
My girlfriend also bought white Z5 Compact and funny thing... I put the Panzer Glass on the screen and guess what? Sometimes she can't turn off the alarm clock in the morning and sometimes navigation buttons are not responding. I tried then without the screen and it works without a problem. I am not sure if this is a problem with Panzer glass or sony's bug.
I have Z5 and have no problems, but mine is black edition
Mine is z5c white version as well. The bug started again on MM
And the bug quite annoying.
I bought it on updated lollipop.
And never had this problem before.
This plus Bluetooth is really making me hold off on not moving up from .200 lol
Argh - just saw the visual representation of this bug:
http://www.xperiablog.net/2015/10/06/xperia-z5-compact-owners-reporting-touch-screen-problems/
and it sounds A LOT like the one from the OnePlus One (driver & firmware issue)
easy blame: Synaptics - fix your ****
Anyway:
try enabling the double-tap-to-wake if it's not already enabled, lock the screen - give it some time to settle (~ 30 seconds),
wake it up (double-tap) - do some stuff - disable the double-tap-to-wake and lock the screen again.
Unlock it via power button and see if that improved the "situation".
Sony recommended a few times to boot into Safe Mode,
does this Mode exist on Android Marshmallow ?
Does it make any change ?
Had this in Nougat is there a fix?
It feels like a software problem! You can try to reinstall the system!
First consider whether it is a system problem. You can refresh the system to see if it is back to normal. If it still does not, then you may need to update a new LCD screen. You can go online to find the repaired video as a reference. The witrigs repair video is doing great, you can check it out!
Hey xda-community,
i've registered, because i have a strange problem with my LG G5 (H850) European Edition. If this is of any use, it's the Vodafone-Edition. Sorry for my language, i'm not a native speaker .
I got my G5 yesterday and was really pleased with the build quality (i was afraid, i was about the get some of those flawed devices as seen on the internet) and the raw power of the whole package. At first i didn't notice but then i realized, that the automatic brightness didn't work. Then i noticed, while having a conversation, that the display was'nt turned down. Up to this point it sounds like the known bug.
What i think (and please, push me into the right direction if i'm wrong - i'd love to take the shame not beeing able to look properly) makes the difference is, that after installing several sensor test apps from playstore, i always got the information, that both sensors are missing.
I took a trip into service menu and tried to calibrate (or better so say, to see if there was any sign of them) those sensors, but nothing happened. No reaction while covering the area where they are supposed to be, nothing.
Firmware is v10c-262-02. Tried to reset the phone and check while having nothing installed - same problem. I tried safe mode - same problem. I can check autobrightness but it doesn't have any effect whatsoever.
What really makes me shake my head is, that when i'm called and i turn the the display downwards to stop the sound, it works after 2 up to 3 times trying to cover the display.
I'd hate to send it in - maybe i'm just too stupid to look for answers, i'd really appreciate any efforts to help.
Thanks in advance and have a nice day.
Nero
Hey there,
short follow up to the problem. Yesterday evening i got a notification about an firmware update and wanted to install it. After hitting the proceed button nothing happened. Nothing. No installation, nada. I shook my head, deceided to return the damn brick and forgot about it. After an hour i noticed that my soft keys had changed their appearance. They got smaller. I asumed a kind of silent update (? nothing is shocking me anymore concerning this phone), checked the brightness control - no change. An hour ago i wanted to unlock my phone and got no reaction. I was about to hard reset it when it unlocked. I scrolled down the notification bar to check something when i noticed that the brightness was different from my setting. I hit the auto brightness button and bazinga. It changed by itself and since then everything works like a charme. The firmware version hasn't changed. I don't have the knowledge to explain anything or to know if something like this is even possibe (something was definitly new because all those vodafone apps where there again - which i deinstalled yesterday). Okay, long story short - either i'm officially going insane or they fixed it. Don't know, don't care.
Have a nice weekend!
Update: And it's gone again. I have no idea what to do anymore. I don't know if anyone is interessted in this, but i share the info anyway...
With Sensors (Umgebungslichtstärkesensor = Ambient light sensor, Näherungssensor = Proximity Sensor)
fs5.directupload.net/images/160508/459jqzhk.png
Without Sensors
fs5.directupload.net/images/160508/wiazcglk.png
nero
It certainly sounds like it *might* be defective, as you say that you have tried a factory reset.
It is a strange problem you have as it only appears to happen occasionally. It also sounds quite annoying. I know it is a pain to have t return it, but it might be better to do that and have a fully functional device, than to keep on facing this problem.
Sorry not to be able to give you a more satisfactory solution.
Good luck.
nobnut said:
Good luck.
Click to expand...
Click to collapse
Hello,
thank your very much for your reply. I agree, i think it'll be the only option i have. I'll try to do return it, it's quite easy in Germany but, nevertheless, connected to some time without a phone.
Have a nice sunday,
Nero
I have this same issue with the proximity sensor and in my case it is because of the Lifeproof case is causing this, many others with this case report the same thing. Try taking out of the case and test again - mine works fine with no case; If this still happens, with no case on, then maybe the phone
jrhlaser said:
I have this same issue with the proximity sensor and in my case it is because of the Lifeproof case is causing this, many others with this case report the same thing. Try taking out of the case and test again - mine works fine with no case; If this still happens, with no case on, then maybe the phone
Click to expand...
Click to collapse
Thank you for trying to help Sensor was damaged, send it in for repair and got it back. One can be sure that it's not a matter of blocked access to the sensors when a sensor test shows, that there are no sensors.
Told about this in so many forums that i forgot to tighten the loose ends. Sorry.
Kind regards
Hello, recently i sent my phone to warranty because of serious screen burn in issues, they replaced my sceen, which had more light bleeding issues, but i wouldnt mind that, as the burn-ins were gone, but to my surprise, yesterday after about 3hrs of constant on screen texting in whatsapp, the burn-in started appearing on the new screen, i am seriously pissed off, i really like this phone overall with the features it offers and so on, but the quality control... Wtf LG.. I now have bought a phone which i should just send for warranty repairs after a period of time?
Just wanted to share my experience with you, i still have a gpad 8.3 thats is still rolling on the latest 7.1.1 and has no quality issues and a robust metal build whatsoever, but this is just annoying...
Im sorry to hear about your issues with g5. Its a great device, whats wrong with your screen? Light bleeding whad do this mean?
Gmobilize said:
...Just wanted to share my experience with you,..
Click to expand...
Click to collapse
If you want to do something for us, try to use the search engine first until you start a new thread!
There are a lot of threads around here which has described screen ghosting on LG devices!!!
See here:
1.) (English) ->https://forum.xda-developers.com/lg-g5/help/lg-g5-screen-ghosting-burn-problem-t3545769
2.) (German) ->http://www.android-hilfe.de/thema/displayflecken-nach-langem-aktiv-sein.790992/page-3
3.) (English) ->https://forum.xda-developers.com/lg-g5/how-to/panel-vs-panel-series-t3480270
4.) (English) ->https://forum.xda-developers.com/tmobile-lg-v10/help/ghost-images-screen-image-retention-t3395732
5.) (English) ->https://forum.xda-developers.com/g4/help/screen-ghosting-lg-g4-t3451879
YOU are not alone!
non-toxic said:
If you want to do something for us, try to use the search engine first until you start a new thread!
There are a lot of threads around here which has described screen ghosting on LG devices!!!
See here:
1.) (English) ->https://forum.xda-developers.com/lg-g5/help/lg-g5-screen-ghosting-burn-problem-t3545769
2.) (German) ->http://www.android-hilfe.de/thema/displayflecken-nach-langem-aktiv-sein.790992/page-3
3.) (English) ->https://forum.xda-developers.com/lg-g5/how-to/panel-vs-panel-series-t3480270
4.) (English) ->https://forum.xda-developers.com/tmobile-lg-v10/help/ghost-images-screen-image-retention-t3395732
5.) (English) ->https://forum.xda-developers.com/g4/help/screen-ghosting-lg-g4-t3451879
YOU are not alone!
Click to expand...
Click to collapse
Dont you think i am aware of this? How does it help me? I have wrote ot in threads before and i write it again, this one was about the same thing happening even after warranty repair, and the cause is a faulty panel, i am sharing my warranty experience, i dont really understand why would you post these links? How is this helpful?
i think it would be interesting for all of us to know the period when it started to happen for the first time and then when exactly after the replacement?
I for myself got the screen replaced about 2 month ago having the screen burn issue as well. Phone IME starts with 604. Since the replacement no issue for me so far..but i am not so sure if it the problem is solved with that and the screen burn in starts again after a while again......
Gmobilize said:
Dont you think i am aware of this? How does it help me? I have wrote ot in threads before and i write it again, this one was about the same thing happening even after warranty repair, and the cause is a faulty panel, i am sharing my warranty experience, i dont really understand why would you post these links? How is this helpful?
Click to expand...
Click to collapse
aking007 said:
i think it would be interesting for all of us to know the period when it started to happen for the first time and then when exactly after the replacement?
I for myself got the screen replaced about 2 month ago having the screen burn issue as well. Phone IME starts with 604. Since the replacement no issue for me so far..but i am not so sure if it the problem is solved with that and the screen burn in starts again after a while again......
Click to expand...
Click to collapse
Its indeed interesting as it really seems to not appear at the beginning, and once it shows up it starts to get more noticable over time, for example as i said, it occured after heavy using whats app for about 3hrs most of the time with auto brightness sometimes hitting the highest levels, right now i can notice the burn in, but its not at levels where it would become disturbing, ill see how it goes, if it progresses and so on..
Gmobilize said:
Dont you think i am aware of this?
Click to expand...
Click to collapse
No, it was not visible for me reading your post, that you have get all informations about LG display issue.
Gmobilize said:
i don't really understand why would you post these links
Click to expand...
Click to collapse
i want to be sure, that you can see, that this is no individual case!
Gmobilize said:
How is this helpful?
Click to expand...
Click to collapse
If you had read all of my linked threads, you should know...
...many people has this problem with different LG devices...
... it was recognized at LG G5 phones produced between march and jun. 2016 (see serial number starting with 604 up to 606)...
... there seems to be a new display without ghosting but with a little more power consumption recognized since serial number 609...
... it makes no difference witch country code your device was! all displays could be affected!
...that some users have installed "sFilter BlueLight" app to prevent this issue!
...as some users reports,it is not granted, that this issue never returns on changed displays because it seems to be a general fault...
Maybe that all this informations does not help to solve YOUR problem, but this is a forum for questions and answers ant i thought, that this informations could be helpful to know. But as it looks like,it seems that this will be for other users only!
So if you feel disturbed of me, feel free to set me to first position in top of your ignore list!
and at least: see my signature at 3.!
non-toxic said:
No, it was not visible for me reading your post, that you have get all informations about LG display issue.
i want to be sure, that you can see, that this is no individual case!
WITH
If you had read all of my linked threads, you should know...
...many people has this problem with different LG devices...
... it was recognized at LG G5 phones produced between march and Jjund 2016 (see serial number starting with 604 up to 606)...
... there seems to be a new display without ghosting but with a little more power consumption recognized since serial number 609...
... it makes no difference witch country code your device was! all displays could be affected!
...that some users have installed "sFilter BlueLight" app to prevent this issue!
Maybe that all this informations does not help to solve YOUR problem, but this is a forum for questions and answers ant i thought, that this informations could be helpful to know. Maybe only for other ons only!
So if you feel disturbed of me, feel free to set me to first position in top of your ignore list!
Click to expand...
Click to collapse
Sorry, but to me the reply seemed non-friendly, as it would be addressed to a rookie user, who hasnt done his research, maybe im wrong about your post...
But overall, yes i have seen all those threads, and unfortunatley, as i have mentioned in some other LCD display threads, the app could basically be a temp fix for the issue, when its not at a disturbing level, as its a cause of a faulty panel.
At this point where my panel has been already replaced, i cant really keep track of its model.
Gmobilize said:
Sorry, but to me the reply seemed non-friendly, as it would be addressed to a rookie user, who hasnt done his research, maybe im wrong about your post...
But overall, yes i have seen all those threads, and unfortunatley, as i have mentioned in some other LCD display threads, the app could basically be a temp fix for the issue, when its not at a disturbing level, as its a cause of a faulty panel.
At this point where my panel has been already replaced, i cant really keep track of its model.
Click to expand...
Click to collapse
Okay so lets go through this together.
A burn-in only happens with amoleds as this is permanent. We have LCD panels so we have image retention which is non-permanent.
A LCD is a liquid crystal display. Means you have a certain state of the crystals. When you apply a voltage the crystals rearrange themselves and block light. This is why we need a background illumination. Anyway once you use it for a longer period with a semi-static or a static picture (like whatsapp typing bar, google maps info boxes, keyboards etc) the crystals start to shift in their relaxed form towards another state. Blue light is due to its short wavelength energy consuming -> high voltage applied -> faster image retention.
That's why blue light filters do work to some extent. (With cf lumen and root you can adjust to use less blue instead of having an overlay draining additional energy)
This liquid crystal thingie is dependent on a lot of different parameters, that's why some get it faster and some slower. My 1,5k$ thinkpad has the same issue with the navigation bar being a persisting image after 10h+ of browsing.
TLR
So this is actually not a warranty issue. LG also returned phones unrepaired as this is the negative side of a lcd and considered standard behaviour. Go for an AMOLED the next time as they can't suffer from this, but once you have image burn-in you will never get rid of it. So doesn't really make a difference.
https://en.wikipedia.org/wiki/Image_persistence (helpful for that burn in issue which a lot of people seem to get wrong)
Cheers
lolmensch said:
Okay so lets go through this together.
A burn-in only happens with amoleds as this is permanent. We have LCD panels so we have image retention which is non-permanent.
A LCD is a liquid crystal display. Means you have a certain state of the crystals. When you apply a voltage the crystals rearrange themselves and block light. This is why we need a background illumination. Anyway once you use it for a longer period with a semi-static or a static picture (like whatsapp typing bar, google maps info boxes, keyboards etc) the crystals start to shift in their relaxed form towards another state. Blue light is due to its short wavelength energy consuming -> high voltage applied -> faster image retention.
That's why blue light filters do work to some extent. (With cf lumen and root you can adjust to use less blue instead of having an overlay draining additional energy)
This liquid crystal thingie is dependent on a lot of different parameters, that's why some get it faster and some slower. My 1,5k$ thinkpad has the same issue with the navigation bar being a persisting image after 10h+ of browsing.
TLR
So this is actually not a warranty issue. LG also returned phones unrepaired as this is the negative side of a lcd and considered standard behaviour. Go for an AMOLED the next time as they can't suffer from this, but once you have image burn-in you will never get rid of it. So doesn't really make a difference.
https://en.wikipedia.org/wiki/Image_persistence (helpful for that burn in issue which a lot of people seem to get wrong)
Cheers
Click to expand...
Click to collapse
Thanks for the interesting article on LCD artifacts, however, i wanted to say some things:
As my for my first panel, that got replaced, image retention was pretty hard, as when the phone got warmer, it became really disturbing and barely usable as the keyboard and status bar started to ghost on grey background apps such as xda, the only way was to let it cool down and wait till everything disappears, as soon as i started using my phone a bit longer, the problem resurfaced very quick. So it clearly wasnt a normal reaction. Just to add, no CF.lumen like apps were able to help back then.
My current replaced panel is showing only minor signs of this, it becomes more apparent on longer usage times with the same elements and the ghosting is barely visible with not so intense usage, so i hope that this wont eventually get stronger as before. As it would seem to be a natural usage reaction, i still consider this an issue however, cause none of my previous LCD phone had anything like it, not even my LG Gpad 8.3. So im gonna try to apply warranty again if needed, as repair services seem to be pretty helpful in my country at least, as long as they have spare panels in stock.
And about amoled, i think ill pass that for a while, i have seen enough samsung demo units in stores have serious homescreen burn-ins.
With LG G5 the quality really seems to be an issue, yes there maybe lucky people with good units and so, but overall it is pretty disappointing, as feature and hardware wise i really love this device.
lol
I see the so called expert stopped responding like a retard. I had the same problem I just lgup and flashed stock all over again about 4 times and it started to show improvements. As of now I got rid of the burnt images on my lcd