Hello,
After the last update (touch screen related bugfixing), my tablet do a strange thing,
With normal usage the screen suddenly started to turn to black, many random pixel turned to black, and in about 5 second the screen is turned completly black (like in some old screen saver)..
I switch off the display, then switch it on and the tablet display is still black, I have to hold power botton for 10 second and reboot the tablet and then it worked perfectly.
A second time the same problem, then i switch off the display, then switch it on and the tablet working perfectly.
I hope it's not hardware related issue (maybe video card related), anyone else have the same issue?
Maybe the option Force GPU Rendering in Developer Option is the cause, I try to disable it (with the previous firmware version no problem with this option enabled in 3 months)..
PS: the upper half of the back of the tablet where the Qualcomm 810 is located isn't hot when the problem showed itself..
PS2: in Developer option I have enabled
- Debug usb
- verify usb app
- Force GPU Rendering
- Use Nuplayer
Did you find out anything more about this?
Have you continued to experience this problem?
I have a problem which is not exactly the same, but since your thread didn't get any answers I thought I would share my problem here in case it may be relevant to yours...
My Z4 (LTE) suddenly doesn't respond to finger inputs on the screen. It has happened three times over the last 5 days.
I did buy a sleeve from aliexpress a few weeks ago, and this has a magnet closing lock that wakes up the screen.
Can it be that this magnet disturbs the digitizer, or is it more likely to be software/OS related?
In dev options I have NOT "Force GPU rendering" or anything else beside "Allow mock locations" and "Stay awake while charging".
BR,
Christopher
Related
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
Dear all!
I am really in despair
I notice a strange phenomenon on my Galaxy S 3 (German version).
Sometimes there occurrs a flickering of the screen. It is caused by thin greyish horizontal lines which jitter with high frequency at some parts of the screen. You should not imagine it as some blinking of the whole screen. It's only a partial jittering of thin greyish lines.
It does appear at random, I cannot force this effect to occurr. Most of the times it's subtle, but sometimes it is clearly visible.
I read in some other threads that people noticed flickering in dependence of the power saving options. This I observed as well. But I don't know why. Unfortunately, none of the other threads came to a conclusion. And the problem seems to affect only very few devices.
My S3 was sent into repair twice. Two times the touch screen was exchanged. Last time they also changed "some electrical and mechanical parts". However, the flickering still occurrs.
I now tested for a while and made the following observations:
- it's not related to 3g, wifi or mobile connections in general (occurred while switched off)
- it's not related to "automatic brightness control" (occurred with manually set brightness, 1/3)
- it's not due to the display (they changed it two times)
- it's not related to ambient light (happened both with artificial light and in darkness)
- it's not related to the setting "adjust display color"
- neon light helps to trigger it, as well as switching the screen on or manually changing the brightness
- it's not related to any one of the single settings in "energy saving mode"
- flickering "survives" switching the screen off for a short time
- switching "energy saving" off always finishes the flickering
Can anyone shed light on the reasons for this?
Try unticking the second option in Power Saving mode, which is supposed to lower the FPS in order to preserve power. You can still user PS mode but the flickering should be gone.
iridaki said:
Try unticking the second option in Power Saving mode, which is supposed to lower the FPS in order to preserve power. You can still user PS mode but the flickering should be gone.
Click to expand...
Click to collapse
thank you!
i already unticked all single options there. didn't change it. the only solution is to switch the whole "enrgy saving mode" off as it seems.
paddybear79 said:
thank you!
i already unticked all single options there. didn't change it. the only solution is to switch the whole "enrgy saving mode" off as it seems.
Click to expand...
Click to collapse
I am sorry, I did not read the OP carefully enough, where you stated that
it's not related to any one of the single settings in "energy saving mode"
Click to expand...
Click to collapse
I am using PS mode with all the options checked all the time, I don't think I have ever disabled it, and I haven't noticed the issue you mention. Can you tell us more about root status/ROM/kernel on your device etc? Also, have you tried disabling PS mode and observing the phone for 24 hours or so, to see if it still does the flickering at some point?
I'm having same issue. As for the conditions my result is that it would only appear after wake up when power saving is on with lowest brightness. Also it's not noticeable on dark wallpapers. Any ideas other than "turn off" power saving mode?
Just to add, I'm running stock 4.1.2 version which didn't fix this problem and I was observing phone without PS for a few days without any flicker of this kind.
Hi everyone, I've had my Moto Z for a couple of days now and am pretty happy with the device - even with the battery life I have one small problem, however.
Sometimes, when the screen is turned off, the Moto Display approach action won't work. In these cases, I also notice that the bottom right IR sensor isn't lit up - which it usually is when the display is turned off. The approach action only starts working again when I pick the phone up. This is very inconvenient and not how it's meant to be.
Is anyone else experiencing this bug?
At first I thought it might be an issue with Doze putting the process responsible for the Moto Actions to sleep, but after whitelisting all Moto apps the issue still sometimes occurs. I have not yet found out under which circumstances this happens.
Any help would be greatly appreciated!
EDIT: It seems this issue only occurs immediately after turning off the screen, after which there is a slight delay (a couple of seconds) before the IR sensor is activated. I will observe if this is really the case, which of course would render it a non-issue.
I purchased my S21 about 5 weeks ago and I am not sure if I have been experiencing this issue since I bought it but in the last week, I have noticed this issue. When my phone is locked, the AOD will either show for a few seconds to a minute or just won't show. I've ensured it is set to always show, power-saving not set to turn it off, no Bixby routines and any updates are installed for phone/AOD. I've even factory reset my phone and removed the case and screen protector and the issues are still persisting. Does anyone else experience this issue?
Disable all power management... it screws up all kinds of things.
Does AOD show if you tap the screen?
I have disabled all power management that I am aware of and still experiencing issues. I've set it to show on tap and while it worked the first time, subsequent taps do not show the AOD
Video demonstrating AOD tap to show issue
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
blackhawk said:
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
Click to expand...
Click to collapse
I normally use AOD always on, I'd tried the tap on the option to test. Going to try flashing it today to see if that helps despite the factory reset not helping.
So I've flashed the stock firmware back onto my device and the issues are still persisting. I've contacted support through the Samsung Members app and it's been escalated to the Research and Development team and am just waiting to hear back.
Did you update any Samsung apps after the reload before testing it? Go with the factory app loads.
Try disabling the lock screen... they tend to end up locking out the intended user anyway, sooner or latter.
If no one else is having this issue it very well maybe a hardware issue.
Did you ever wonder what happens when one or two micro transistor junctions out of the millions in a phone fail? Yes, well...
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
The you
brodieb321 said:
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
Click to expand...
Click to collapse
Did you ever get this fixed. I have the exact same issue on my s20 ultra
Edit: Nevermind just fixed it after 3 days troubleshooting. Oddly it was the the disable AOD while in power saving mode that needed to be disabled even though I don't use power saving mode. Samsung never seem to amaze me with these dumb persistent bugs.
Glad to see you solved the issue. I'd already confirmed this setting was off for me. It's still happening. Looks like it's something to do with the level of light detection as the issue only happens when I have auto brightness set for the AOD. The problem is it's not even that dark when it's happening and never occurred with my S20 FE.
I've been documenting my struggles with my lock screen in another thread. But I just had a major breakthrough and didn't want this to get buried.
To recap, my lockscreen has been a buggy mess from day one. The fingerprint sensor barely works, the fingerprint icon randomly disappears, and the gray border that's supposed to appear around the fingerprint icon simply doesn't show up. The lockscreen doesn't light up when I pick up the phone either (it stays dimmed). Also, wallpapers don't show up on the lock screen, and the big ugly clock sometimes disappears or moves itself to the top-left.
I've tried just about everything to fix this. As a last-ditch effort, I added a new user profile only to find that the lockscreen works perfectly well for this new profile (but still not for my main one).
Here's my main profile with the unusable lockscreen:
broken lockscreen of main profile
Watch "broken lockscreen of main profile" on Streamable.
streamable.com
And here's what it looks like when using the other profile:
working lockscreen on new profile
Watch "working lockscreen on new profile" on Streamable.
streamable.com
So there's clearly some obscure bug that most people aren't experiencing here. I'd love to just figure it out so I can move on.
When I didn't have the "always on display" turned on, the phone was very consistant about turning on properly when I picked it up. I ran it this way for 3-4 days without any issues.
After reading some articles on the P6, I realized that it has an AOD and that it was turned off. So I turned the AOD on while leaving all the other settings set the same. At first, the finger print icon wouldn't appear consistantly, but that is because I had adjusted the animation scale settings in the Developer settings. Changing that back to stock fixed the issue with the finger print icon not showing up.
That beings said, I have experienced the same "unresponsive" screen many times over the last couple of days that I have had the AOD turned on. The screen stays dimmed (or even turned off if I pull the phone out of my pocket) and the finger print reader is inactive (even though the icon is displayed). The screen is suppose to turn on when I lift the phone up, but it doesn't always do it. When this happens, I have to either manually turn the screen on using the power button, or double tap the screen to wake it. This is clearly a bug in the system somewhere. I probably need to report it to Google, but hopefully it is fixed soon.
After spending way too long on this, I've determined that the bug occurs consistently with these specific settings (although it may also occur for similar ones):
Lock after screen timeout: 30 minutes (or anything high enough to prevent it from locking between tests)
Power button instantly locks: disabled
Lift to check phone: disabled
Tap to check phone: disabled
Always show time and info: enabled
Replication steps:
1) Enter the above settings
2) Press the Power button to go to the lockscreen
3) Set your phone down for a couple seconds
4) Pick your phone back up and try to use the fingerprint sensor
Result: The fingerprint sensor won't work the first time.
I think all the other issues I had were actually stemming from this one issue.