Hi everyone,
With the new Huawei Mate 8 that came out a few months ago I think everyone is having some good fun with it.
But they are few issues like the screen being unresponsive (Black Screen). A solution was posted on a site (search on Goggle) which was to clear the memory on the phone and the cache partition in recovery. Personally I clear the memory on the phone, the cache partition and Dalvik cache (not sure it's the right solution).
Here is what was said on that website, credit to them.
"Boot to Recovery Mode and Wipe Cache Partition
The following steps will get the Huawei Mate 8 into Recovery Mode by booting the smartphone:
Press and hold the Volume Up, Home, and Power buttons at the same time
After the phone vibrates, let go of the Power button, while still holding the other two buttons until Android System Recovery screen appears.
Using the “Volume Down” button, highlight “wipe cache partition” and press the Power button to select it.
After the cache partition is cleared, the Mate 8 will reboot automatically"
I was on Simply ROM and it was very bad. I have changed to International B107 with KangVIP it was fine until last week (18/04/16) when it started again.
I wanted to gather solutions under one roof.
So I wanted to know how many people are affected by it and what what are the solutions?
Nobody apart from me and Zyklo have this issue? Are we really the only one in this world?
Anybody got a solution. Come on guys...
Do you have smart cover and DT2W enabled? If yes, that could be the issue.
I was on stock rom. Then for using xposed I installed Kangvip rom. It was all good and fine and then I was on the phone call with my gf. All of a sudden the screen went black. Not pure black but something like Grey. The phone was hot as hell. Or maybe it was because of the call. Strangely though I was still able to talk. The call was going through. After about 2 minutes or so. My phone restarted itself. And since then no issue. But its been a day only yet.. And no the cover is not checked. It Def something else.. Maybe themes??
ok now, to tell the truth, it has happened to me for last 1 day, quite a few times. mostly during calss and smart cover. any solutions??
Disable smart cover / disable DT2W. Only way to solve it, for now. Later updates might resolve the issue.
I was root and after reinstaling stock rom the issue dissapeared. I think it is because of "double tap to wake".
I'll do more testing.
Combo DT2W and smart cover is borked. Disable one of them :good:
Hello , I also have the same problem and had not activated any of the two functions mentioned. continuing my phone with black screen even in the recovery menu . any solution?
That will be good if we could have more feedback from others.
I'm going to try both method for a few days, disable DT2W and enable smartcover, disable smartcover and enable DT2W and then disable both of them. And I will report my findings.
But do we all agree that it is 100% software related?
Hi guys,
I have disabled DT2W and enabled smartcover and so far I have seen an improvement. I will try the others settings.
I have disabled smartcover and enabled DT2W. I have seen an improvement compared to before but I got the issue twice so far. I will try the last setting. But it seems like DT2W is the issue.
I have disabled smartcover and DT2W. The black screen didn't happened at all.
So I guess we have a conclusion here. Having both of smartcover and DT2W causes problem. But it seems like DT2W is the more at fault here. Hopefully they will fix this problem in future updates.
how can i disable smart cover and dt2w since my screen is black?
Related
OK so I downloaded & installed the latest OTA update (RV23RC03; 1.057) with the power mode choices, and it has completely destroyed my touch screen response! I previously had ZERO problem with this- every key press registered on both the original ROM and the 1st update. Since the latest update, everything takes 2 or 3 presses, sometimes VERY firmly, many times still without registering. This totally sux
Is anyone else having this issue? I should note that I do have a matte screen protector on; this previously caused NO problems.
Is there an easy reasonably safe way to revert back to the 1st update (RV07RC06; 1.029)? A link and/or instructions appreciated. Thanks.
Acer, are you out there? This exact issue occurred with my A510 on its 1st update, after which it became nearly unusable for me. Since it was < 30 days I was able to return it. No such luck this time. Why are these updates doing this? It's driving me nuts!
No issues with touch on update. It seems to be running better actually.
Try to completely reset thru recovery with wipe data maybe.
More specific instructions
Itchiee said:
No issues with touch on update. It seems to be running better actually.
Try to completely reset thru recovery with wipe data maybe.
Click to expand...
Click to collapse
That's so amazing. I went from no problem at all, to I can hardly use this any more; only thing that changed was the update.
Can you please be specific about how to reset through recovery. (Step-by-step if possible) and how to wipe data.
Thanks.
You can reset data thru settings/privacy but you will lose everything and start fresh.
I'll check on the other method later on for you.
Also turn up touch sensitivity in settings/display if you haven't...
Edit - it appears that the stock recovery doesnt have those options.
You can still reset by inside ICS like above, or...
Factory Reset:
WARNING: reset will start immediately
Volume button (one dot) and Power button, once buzzes release power button and then toggle the rotation switch on and off a few times
Yes of course, I have set screen sensitivity to high. I think I'd rather go back to 1st update, rather than wipe everything (I do have a backup but it's still a hassle). I can't believe no one else is having this problem.
Any idea how to revert to last update?
Someone in a german android forum mentioned that it help on his device after the update to set the sensitivity to the lowest setting and then back to middle or high.
I tried playing with sensitivity settings, turning on/off,resetting and no luck.
I actually found the ROM from before the update on this website and flashed it as update.zip with vol +power. It worked, I now have 1.029 back and touch screen works perfectly. I'm sorry to lose power management but i think I'll stay where I am . Don't ask me about a Jellybean update; I'll want it but after this I'll be afraid to try it. If anyone has an explanation for this i'd love to hear it.
Anyone else have an issue with unlocking the phone either by the power button or fingerprint scanner? My phone at times just sits there when i try to unlock it and will sometimes restart when i press the power button again when its frozen. Anyone else have that issue?
I have the s8+ from tmobile. I tried factory resseting and even updated to the new update. No luck. Any ideas?
Same, looks like a bug in the OS
Good!!! Better than getting a faulty device. Hopefully it can be fixed soon!
Mine froze and went to black screen after i downloaded and applied new theme. And when i press the home button i can feel the haptic feedback. I tried charging the phobe but there was no light too. I just perform a hard reset with the power + volume down keys.
You jinxed me... I read this thread but didn't bother clicking on it because I wasn't having the issue...
well... just did it. iris unlock, and then I got a reset and power button wasn't turning it on for a minute.
Hopefully it will be fixed
Yep
Hello, No issues on my S8+ from Tmobile.
Do you have a theme installed that maybe is causing the delay?
I learned from other posts from xda, when doing a factory reset, do NOT perform a backup and restore for apps. This causes some delays in response from the phone. Is better always to install fresh the apps from the app store and then just log in.
I also recommend enabling the developer options and disable all three animations to off. This will speed the phone response.
jdanielsantiago25 said:
Hello, No issues on my S8+ from Tmobile.
Do you have a theme installed that maybe is causing the delay?
I learned from other posts from xda, when doing a factory reset, do NOT perform a backup and restore for apps. This causes some delays in response from the phone. Is better always to install fresh the apps from the app store and then just log in.
I also recommend enabling the developer options and disable all three animations to off. This will speed the phone response.
Click to expand...
Click to collapse
No themes and installed the apps fresh on the second time. Has only happened twice since the reset so it improved. Now i just give it time if it freezes on me when unlocking so that it doesnt reboot.
I'm having an issues were using the messeges app makes my phone freeze
Now this doesn't happen all the time every time, but usually around a notification and the screen is off, I go to hit a button to turn on the phone and it doesn't respond but the touch-keys are backlit. If Always-on Display is on, the screen is black regardless, not even showing the time or notifications. The only fix is waiting ~10 seconds for the phone to respond, which in some cases can be the difference between a missed call.
Now, seeing Always On Display off like that while it should be on made me think back to when I saw some sort of Nougat optimization setting that allowed me to select Always On Display, and as far as I remember, I did. That makes me think this process is killing AoD and it is taking that long to start back up, where the phone won't unlock until AoD (is back on and) can confirm that it's trying to wake up out of that state.
However, I don't believe this is the issue. I have turned off AoD and the issue still happened directly afterward, after a Messenger notification. This is stock firmware, however it is not factory firmware. I believe I downloaded it from Sam-Mobile, and they had the 7.0 Nougat upgrade that I would have gotten OTA with the factory firmware anyway.
Somehow I don't think it's the flashed firmware that is the problem, however please let me know if that's a possibility.
While the phone (or whatever) is hanging, I can still hold down the power button and I will feel haptic feedback as if the power menu has opened, and when the phone responds the power menu will be open, so the phone does still receive input. It just doesn't seem to act upon it or wake the screen properly. Is this perhaps merely a known Nougat bug or is it a glitch with my flashed stock firmware?
I'm sorry I don't have much more information. I do have Greenify, but I don't think that can or is set to disrupt anything that would affect the phone waking, or that would hang the OS, homescreen or whatever it is.
I haven't done other troubleshooting because I don't know what direction to attack this from, and that is why I have come here.
Help please!
Thanks in advance. :good:
UPDATE: It seems to happen directly after my screen shuts off from being on. So, if a notification wakes my phone but I don't interact with it in time and the screen goes off, when I press the power button it won't respond for ~10-15s. That's all I've really noticed... Anyone else have this problem??
BUMP.
Also, the same thing happens if I press the power button on my phone (by accident) and then go to turn it back on almost immediately - it won't respond for a while.
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
*Detection* said:
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
Click to expand...
Click to collapse
Won't be factory resetting unless I plan to root or something. I'll fiddle with the keep screen off setting that I do have on, and I highly doubt gestures would affect it but regardless I haven't enabled or used any. Thanks for the reply.
So the "Keep screen off" setting didn't affect anything. I turned Always On Display back on and I see the same issues. However, now sometimes I notice when I lock my screen or it shuts off, sometimes the AOD will appear and then quickly disappear, and stay in this hanging state for 10-15s. Then, if I haven't touched it during that time, the AOD will reappear. Any ideas? :/
So nobody else has this issue? This is still a problem, even if I press the power button and sometimes I'll want to turn it back on again as I just remember something to do before putting the phone away, it hangs on black for too long to be useful in that moment. The only potential solution is a factory reset?
Even if I lock the screen... If I try to turn it back on too soon, and I think it's specific timing... I have to wait 10-20 seconds. Sounds and vibrations still work.
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Kilva said:
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Click to expand...
Click to collapse
This happens for me also as a point of interest.
I am hoping that O solves it, since the monthly updates have never helped.
I haven't had this happen since upgrading to Oreo a week ago, so far so good!
An hour or so ago everything worked fine, and then I updated my playstores pending apps (only Fleksy was pending) and the "force touch" feature of the phones seems to have completely stopped working, no matter what setting I turned on or off it didn't work...
Anyone has a clue as to what can cause this?
General notes:
1. Using stock Exynos unlocked variant
2. I am using package disabler (which btw didn't improve much my battery life, but that might be just me using the phone too much ) so maybe one of the packages decided that it depends on a disabled one?
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
RazoE said:
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
Click to expand...
Click to collapse
Mine also stop working after I restart my S8 Plus, it will again work if I wait around 20 minutes. Is this software or hardware problem? Any solutions?
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Ady1976 said:
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Click to expand...
Click to collapse
How does it act up on your part? Mine would just stop working if I restart the phone & I should wait sometimes hours before it would work again.
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Ady1976 said:
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Click to expand...
Click to collapse
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
bladefrost said:
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
Click to expand...
Click to collapse
Unless your phone is unlocked no pins etc the phone will just go to the lockscreen, it's a useless feature, most people have the phones locked and thus it's a complete waste of time, it sounds to me the capacitive home button part of the screen was an afterthought because they couldn't install the fingerprint reader under the screen, just had a software update yesterday and still can't turn it off, basic stuff Samsung should enable an ON/OFF toggle switch for this.
Had the same problem with my S8 Plus India Variant(SM-G955 FD), I got my screen replaced from service center, Device was not rooted back then, so was under warranty.
But it is an hardware issue, as since then it has never gone off.
I mean when I press the home button hard it doesn't wake the phone up & no vibration. It happens when I restart the device then it would stop working for few minutes to a few hours sometimes, then it would start working again normally until I restart the phone again. I think this is just a software issue.
Good morning, i have a Note 20 Ultra exynos version and when i test the proximity sensor i have no response. It's possible ??
Thanks
yes, it is implemented differently. it works fine with apps that support it
What do you mean by "test"?
When you're on a phone call it should turn off the screen if you cover the sensor.
No if i cover the entire note the screen is always on.
trismet said:
No if i cover the entire note the screen is always on.
Click to expand...
Click to collapse
Using the mic not in speaker phone mode?
If so it sounds like it's not working... phone screen should go dark when it's against your face on a call.
Try clearing the system cache on the boot menu, this may fix it.
Try it in safe mode for the off chance a 3rd party is the cause.
When i try with a call it seems to work but after two or three attempts the screen remain on also if i close the cover..
trismet said:
No if i cover the entire note the screen is always on.
Click to expand...
Click to collapse
trismet said:
When i try with a call it seems to work but after two or three attempts the screen remain on also if i close the cover..
Click to expand...
Click to collapse
Not sure but that sounds like software.
You said cover as in a wallet case?
There may be a setting for that but if so I have no clue.
Doesn't sound like a normal operation unless it's a Samsung case and it's suppose to do that.
Don't think there's even a visible specific system apk for it. You could try clearing the Android Systems cache maybe data too but that may cause more trouble with lost settings... and end up worse off for the trouble.
On the note 10+ a small faint blinking circle is visible about a quarter inch to the right of the front cam cut out when the proximity sensor is active. Not flashing, not active.
If that helps you any...
Note: if it's active during a call and I trip it 2-4 times with a second or two spacing, the screen will remain off until I turn it back on.
This is normal operation.
Ok thaks a lot for your explanation..
I'm having the same issue which started today. Every time I put the phone up to my ear to place/ receive calls the proximity sensor isn't working and I'm pressing all random buttons accidentally with my cheek. I've turned my phone on and off to try to get it to work and no dice. It was working fine before today so I'm not sure what happened. I didn't drop my phone or anything. A google search showed this has been a problem since the S10 when Samsung embedded the sensor under the screen and dropped to turn on/ off this feature under call settings.
Advice anyone?
Try in safe mode. If it works there it's most likely a 3rd party app.
Was -anything- updated or just installed?
Did you change any settings?
Try a "hard" reboot and clear System Cache in boot menu.
Clear Android Systems cache.
blackhawk said:
Try a "hard" reboot and clear System Cache in boot menu.
Clear Android Systems cache.
Click to expand...
Click to collapse
Is a hard reboot restoring everything to factory settings? If not can you provide me the steps I need to complete to get there and If I need to back up everything and how to go about doing that? I'm a novice who's learning everyday so I appreciate your patience
dj24 said:
Is a hard reboot restoring everything to factory settings? If not can you provide me the steps I need to complete to get there and If I need to back up everything and how to go about doing that? I'm a novice who's learning everyday so I appreciate your patience
Click to expand...
Click to collapse
No! Not a hard reset!
Hard reboot simulates pulling the battery...
I think I got it to work again. Hard reboot I guess according to google is pressing the “Volume down” and Power / lock key for 10 to 20 seconds bypassing the options shown on the screen until the phone turns off by itself. I then pressed the volume up key and the power/ lock key until the android recovery menu came up on the screen. I then chose "wipe cache Partition" and rebooted the phone after that.
It seems to be working again and hope this helps anyone who starts encountering this problem like I did.
dj24 said:
Is a hard reboot restoring everything to factory settings? If not can you provide me the steps I need to complete to get there and If I need to back up everything and how to go about doing that? I'm a novice who's learning everyday so I appreciate your patience
Click to expand...
Click to collapse
dj24 said:
I think I got it to work again. Hard reboot I guess according to google is pressing the “Volume down” and Power / lock key for 10 to 20 seconds bypassing the options shown on the screen until the phone turns off by itself. I then pressed the volume up key and the power/ lock key until the android recovery menu came up on the screen. I then chose "wipe cache Partition" and rebooted the phone after that.
It seems to be working again and hope this helps anyone who starts encountering this problem like I did.
Click to expand...
Click to collapse
Clearing the System cache can fix a lot of Android voodoo gremlins. I clear mine regularly or if the Android is acting erratically.
Hello
I am the owner of a Note 20 Ultra starting today.
I previously had a Note 10 Plus, where the proximity sensor showed as a blinking white light near the front camera.
At Note 20 Ultra there is no sign of its presence, no blinking light. Is this normal? Can the real owners check and confirm?
I also checked with secret codes:
Using *#0*# and selecting Sensor opens a menu where I cant find any proximity sensor
Using *#77692# opens a window with proximity and light sensor; for proximity sensor I turn on and wave my hand over the front camera area, it vibrates and turns display green each time, but after several attempts (7-8) it stops working.
So, is this normal? It has a new algorithm or type of sensor?
Please check and confirm.
Thank you
ionutdicu said:
Hello
I am the owner of a Note 20 Ultra starting today.
I previously had a Note 10 Plus, where the proximity sensor showed as a blinking white light near the front camera.
At Note 20 Ultra there is no sign of its presence, no blinking light. Is this normal? Can the real owners check and confirm?
I also checked with secret codes:
Using *#0*# and selecting Sensor opens a menu where I cant find any proximity sensor
Using *#77692# opens a window with proximity and light sensor; for proximity sensor I turn on and wave my hand over the front camera area, it vibrates and turns display green each time, but after several attempts (7-8) it stops working.
So, is this normal? It has a new algorithm or type of sensor?
Please check and confirm.
Thank you
Click to expand...
Click to collapse
Its possible that there is no sensor, I have not done any research on this but it is possible to use front camera as proximity sensor. It would mean that the function would activate when you are on call and not on loudspeaker, it should not be tough to implement.
It has a discreet proximity sensor...
https://us.community.samsung.com/t5...ingerprint-and-proximity-sensors/td-p/1394254
blackhawk said:
It has a discreet proximity sensor...
https://us.community.samsung.com/t5...ingerprint-and-proximity-sensors/td-p/1394254
Click to expand...
Click to collapse
I have seen this article but it is useful only to locate the proximity sensor. But regarding how it is actually working, there are no details.
I was expecting something similar with Note 10 Plus but there was no blinking led/pixel to be found when having a call.
And honestly, I am not very impressed with its functioning. When using phone on left ear especially it skips activating many times.
Also, during a call (normally not on speaker), when I cover the top of the phone with my hand, the screen does not go black instantly (I must keep it covered about 3-4 seconds) but if I puck up the phone to my ear it seems to activate, which makes me think it has an algorythm that includes other sensors like gyroscope. Or maybe my proximity sensor is faulty... but as I said, if I test it with proper code, it seems to be present and work.... Which makes me thing it is a software problem.
So, I come back to my previous details and kindly ask other Note 20 Ultra users to replicate similar behaviour.
Thank you
My note 20 Ultra sensor works fine if the speaker is off. Turn the speaker on and the proximity sensor is disabled.
Try using this code in dialer.
*#77692# and then turn proximity sensor on and put hand over top part if it lits up green then it's working as it should. But if it remains white and nothing happens then there is an issue with sensor.
Skickat från min SM-N986B via Tapatalk