Related
Did anybody here experience on SK17i that when you install an APK coming from say, a file explorer or even the "Application Installer", then you click on the program you want to install, you can't click the "Install" button?
I mean you can click it but it won't register. And there's nothing you can do about it, unless power cycle the phone, and randomly experience the issue again.
I am pretty sure that this is not a hardware problem as the touch screen works everywhere, only in Installation this problem comes up.
I noticed this on the stock .335 firmware, and now that I flashed the .368 I thought it was fixed, still there sometimes, randomly.
But when it works (immediately after a power cycle), it works just as normal.
Installations coming directly from Android Market does not have this problem.
I don't install/uninstall apps regularly so its not much of a big deal but I really find this strange. As I am not fond of doing reboots and waiting for phone to start up just to find out it has that issue again, what I do is just install using "adb install" when connected to my laptop.
Any similar experience, and how is this resolved?
i was .335 now .368 but i don't have this issue sorry.
I'm curious when you say reboot do you turn off the phone completely or you have an app.
in the market Fast Reboot closes all app but keeps phone still on. maybe that can help in some strange way instead of turning off the phone, if thats what you mean.
thanks for the response. like i said its rare i encounter this, but at some random instance it happens. if i had no choice i power cycle the phone (sorry i mentioned reboot in the 1st post), but it is power cycle. i know the "Fast Reboot" application, but what that does is just kill all apps, not really reboot
btw, a program that really reboots the phone on one click is "Reboot Control Widget", which I have installed (rarely used though) and it needs root.
Same issues have happened here randomly. I am running the .368 firmware with google market automatically updated to the newer version (the windows phone 7 like).
Nope. Didn't have this problem
Sent from my SK17i using XDA App
Could that be because the installation file is corrupted or invalid?
^ Not so, because after a power cycle, its almost 95% the error disappears and you can install it normally. Strange huh...
I have this issue sometime,which the version is 4.0.A.2.364
and will try the 2 'reboot' app mention in this post,thanks.
2 days ago my phone totally lost responsiveness of touch screen. As in touch screen dead. I'm sending it back today for seller to replace. Good thing I bought a cheap arc yesterday.
What's evident here now, is this issue could be telltale signs that eventually the touch screen will die so arrange for backup and warranty.
Sent from my LT15i using Tapatalk
jtdc said:
2 days ago my phone totally lost responsiveness of touch screen. As in touch screen dead. I'm sending it back today for seller to replace. Good thing I bought a cheap arc yesterday.
What's evident here now, is this issue could be telltale signs that eventually the touch screen will die so arrange for backup and warranty.
Sent from my LT15i using Tapatalk
Click to expand...
Click to collapse
Or you had a dud phone
Sent from my ST15i using xda premium
Yes that may be the case. In any case, because of that event, I was able to get a cheap Arc. Now i'm thinking which do I keep when the SK17i gets back.
Sent from my LT15i using Tapatalk
Just an update on this matter.
It seems the app "Screen Filter" which helps reduce the brightness contributes as one of the cause or maybe the main cause of this issue. I happened to observe it on Xperia Arc on rare occassions. When I turn off the app, Install clicking works afterwards.
Do you know if the recent ota fixed it?
I normally get it when I open the play store.
Sent from my EVO using xda app-developers app
joebarkho said:
Do you know if the recent ota fixed it?
I normally get it when I open the play store.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Still flickering for me (Play Store grey-background loading screen) on 1.22 - don't see any difference
SOB!
same here still there :crying:
just installed mean rom 1.4 with the new ota as the base.. So far no flickering..
Was on meanROM 4.2 until today, when I relocked and unrooted in preparation for getting a replacement at Sprint (I'm still within my 30 days). I was going to replace the phone because of this exact problem - a weird, barely-perceptible strobe effect when viewing grays and looking at certain photos in the gallery. And now - after all the hard work of finding an RUU for 2.13, figuring out the android SDK, learning how to use ADB (not to mention the whole initial unlock/twrp bootloader shebang) - I find that I cannot for the life of me make the screen flicker. OK, sometimes there's an extremely brief (~150ms) hint of it all on a gray screen, but absolutely nothing compared to the headache that it was before. I'd recommend completely unrooting/relocking your phone and pushing the correct RUU. QBking77's the best for it - look up his youtube vids on android sdk intstallation/usage, then relocking your bootloader, then unrooting/installing an RUU. Remember to clear your Google Wallet first, and set your fastboot to off (under power settings). After relocking your bootloader, you might notice that you cannot boot past it. That's fine; just push your RUU with fastboot USB. You'll know what I mean after watching the vids.
After all that, if your results were like mine, you'll know it actually had something to do with your custom ROM. I have no idea how that is possible, as I seem to recall a flickering in my stock ROM, too, but I guess I was wrong.
For relocking/unrooting
Step 1: Android SDK setup
Step 2: Relock the bootloader
Step 3: Unroot/Push RUU (for some reason, I had to go straight to pushing RUU from step 2 without booting into any ROM).
From all my scouring online, though, I've noticed that the people most consistently hammered with this problem (especially on screens other than photos in the Gallery or gray colors in the battery histogram of power settings) have build issues with their screens. These include light leak seeming to emanate in bands fanning up out of the home 'button' or graphical issues. These people usually report a fix to the problem once they receive a replacement; the ones with my problems typically complained of having received up to 3 (!) phones in a row with the maddening flicker, suggesting a software issue. It seems that the HTC One X itself was plagued with these problems, with graphical glitches also entering the mix, but an OTA fix a month ago or so minimized issues.
Lemme know how things go... I still have 4 days or so to return my phone if the flicker comes back, haha.
i saw flickering in minecraft, some other apps like ColorMe and even google maps. it was the phone itself, there was something physically wrong with it. Took it to the sprint store, showed them what was wrong. they even unrooted me and updated me to the latest firmware. i re downloaded Minecraft and opened google maps and showed them the problem was still there. and showed them on their own demo phones that it was not normal. Got a new phone.. but now i cant be S-Off.. How ever the flickering started to piss me off too much. Had to do it
For some reason I believe this made it worse for my phone, had minor flickering at first and once I updated it got really horrible. Point where I could pretty much notice it everywhere.
Sent from my EVO using xda premium
drmclove69 said:
For some reason I believe this made it worse for my phone, had minor flickering at first and once I updated it got really horrible. Point where I could pretty much notice it everywhere.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Probably had nothing to do with the update. Hardware problems only get worse until it gets fixed. Think of a crack on your windshield. It grows like an inch a week.
Recently, the past couple of weeks, my XTZ has been lagging out a lot, the keyboard has been freezing, and the screen has been going unresponsive a lot! I've had it since June and this is a recent problem. Its not the launcher; one of the first things i did was install Nova launcher, however i am running stock (I believe build 370). This is getting to be a real problem as i have to restart my tab in the middle of important tasks (as i'm mainly using it for school now). I am rooted using DoomLords easy rooting kit ( i believe v13, maybe 14 but i doubt it) and bootloader is still locked. And no i dont have a live wallpaper and recents is cleared plus i use greenify.Thanks in advance for any help.
Don't know if this is related, but I just updated to the official 4.2.2 update a few hours ago, and the touchscreen on my Tab Z is unresponsive, doesn't want to register any inputs
573W1E said:
Don't know if this is related, but I just updated to the official 4.2.2 update a few hours ago, and the touchscreen on my Tab Z is unresponsive, doesn't want to register any inputs
Click to expand...
Click to collapse
Hmm i'm not sure but i haven't updated it yet. Do you have the 16gb wifi as well? (SGP311)
jetstream131 said:
Hmm i'm not sure but i haven't updated it yet. Do you have the 16gb wifi as well? (SGP311)
Click to expand...
Click to collapse
Yes, I do. I've had it about a week
So I restored my device with flashtool (still .370) and i'm still getting slight lag out issues. It's definitely better than before, but the screen still goes unresponsive and I have to lock and unlock the device in the middle of whatever im doing. Also, ive noticed it registers multiple touches at random moments. For example if im on chrome and my tab is lying flat on my desk I may go from scrolling a webpage to zooming into it, all whilst using one finger. Any help would be greatly appreciated.
Hi,
My Z4 just asked to update the ROM, and afterwards, the screen has areas that are no longer touch sensitive.
Is anyone else experiencing this issue?
Thanks for any ideas!
Jim
Have you tried rebooting, then opening the Diagnostics app and running the touch screen test? If there are still dead spots showing in the test, you might want to flag it to Sony support.
I'm not certain if it's a software or hardware issue, but I have found both pre and post-update, that the touchscreen occasionally becomes less responsive, to the point that trying to use a drag gesture doesn't work without the touch dropping out. This happens every couple of days, and I suspect it's to do with throttling as it coincides with very sluggish performance. Seems to resolve itself when left for a few minutes, or a reboot.
Yes! I thought it was just me. I have a tempered glass screen protector and removed it to confirm whether it was causing the issues. Also ran the diagnostics which ran just fine.
It seems to be perfectly fine after a reboot and then the longer you go the worse it gets.
Hoping that this is fixed in the 5.1.1 update whenever that happens.
The conditions that this occurs does seem extremely sporadic. After playing Star Wars Uprising for ~45 minutes yesterday morning, the touch screen failed to recognise any swipes or taps, to the point I had to force a restart with the power button to exit the game. After leaving the Z4 for 15 minutes, no issues at all.
Last night I managed to play the same game for over 90 minutes, and today for another 90 minutes with no problems at all.
I'm starting to think that it could be performance throttling, alternatively I have noticed the screen getting particularly warm above where the SOC sits. Could this temperature be affecting the screen sensitivity? Using CPU-Z I have found some of the sensors reporting around 70C, battery around 35C, though this is after running intensive games. I'm unsure if the upper temperature is normal for this type of chip or not.
Sent from my SGP771 using Tapatalk
I have the very same problem:
Tempered glass from IVSO and the original case from Sony.
Since the update the touchscreen is VERY unresponsive.
I removed the case (!) and it got better (seriously, WTF?).
Does it mean to remove the tempered glass will solve the problem?
But it was fine before upgrade to 251. Sony sucks...
我從使用 Tapatalk 的 SGP771 發送
I reset to factory settings, and that may have cleared it up... but I'm not positive.
I'll update this thread when I play with it some more.
Did anyone have success with removing the screen protector?
OK - I can confirm that a factory reset after the upgrade does not solve the problem. My tablet cannot pass the touch screen diagnostic.
2xmanman said:
Does it mean to remove the tempered glass will solve the problem?
But it was fine before upgrade to 251. Sony sucks...
我從使用 Tapatalk 的 SGP771 發送
Click to expand...
Click to collapse
I removed the case, not the screen protector.
But some issues are left, so i hope for the next FW-Update...
An update:
I reached out to Sony's support group. They suggested downloading the PC companion app and having it reflash the .251. This does a factory reset.
This made the touchscreen response significantly worse.
My next step is to see if they will let me downgrade to the previous release, because the tablet was working flawlessly on that release.
Sony support says you can't downgrade to the previous rom. I found flashtool, but can't find the old rom to flash onto the tablet. Still looking...
Noticed the same thing after the update.. Hoping for a fix soon as it was flawless before the update.
Now simply browsing is annoying because it either misses swipes or registers them as longer swipes, causing the page I'm trying to read to scroll down super fast as if I flicked it when I actually scrolled slowly. :crying:
There is no update coming. Sony does not acknowledge that the problem exists.
Need more people to post on Sony offical forum, tell them this problem.
I'm hoping the .253 version helps this problem. It doesn't appear to be available for anyone yet.
jbresee said:
Sony support says you can't downgrade to the previous rom. I found flashtool, but can't find the old rom to flash onto the tablet. Still looking...
Click to expand...
Click to collapse
Here is a complete tutorial about flashing any firmware on your Z4 tablet, even downgrade to an older one.
http://www.xperiablog.net/2015/03/1...peria-lollipop-using-xperifirm-and-flashtool/
I flashed Nordic version of 28.0.A.7.24 firmware and my touchscreen sensitivity is back to normal
If you have any questions about the flashing procedure feel free to ask.
I had this exact problem after updating to 224. Ran the Sony Pc companion program on my windows pc and did a full software restore on my z4. problem solved.
laggist said:
I had this exact problem after updating to 224. Ran the Sony Pc companion program on my windows pc and did a full software restore on my z4. problem solved.
Click to expand...
Click to collapse
I'm not sure whether is it because of root or Xposed, but after doing a factory reset, the touchscreen seems a bit more responsive. It is after rooting or installing xposed that the problem comes back up.
riveria said:
I'm not sure whether is it because of root or Xposed, but after doing a factory reset, the touchscreen seems a bit more responsive. It is after rooting or installing xposed that the problem comes back up.
Click to expand...
Click to collapse
Ah, I also have intermittent touch problems. Until now I kept thinking it's because my finger is too cold or something, but I have it since upgrading to .224 also. Rooted and running Xposed v.85.1.
jelbo said:
Ah, I also have intermittent touch problems. Until now I kept thinking it's because my finger is too cold or something, but I have it since upgrading to .224 also. Rooted and running Xposed v.85.1.
Click to expand...
Click to collapse
Yea, I kinda think it's either because of root or Xposed that's interfering with the touch sensors. But I'm kinda leaning onto to Xposed that's causing the problem.
Yet another problem with my device: random reboots. No matter what I'm doing, lots of apps open or only one, battery high or low: the screen goes black, the red LED blinks a few times and off the device goes. Any other people experiencing the same?
You most certainly have a faulty unit.
It happened once. I got the phone on Tuesday. I was reading on Flipboard. Let's see how it goes.
Sent from my E5823 using XDA Free mobile app
it happened to me too, it was within 7 days period so i exchanged it for another one, the new one has been problem free
one of my friend also had random rebooting problem on her z3c and she sent it in twice for repair without success, if i didn't hear her case i wouldn't have demanded an exchange
Happened to me too, listening to music with my headphones, I pause the music to talk to someone, 5 minutes later press the headphones button to play, nothing happens and when I check the phone it was rebooting. Hasn't happened again yet, was 7 days ago
My phone has rebooted maybe 5 times in two weeks. Usually phone has been idling on table.
Sent from my iPad using Tapatalk
Seeing all responses here, it doesn't look very promising... I dont want to send it back yet, because the "service and repair" here in NL is a joke. They do a factory reset, say everything is fixed and send it back to you. I've experienced this before several times with my Z3c...
Hope a sofware update gets rid of these blackouts and bugs.
I got zero reboots after 1 week so i wanted to let you know because its to easy to get negative things out while the people with no problems dont come to the web because they have no reason yet
I had this problem, I fixed it by flashing latest build from xperifirm, and
I also had noticed media storage app using 1gb of memory so I forced close n cleared data and problem has gone.
karimero said:
Seeing all responses here, it doesn't look very promising... I dont want to send it back yet, because the "service and repair" here in NL is a joke. They do a factory reset, say everything is fixed and send it back to you. I've experienced this before several times with my Z3c...
Hope a sofware update gets rid of these blackouts and bugs.
Click to expand...
Click to collapse
that's exactly what they did for my friend's z3c, they kept believing it was a simple software problem, you gotta be tough to get more
like the other guy said, my first z5c would reboot just sitting on the table doing nothing, i suspect this might be more than software
Ill repeat, mine does not reboot for itself, and if would be, its an obvious sign 1) you did something what the device doesnt like, 2) you clearly have a faulty unit. Peace of cake, nothing to worry about, just exchange it and voila.
I've been having this problem on my brand new Z5 as well. I bought it from Clove so I really don't want to have to send it back. Gonna try and see if I can narrow down the cause or try to see how I could fix it (factory reset, reflashing the stock firmware or whatever).
Really hope it clears up.
Edit: So I repaired via PC Companion and I don't want to speak too soon but it looks like it's all good. The first time it happened was after installing a bunch of apps, including some older ones as well as some obscure ones. It's entirely possible that one of those apps were at fault. I've tried my hardest to replicate the issue since the repair (and being much more conservative with the apps that I've installed) and I haven't seen it happen once. I'm definitely hopeful now that it was an app-related issue and not a hardware one.
Sent from my Xperia Z using Tapatalk
Just out of curiousity..
What color is your device and from where did you purchase it?
Ive been hearing about faulty white Z5Cs which Sony acknowledged even.
Mine is black. But I have only had one spontaneous reboot the second day after I bought it. 3 weeks now and it hasn't happened again.
Sent from my E5823 using XDA Free mobile app
Mine is black color.
I have it since 4 days, and it already rebooted three times randomly ...
I don't know if I'll keep this phone or resend back and have an other brand device.
It happened with my white one when I had my SD card plugged in. I sent it back and got a new one
Mine's black and it never rebooted on its own
Black Z5C. I've been getting that kind of reboot regardless of repairing via PC Companion, or build number.
Any thoughts on what might be the issue?
Also, off topic, I believe I have two dead pixels (installed Screen test, and two pixels can't reproduce blue color) and I was wondering if that was an issue that might get me a new phone or just repair (it's been 2 months since I got it)?
I've had it for a month and maybe have gotten one or two reboots. I recently took a week long vacation and got 4 or 5 freeze/reboots. I'd be viewing photos, taking a picture, recording 4k and it would freeze. Power button could still bring up the menu but screen is not responsive. Eventually it reboots with the red led flashing. Only one it just rebooted with no warning
I have between 0 to 3 restarts/day. Sometime it crashes and freezes in the crash without restart. That is very nasty. I'll try to track it down.