Hi all,
Anybody else has the gray overlay issue persist in their lock screens when using fingerprint unlock after the 5.1.1 update? Read up on it and some people still have that issue. Switching from swipe to fingerprint doesn't solve it for me like the other threads. It seems like the gray overlay just gets inserted a few moments after I wake the screen so not sure if it's something changeable somewhere in the settings.
It's much more noticeable when I use a black lockscreen wallpaper, and only when using a secure lock screen. Attaching screens shots for your reference. First one is on a Dynamic Notifications screenshot with the pure blacks, second is the system default with the grays.
I'm on 5.1.1 build LMY47X.G920FXXU2BOFO on what I think is an XTC (Generic Philippines) FW. Used to be on a Telcom firmware (GLB).
Hope you guys can help! I'm willing to go as far as root my phone and take out a file that's responsible for the overlay if that makes a difference, but hopefully there's an alternate method.
Thanks!
See post #8 in the following link and it will show you how to fix this. I had the same issue and used this solution and it works perfectly...
http://forums.androidcentral.com/sa...ock-screen-wallpaper-darker-than-default.html
Good luck...
yiannisthegreek said:
See post #8 in the following link and it will show you how to fix this. I had the same issue and used this solution and it works perfectly...
Good luck...
Click to expand...
Click to collapse
Nope, tried this method already but the tint still persists. This is too frustrating even if it's a small thing.
Were you able to find a solution to this issue? I remember reading about a rooted method for solving this but i cant find that post now.
Same issue here on edge plus
There's an xposed module for this I believe.
I'm having the same problem on my Note 4 running 5.1.1.
Using the xposed module did help.
heartog said:
I'm having the same problem on my Note 4 running 5.1.1.
Using the xposed module did help.
Click to expand...
Click to collapse
whats the name of the module?
kisetsu17 said:
Nope, tried this method already but the tint still persists. This is too frustrating even if it's a small thing.
Click to expand...
Click to collapse
GOD SO MANY PEOPLE, including me, ARE HAVING THIS PROBLEM AND NO ONE KNOWS A DAM FIX
---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------
kisetsu17 said:
Hi all,
Anybody else has the gray overlay issue persist in their lock screens when using fingerprint unlock after the 5.1.1 update? Read up on it and some people still have that issue. Switching from swipe to fingerprint doesn't solve it for me like the other threads. It seems like the gray overlay just gets inserted a few moments after I wake the screen so not sure if it's something changeable somewhere in the settings.
It's much more noticeable when I use a black lockscreen wallpaper, and only when using a secure lock screen. Attaching screens shots for your reference. First one is on a Dynamic Notifications screenshot with the pure blacks, second is the system default with the grays.
I'm on 5.1.1 build LMY47X.G920FXXU2BOFO on what I think is an XTC (Generic Philippines) FW. Used to be on a Telcom firmware (GLB).
Hope you guys can help! I'm willing to go as far as root my phone and take out a file that's responsible for the overlay if that makes a difference, but hopefully there's an alternate method.
Thanks!
Click to expand...
Click to collapse
Were you able to find a fix at all?
Prandals said:
GOD SO MANY PEOPLE, including me, ARE HAVING THIS PROBLEM AND NO ONE KNOWS A DAM FIX
---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------
Were you able to find a fix at all?
Click to expand...
Click to collapse
Not on 5.1.1. It never went away but when I upgraded to 6.0.1 the light gray tint isn't there anymore.
Related
I installed the Blaze 3 Rom, and it seems to be working fine except for when the keyboard comes up sideways its black on black and cant see anything. Is anyone else having this issue with this rom? If not any ideas on why I am getting it black on black so I cant see any of the letters on the keypad. Only happens when I have it tilted long ways.
they said that they are working on fixing that issue. Your options really are to either get something like swiftkey x or a new keyboard outside of the rom or you could revert back until they fix it. i just checked my phone and multi-touch looks fine with messaging pro.
---------- Post added at 01:05 PM ---------- Previous post was at 12:58 PM ----------
they apparently fixed it
"This flashable zip will fix the blacked out keyboard in land issue and also fixes the black on black text in menu,now its black on blue. flash in cwm recovery.this is not a restore."
http://forum.xda-developers.com/showthread.php?t=1550693
i'm going to flash it on now and test it now.
Thankd for that info. Going to have to try that out once I get home and can do it.
the update makes the background of the black to be blue so its fixed just looks a little weird. but yea glad i could help.
Thought I would check if there was an OTA update for my GEM 702 & lo & behold here is B006.
The update say stability improvements, application compatibility & a merge with google ??
Just in the process of updating now - will let you know what I find after the update.
What have others on GEM 703 to say about B006 ??
Thx Paul
OK well the upgrade does not appear that exciting.
EMUI 3.0.5 & Android lollipop 5.0.1
Occasionally I would see App crashes on B003 & had issues with USB default accessory never letting go once default was set; so hopefully these are fixed - otherwise I am not seeing any advantage.
Regards
Paul
It fixes the bug where if you had the screen lock set you couldn't give notification access to applications like Android Wear or Pebble Time. I should think so too if they want you to buy a Huawei Watch!
Don't know if it's related, but my camera stopped working after the upgrade a couple of days back. Didn't use the camera until morning.
P. s. Dunno why but the camera just woke up out of nowhere. So just note above issue but it went away. Phew!
tweety889 said:
Don't know if it's related, but my camera stopped working after the upgrade a couple of days back. Didn't use the camera until morning.
P. s. Dunno why but the camera just woke up out of nowhere. So just note above issue but it went away. Phew!
Click to expand...
Click to collapse
Camera is supposed to autostart at boot so maybe a few reboots helps?
---------- Post added at 12:29 PM ---------- Previous post was at 12:29 PM ----------
BIG Question:
Does the OTA blow away root?
Did the OTA on my GEM-702L. No big change, indeed.
I'm experiencing some issues with this Mediapad.
First is with the lock screen and home screen. I use ultimate rotation in order to have those creen in portrait or lanscape mode, according to the position of my mediapad.
It worked ok (while the landcape mode was showing only the top of the portrait screen with less visible lines), and suddently stopped. Now those screen stay in portrait mode, while "rotation" say "forced". And auto rotation is "on". Don't know what happened.
Too, i have some programs set to start on boot. Like Last pass, rotation, flip cover etc...
But at each boot I am obliged to reset the activation under "accessibility". (Adblock +, Last pass, rotation). Boring !
Last, no way to set the proxy for Ad block+ it stay greyed...
Any idea ?
Rudolpht said:
Camera is supposed to autostart at boot so maybe a few reboots helps?
---------- Post added at 12:29 PM ---------- Previous post was at 12:29 PM ----------
BIG Question:
Does the OTA blow away root?
Click to expand...
Click to collapse
Mine wasn't rooted, but the camera problem didn't go away as I would have wanted. It came back and forth, i.e. worked once in a while but will go blank soon after. Google camera can't work at all.
If you use SD Maid you can tell if the camera is autostarting at boot, but no real good advice.
Still interested if anyone rooted took the OTA and what happened?
I just got my mediapad x2 in Monday, and did The update right away. So far so good no app crashing or any odd behavior, this phablet is really good.
Mine is a X2 Gem-702L non root.
I upgraded my 702L to B006. Don't know what's changed apart fom android is now 5.0.1.
Just means I have to downgrade to B003 to be able to upgrade to a 703L
Did anyone install the new PK7 watch update on their Gear S3? Any issues with AOD? Like AOD not working or turning off despite the AOD setting being on?
Sent from my SM-G935P using Tapatalk
Installed PK7 yesterday. AOD working fine for me.
---------- Post added at 12:13 PM ---------- Previous post was at 11:29 AM ----------
I TAKE IT BACK!!! After I put that last response, I switched between some watch faces I had made, and noticed the AOD was flipping back to the previous watch face when it dimmed. Strange. So I switched again, and same thing. Figured maybe a reboot would fix it.
Rebooted and tried another face I created (with GWD) - IT CRASHED THE WHOLE WATCH. The AOD dimmed face for this one face is distorted, and when I wake it up, the screen goes black. Unable to do ANYTHING with the watch. It will dim back to the distorted face, but wakes to all black. Rebooted and tried again - same result. Only way to recover my watch was to reboot and switch faces before it dims.
So I'm hoping it's just a corrupted file on that face - the other ones seem to be working again. but the wrong AOD screen before, and the "soft bricking" now, along with your comment that you've had issues makes me wonder...
I installed PK7 yesterday also. Everything working fine.
After reading this thread I tried changing faces and letting it dim. Still no issues for me.
---------- Post added at 12:05 PM ---------- Previous post was at 12:02 PM ----------
Forgot to mention my usual watch face is one I made with GWD. Switched between it and several I downloaded or came with the watch and can't re-create either of your problems.
Yeah, I've tried out all my other faces - downloaded, stock, and personally made. No more problems. Some reason it's just that one that is causing the crash, so I'm leaning more towards that one being corrupt and the culprit. Just tried it again, and it crashed again. Just weird that I found it immediately after reading this thread! See attached picture...
arl16 said:
Installed PK7 yesterday. AOD working fine for me.
---------- Post added at 12:13 PM ---------- Previous post was at 11:29 AM ----------
I TAKE IT BACK!!! After I put that last response, I switched between some watch faces I had made, and noticed the AOD was flipping back to the previous watch face when it dimmed. Strange. So I switched again, and same thing. Figured maybe a reboot would fix it.
Rebooted and tried another face I created (with GWD) - IT CRASHED THE WHOLE WATCH. The AOD dimmed face for this one face is distorted, and when I wake it up, the screen goes black. Unable to do ANYTHING with the watch. It will dim back to the distorted face, but wakes to all black. Rebooted and tried again - same result. Only way to recover my watch was to reboot and switch faces before it dims.
So I'm hoping it's just a corrupted file on that face - the other ones seem to be working again. but the wrong AOD screen before, and the "soft bricking" now, along with your comment that you've had issues makes me wonder...
Click to expand...
Click to collapse
pk7 was pushed to you?
Yes model and location would be good info. I have AT&T LTE SM-R765A and have checked for updates. None available. it says I have the most update software.
I have been trying out a number of watchfaces. Noticed that this distortion tends to happen only to light coloured watchfaces (some, not all).
highaltitude said:
Yes model and location would be good info. I have AT&T LTE SM-R765A and have checked for updates. None available. it says I have the most update software.
Click to expand...
Click to collapse
I have the T-Mobile version (Model: SM-R765T Version: R765TUVU1APJ9). We will not get this PK7 update in it's current form. We have different versions due to our models being LTE and with a carrier. The Carriers will release a version for our S3s.
w00t!
Linky here
XDA user yshalsager has grabbed the download and provided a link to it
I just downloaded it - off to have me some pie fun!
Edit
I'm back! Pietastic!
The updater displays the percentage completion, gets to sixty something then reboots
You get the boot screen for a couple of minutes (during which you assume you've bricked your phone, obviously) them it springs into life and you got Pie!
Off to enjoy!
Already updated 8 hours ago.. Everything looks fine touch, in games' sound, camera etc.. Only GCam lagging as it was on Oreo
Sent from my POCOPHONE F1 using Tapatalk
Do you have the changelog please?
Gcam lagging, touch lag looks better, but on pubg the problem persists.
Shishisonson said:
Do you have the changelog please?
Click to expand...
Click to collapse
There ain't a lot, as you can see from the attached...
rodrigoxm49 said:
Gcam lagging, touch lag looks better, but on pubg the problem persists.
Click to expand...
Click to collapse
Nuts! I was just about to fire up PUBG to check
No improvement in handling of notifications either
Google launcher still isn't supported
thesoupthief said:
There ain't a lot, as you can see from the attached...
Click to expand...
Click to collapse
Ok thanks anyway
did they added back the option to hide the notch?
eilegz said:
did they added back the option to hide the notch?
Click to expand...
Click to collapse
No ?
Just found a setting to display incoming notifications, but these don't seem to persist for more than a few seconds. I can't promise this setting might not have been there before...
Waste of time if they can't be made to last - they're only gonna be noticed if you're staring at the screen when a message arrives
rodrigoxm49 said:
Gcam lagging, touch lag looks better, but on pubg the problem persists.
Click to expand...
Click to collapse
Basically the stable update used touch firmware from 8.11.15. So any optimisation the made about touches from 8.11.23 to 8.12.7 is totally useless.
Keyboard lag is back.
PUBG delayed aiming where you can't register small swipes is back.
Laggy edges is back.
But on the bright side screen flickers and laggy nav bars is fixed tho
thesoupthief said:
Nuts! I was just about to fire up PUBG to check
No improvement in handling of notifications either
Google launcher still isn't supported
Click to expand...
Click to collapse
yeah the notification issue still persists.. the status bar notif icons only appear for 2 secs and then bye bye.. not much improvements
Can it be flash through twrp or fastboot??
Chrome is also lagging on Pie Stable
I have boot loader unlocked, twrp and magisk installed in miui 10.0.6.0 stable..can i flash this stable pie using TWRP.what will be step
Updated
Will it keep on receiving OTA?
---------- Post added at 03:54 PM ---------- Previous post was at 03:48 PM ----------
mameenbh said:
Updated
Will it keep on receiving OTA?
Click to expand...
Click to collapse
I have also noticed that a lot of new software is there like Opera, UC Browser, Netflix, Skype, etc.. which were not there during the phone's initial setup on Oreo
Coming from Oreo (never tried the betas, I don't have time):
They have FINALLY improved/fixed memory management. I'm getting notifications instantly and frequently from all my apps. Yay!
Although I can't get Adaway working, just shows blank screen... Possibly an incompatibility with Magisk 18.0 though, I never get superuser prompt/toast.
CosmicDan said:
Coming from Oreo (never tried the betas, I don't have time):
They have FINALLY improved/fixed memory management. I'm getting notifications instantly and frequently from all my apps. Yay!
Although I can't get Adaway working, just shows blank screen... Possibly an incompatibility with Magisk 18.0 though, I never get superuser prompt/toast.
Click to expand...
Click to collapse
Working fine here with magisk 18.
Try set root access for specific app root access in superuser settings.
Happened me same with adblock and titanium backup
mameenbh said:
Updated
Will it keep on receiving OTA?
---------- Post added at 03:54 PM ---------- Previous post was at 03:48 PM ----------
I have also noticed that a lot of new software is there like Opera, UC Browser, Netflix, Skype, etc.. which were not there during the phone's initial setup on Oreo
Click to expand...
Click to collapse
I haven't ended up with these "bonus" apps since upgrading, saving me the effort of removing them.
The inability to hide the notch is irksome, made more so by miui's tendency to kill natchonotch, despite setting up power management to keep it alive
misleaded said:
Basically the stable update used touch firmware from 8.11.15. So any optimisation the made about touches from 8.11.23 to 8.12.7 is totally useless.
Keyboard lag is back.
PUBG delayed aiming where you can't register small swipes is back.
Laggy edges is back.
But on the bright side screen flickers and laggy nav bars is fixed tho
Click to expand...
Click to collapse
Sounds like the current beta 8.12.10 is a better option than this official stable?
Can anyone confirm if otg is working in miui global 10.1.3.0? Otg is not working in my phone.
I'm facing a bug after update to OxygenOS 10.3.3.GM57AA on my One Plus 7
in deep sleep mode (long time after lock screen condition) the "tap to show" ambient display fiture doesn't work so I have to press the power button to turn the screen on.
I didn't even face that problem before update
any solution for that?
thank you
This problem has been going on since 12 beta, there is no solution yet.
When there is light, the tap works fine, as soon as it gets dark, it stops working.
Probably the sensor calibration will help, but the command *#808# does not work.
yes you are right. it seems like sensor bug
hope there will be an update for this bug
After the 10.3.3 update, in June 2020 ( India) when the phone sleeps, no amount of 'double tap to wake' wakes it up, Fingerprint scanner doesn't show and Ambient display doesn't work.
My phone model is OnePlus7 GM57AA.
---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------
Someone suggested to uninstall OnePlus launcher sand reinstall the same. Didn't help
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
meat_hooligan said:
This problem has been going on since 12 beta, there is no solution yet.
When there is light, the tap works fine, as soon as it gets dark, it stops working.
Probably the sensor calibration will help, but the command *#808# does not work.
Click to expand...
Click to collapse
At ANY TIME OF THE DAY, regardless of Night or day it's not working after Sleep
Bugs on the Oxygen Os 10.3.3
1.Portrait mode blur doesnt works fine it blurs subject also in the pics
2.deep sleep of ambient display after some times...it means double tap doesn't work you have to wake your phone with power ker as usual
is there any information about official update to fix this problem / bug?
It is really annoying problem for me
yanuarcensoe said:
is there any information about official update to fix this problem / bug?
It is really annoying problem for me
Click to expand...
Click to collapse
The problem is really annoying and has been present for some time and even in the latest beta firmware it has not been resolved, a temporary fix is possible, pending a definitive correction of the defect by oneplus, but root is required. You can find the fix here.
dianoandr said:
The problem is really annoying and has been present for some time and even in the latest beta firmware it has not been resolved, a temporary fix is possible, pending a definitive correction of the defect by oneplus, but root is required. You can find the fix here.
Click to expand...
Click to collapse
I love the performance of this phone, so I use it for my daily driver. I'm not going to root this phone because there is an app that requires non-root device.
just waiting for an update or sell this phone. haha
yanuarcensoe said:
I love the performance of this phone, so I use it for my daily driver. I'm not going to root this phone because there is an app that requires non-root device.
just waiting for an update or sell this phone. haha
Click to expand...
Click to collapse
Magisk - the root solution commonly used - has the ability to hide root from apps. You can use MagiskHide to hide root from your app after rooting the phone. Your app won't know that the device is rooted.