Look at the clip and picture please,You can see the problem
These dots sometimes appears and sometimes disappears
It happens rarely
Its not permanent
Does anyone have any idea about this weird problem?
Edit: it's proximity sensor. It happes during call.
It's likely software. Does it do it in safe mode?
If present in safe mode probably a firmware or system apk bug.
Try clearing the system cache.
Is the system clean, no malware, rootkits etc?
If in doubt, factory reset.
If you can't track it down, factory reset, then verify it's gone before you update or load anything.
Then be careful what you install.
I will try it in safe mod.
I'm not sure, but i think this problem didn't exist before BULF.
Yeah, it seems like a software issue. Try backing up your data and doing a hard factory reset and see if that helps
It's Android 12, One UI 4.0. Guarantee if you downgrade to Android 11 3.0 the issue will be gone.
But that won't be possible, after BL upgrade with BLUF...
It is proximity sensor
olafsand said:
It is proximity sensor
Click to expand...
Click to collapse
Is it really?
Because it happens when I'm calling on WhatsApp.
It checks that do you hold your phone on ear or not i think.
Related
This happened to me yesterday and that was completely by mistake. I had the marshmallow update for sometime now and not experienced any major issues other than the random heating (while charging) and some drains at times.
The major issue occurred to me yesterday, when my mutli-window function got disabled by some how and then the phone did not respond to any of my finger touches anywhere on the screen. I have a password lock screen and that too stopped working because the touch response system was not usable. After a struggle for many hours and one sleepless night, the next morning, when I was just thinking of sending the phone to the service center; it just came to my mind and I tried out the SPen and that was working just fine. :victory:
So, using SPen I unlocked my phone and tried to understand what changed. As I normally enable a few functions on my phone, it easily came to my notice that the multi-window function was disabled. So, again using the SPen I enabled it and Voila!! the finger touch started working back.
This is pretty crazy and never experienced this before the marshmallow update.
PS: Even the backlit hard buttons ( left one, home, back right ) had stopped working for me for that instance.
Anyone has any clue on it?
Did you do a reset after the upgrade?
donalgodon said:
Did you do a reset after the upgrade?
Click to expand...
Click to collapse
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
vaibhavgaikwad said:
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
Click to expand...
Click to collapse
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
donalgodon said:
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
Click to expand...
Click to collapse
I think I have been more clear and transparent, if you says the multi-window is not an issue then it may be something else which I am not aware of. Though I know that over that particular day nothing new was installed on my phone (so I doubt it can be other software).
Why I am sure its the marshmallow update is because the older version I had tried disabling the mutli-window and the phone worked well, only with the marshmallow update the phone got weird (that too with that multi-window disabled) and enabling the multi-window made it work, so that's my point.
To answer you question on "Did I do a reset", the answer is no I did not, I rebooted (and shut) it couple of times thinking its overloaded but it did not change my situation. Only after I realized that SPen was working fine I could unlock the phone and enable the mutli-window and there after it started responding well to my finger touches too. It's working good today as I write this response. I can once again disable mutli-windows and check if it goes weird again. Let me know if you want me to do that?
Regards.
I recognize that doing a reset can be a pain, but it's probably worth it in the long term. It's up to you, but if it were me, I'd do a reset and start fresh.
When you make major version leaps, the chances of problems increases dramatically over point releases. (i.e. going from 5.x to 6.x is bigger than going from 5.0 to 5.1)
Hi there,
my XZ2 (H8266, latest patch level) regularly gets stuck / stalls: After interacting with the phone, the processes suddenly become much slower, the UI almost gets unresponsive, and it seems like the pone takes ages to execute processes. Only a restart helps. I couldn't figure out what triggers this behaviour or if it is caused by an application running in the background.
Any hints how to fix that or how to debug it?
Might be a good reason to try out that safe mode.
hotcakes_shinku said:
Might be a good reason to try out that safe mode.
Click to expand...
Click to collapse
Hi, could you elaborate a bit? What would be the point of trying the safe mode? Using the phone in safe mode and see if similar behavior happens again? If yes, what is the conclusion?
If this behavior does not occur in safe mode, it is proof that some application, you installed, is to blame.
If this behavior occurs in safe mode, then either some system application, or system itself is to blame.
After this, you will know what to do.
In first case, only way is to go through your installed applications one by one and try uninstalling them. This way, you will identify the app that is causing it.
In second case, I would recommend trying to repair firmware using Xperia Companion.
Sent from my Xperia XZ2 with Tapatalk
I didn't have this issue on Oreo, but it was indeed a problem on DP3/Beta 2, but seems solved on DP4/Beta 3.
Update & it should be fine.
Dear all,
I was using Sony Companion to basically do a factory reset (they call it hardware fix) and now it seems solved.
Hello there
This is regarding a P20 Pro (running Pie EMUI)
Getting some error as following : suddenly, the camera won't start at all / black screen
(attached a screenshot that usually displays when attempting to start the camera)
Usually goes away after a restart, but not all the time
Is this a hardware malfunction or?
Any suggestions appreciated
Thanks a lot
Could be either hardware or software, first step, find camera app in settings and clear data.
If no result,, backup and reset phone, if this fails to cure it, then its likely hardware so contact carrier or huamwei
Sent from my CLT-L09 using Tapatalk
Hi I have the same problem. It works after restarting the phone but it is just temporary fix. I tried cleaning cache and data, factory reset no change. Interestingly the issue is reported on other forums. I don't know is it software or hardware problem
This thing started with that ****ty Pie update. if you can rollback do it, i sadly cannot since my region dont support it, hope this **** got fixed next patch.
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Tritonio_GR said:
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Click to expand...
Click to collapse
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Tritonio_GR said:
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Click to expand...
Click to collapse
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset or software repair with Xperia Companion
Use Xperia Transfer to back up your calls/contacts/texts before you reset the phone
Didgesteve said:
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset
Click to expand...
Click to collapse
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
thegrobi said:
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
Click to expand...
Click to collapse
Hi Ralf,
the phone will always work better with a reset after a major update, all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
here, is one example, or another, but I didn't jump to Pie because of all the negative feedback and the scores of people trying to downgrade.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Thanks for the links.
Didgesteve said:
all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
Click to expand...
Click to collapse
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Click to expand...
Click to collapse
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
thegrobi said:
Thanks for the links.
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
Click to expand...
Click to collapse
Looks like there is know issue with the Osmand+, the date of the post is may last year, but it may just be a 'feature'
When backing up with Xperia transfer, make sure you select all the boxes that are optional. It's things like text messages/contacts/phone history that are useful after a reset. Some apps can't be moved and have to be downloaded directly from the playstore, but Google should give you that option, after you log back in to the wiped phone.
Edit: I can recomend Sygic, free maps for one country, works without data.
In the meantime, I found more users with this problem and a little solution that another user describes:
I can confirm I have the exact same issue since Android 9 with my Xperia xz1 compact.
I normally have no lockscreen options set. So when I wakeup the Phone, it sometimes kind of 'locks' the screen. Widgets do not respond, I cannot switch home screens. The time on the status bar remains correct. If I then click on an app and go back, everythning behaves normally.
So I'm quite sure this must be a software issue, as other people have this problem to.
My workaround for now is to have a lockscreen option aktive. But I would rather have not, for conveniance.
I tested this also with safe mode and complete factory reset of the phone. The 'bug' is still there.
Click to expand...
Click to collapse
If I disable lockscreen, then apps stop when it is switched on again. However, I always have to enter pin or use fingerprint sensor, or smart lock.
This often does not work when cycling and is dangerous when cardriving.
On Android 8, the lockscreen did not need to be active.
So the problem is not Osmand and MagicEarth.
It is a Sony 9 bug with Android 9.
bye,
Ralf
Found in an other forum an easy method to reproduce the problem.
disable the screen lock (it must be set to "None");
lock the phone and then unlock it;
lock and unlock it again.
Click to expand...
Click to collapse
bye,
Ralf
---------- Post added at 01:50 PM ---------- Previous post was at 01:20 PM ----------
Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf
[/COLOR]Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf[/QUOTE]
So, did you ever find a solution?
I will notice that in my phone I have installed a MDM of my work place but I am not sure that it is related to the described issues
I have this issue too on my 4 XL when i unlock the phone for like a few seconds the refresh rate goes down and back to 90 hertz. After that it is fine.
Same here, factory reset can't fix it either
It seems like an hardware issue...
It can be possible that this problem is not shown on each device, and after less the a year to make these issues
Assafaviv said:
It seems like an hardware issue...
It can be possible that this problem is not shown on each device, and after less the a year to make these issues
Click to expand...
Click to collapse
Are you using "smooth display" in dev options with "show refresh rate" toggled on? What about in safe mode? have you wiped and clean flashed the phone?
The answer to all your questions is yes, and still having this issue