I'm getting random problems with proximity sensor during call. Sometimes it locks at screen disabled state and never enables. On Oxygen 11 I am still able to turn screen on using power button. On Oxygen 12, it's not possible and phone is locked and dead completly with black screen until 2rd party disconnects call - after that, need to wait 1-2 minutes. Not even possible to hard reboot.
It's completly random issue, sometimes after 5 minutes call duration, sometimes 10 or 15 minutes, sometimes it's still fine even after longer time elapsed.
Any ideas what's wrong?
I have the same problem
You guys should open a thread on OnePlus forum, since it's not really related to this forum. It's an OOS issue.
Related
I've been experiencing the following symptoms in the last 24 hours or so, on a Tilt2, stock ROM:
-Frequent unsuccessful attempts to wake the phone from sleep. Often takes a few tries, usually successful, but I've felt the need to reset at least twice today.
-Occasional full-screen random color pixellation upon wake attempt. This generally goes away after a second or two, but sometimes I need a few wake attempts to get it off.
I am speculating that this might have something to do with the GMail IMAP issues that some people are having in the last day or two, or at least that's my best guess at associating it with a known issue, but I have really no idea. I've changed nothing, and I can't think of any possible traumatic experiences the device has gone through recently.
Everything worked fine yesterday, and has worked fine for over a year.
Follow-up, I hadn't yet noticed patterns in the issue until more recently. Now, I see that the problem occurs more in portrait.
Symptoms include:
-Landscape - generally normal touchscreen operation, I remember one time having some odd hardware keyboard behavior, though can't remember exactly what it was doing. I have also noticed that the power button seems to have no effect when in landscape.
-Portrait - phone is sluggish to wake, occasionally waking up to that random color pixel screen. Screen often freezes. Sometimes it comes back to normal, other times not. Power button seems to work normally, at least in toggling sleep/wake states.
I'm now thinking this probably does NOT have to do with the GMail IMAP issue, as some screen difficulty is occurring immediately upon power-on at times, before WinMo even begins to start.
I'm thinking some bad circuitry somewhere for whatever reason, and it might soon be time to evaluate repair/replacement options. Not sure what happened.
Which begs the side question, anyone have any idea what AT&T is replacing the Tilt2 with on insurance claims these days?
hi guys, i got a d855 and i have some issues which i think they may be stock rom's bugs and i d like to hear your opinion. I have the latest ota V10h-EUR-XX btw.
1) Every time i restart it appears in the notification panel the "voice mate" shortcut. I remove it using the edit at far right but still it reappears every time i reboot the phone.
2) Sometimes after an unanswered call or message the screen turns on as usual but it doesnt turn off. Ofc i ve selected to shut off at 30 seconds from the settings. Even if i change the settings to like 15 seconds the screen still wont turn off unless i manually lock it. This problem fixes if i restart the phone.
3) Every time i boot my phone i get this message: "unfortunately the process com.google.process.gapps has stopped"
So is there someone else who experiences these kind of issues?
wow, these 3 bugs are new to me. haven't experienced any of those at all.
I'm on V10J global though.
You're having permissions issues.
I'd bet my left testicle that a fresh flash back to stock will fix all 3 of your issues.
+1 on the voice mate .. irritating ~
I've encountered the screen on issue - although not only did the screen stay on after a missed call, the phone also became and remained completely non-responding, no screen input registered. Had to reboot manually. It happened only once in 3 weeks though.
Hi fellas, I'm currently on my favourite ROM (Resurrection remix) from all time. I use fingerprint unlock and when I place my finger, the phone unlocks but screen takes longer to turn on (up to a minute in the worst case)
Yes, you heard me, turn on, the phone is unlocked, gives feedback when touch the screen and responds to input for a while, then stops responding until screen comes up. I have greenify and I can confirm it does not interfere with it
Sometimes in the morning I have to even hold down the power button to reboot in order to stop the alarm
Missed few calls
List of troubleshooting methods I tried
Remove Greenify (absolutely nothing improves, standby drain increase)
Unroot (the same, nothing gets better)
Enabled ambient display (got even worse)
Clean ROM (no apps installed at all, no Google account, still the same issue)
Replaced kernel (installed insigniux and screen does take a little bit less) The eternal wait time barely happens, but is not fixed, Its a 45% fix anyway
All I ask is this is a rom bug and if it there is a workaround
Thanks in advance and have a nice day:fingers-crossed:
Did you try disabling pocket mode ?
Sent from my whyred using XDA Labs
Well I still can try it, I'm gonna see but that does not seem to be the problem
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
It seems the problem is more severe than just Android.
Because even in TWRP, I noticed the display need to wait ~1 minute from the last time I turn off the display (push the power button) to reactivating it.
If I try to turn it on, the display will give black color, but I still can actually interact with the system.
ArcOnFire said:
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
Click to expand...
Click to collapse
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Shimizux said:
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Click to expand...
Click to collapse
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
ArcOnFire said:
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
Click to expand...
Click to collapse
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Shimizux said:
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Click to expand...
Click to collapse
I don't think it's a battery problem. I see that I can play game for 1hr+ fine. A game that require exact timing of 2 touches on top of that. So that ghost touch really doesn't appear.
But yeah, it's really 2 contrasting sign
- In one hand, it seems an OS problem because I can simulate an environment where the screen definitely won't be frozen for hours, while on specific other environment, the screen freeze can happen very quickly between release and re-occurence.
- On the other hand, the problem seem doesn't stop on OS level because it can be found in TWRP.
If I read an answer on Quora that shows GIF image on the section I read, the screen freeze 100% won't happen. I tried the same thing on imgur too, the screen freeze won't happen.
So it seems that as long as the screen is showing dynamic content, it won't freeze (that's why game and YouTube doesn't show this kind of problem, but reading a web full of text/static images can)
A bit of update : I have left my phone in off state for 4-5 days. And I have been using it again, albeit, less extensively since my main phone has changed to K20 Pro.
Long story short : I haven't encountered screen freeze again. But this is just after 2 days playing with less intensity.
I wonder what really went wrong.
EDIT: fixed... sort of...
im getting "battery and performance keeps stopping" error now tho if anyone knows how to fix it
deleting data for battery and performance helps for some time then the error returns
Shala1122 said:
i dont get notifications when using wifi after locking the screen and waiting for about 30 seconds
i send myself whatsapp message from another phone and it wont appear and only appear after i turn on screen... sometimes they will arrive with screen off but minutes late...
on moble data its working perfectly...
i already auto start + no restrictions for the app
this is happening on miui eu and also lineageos after clean install
when charging i do get notifications even on wifi
is there a way to fix this issue?
Click to expand...
Click to collapse
if it works while charging then the problem is with deep sleep
i identified the problem but idk how to fix it
3zozHashim said:
if it works while charging then the problem is with deep sleep
i identified the problem but idk how to fix it
Click to expand...
Click to collapse
do you experience the same issue? what rom are you using?
its super weird cause some time ill receive notifications immediately or within a couple seconds even after half an hour when the screen is off, and sometimes ill receive nothing at all only when i open the screen
making notifications very unreliable...
EDIT : thinking of that im not sure its a deep sleep issue since i only experience it when using wifi... on mobile network everything seems to be working as it should
seriously turn off battery restrictions to that app to none
Shala1122 said:
do you experience the same issue? what rom are you using?
its super weird cause some time ill receive notifications immediately or within a couple seconds even after half an hour when the screen is off, and sometimes ill receive nothing at all only when i open the screen
making notifications very unreliable...
EDIT : thinking of that im not sure its a deep sleep issue since i only experience it when using wifi... on mobile network everything seems to be working as it should
Click to expand...
Click to collapse
i do not experience this issue
im using stock rooted rom
i also turned off battery restrictions on all apps
EDIT : I was wrong, the issue is not fixed.
3zozHashim said:
i do not experience this issue
im using stock rooted rom
i also turned off battery restrictions on all apps
Click to expand...
Click to collapse
please try the following on your xiaomi phone
connect to wifi (and turn mobile data off for testing purposes but it also happens with it on)
restart phone
unlock screen wait a couple of seconds then lock it
from a different phone send yourself a whatsapp message
you probably will receive that notification
unlock the phone and tap on the whatsapp notification to enter the chat
then go to home screen
open recent apps and tap on the "X" button to close all apps
turn off screen and wait for 5 minutes without using your phone (better wait 5:10 to be sure)
now send yourself a message from another phone and the notifications should arrive late and if youll turn on the screen itll arrive as soon as you turn it on...
issue seems to be happening across models and roms too
it happens on my f3 with v13 & v14 after a clean flash and only whatsapp installed
also happens on my redmi note 9s with xiaomi eu v13
strangely enough also happens on my f3 using linageos rom...
many people online complain about this issue, i tried every solution but it seems like there is none...
on my moms galaxy a52 there are 0 issues with whatsapp notifications...
Shala1122 said:
please try the following on your xiaomi phone
connect to wifi (and turn mobile data off for testing purposes but it also happens with it on)
restart phone
unlock screen wait a couple of seconds then lock it
from a different phone send yourself a whatsapp message
you probably will receive that notification
unlock the phone and tap on the whatsapp notification to enter the chat
then go to home screen
open recent apps and tap on the "X" button to close all apps
turn off screen and wait for 5 minutes without using your phone (better wait 5:10 to be sure)
now send yourself a message from another phone and the notifications should arrive late and if youll turn on the screen itll arrive as soon as you turn it on...
issue seems to be happening across models and roms too
it happens on my f3 with v13 & v14 after a clean flash and only whatsapp installed
also happens on my redmi note 9s with xiaomi eu v13
strangely enough also happens on my f3 using linageos rom...
many people online complain about this issue, i tried every solution but it seems like there is none...
on my moms galaxy a52 there are 0 issues with whatsapp notifications...
Click to expand...
Click to collapse
Im also facing the same issue with whatsapp and emails. rest all works perfectly.