I updated to 5.0 a while back when Rogers rereleased it, and every once in a while the numbers/letters on the lockscreen keypad will turn to white blocks. The lock screen is the only place that this happens.
Anyone know what's wrong/how to fix it besides rebooting the phone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bump!
Anyone has a better solution than reboot?
It is appearing on T-Mobile I-9505, I-9515 and G-900F.
Do you use SwiftKey? My girlfriends Canadian GS5 is doing this as well, when I searched the internet I found a reference with regards to SwiftKey not playing 100% nice with Lollipop and causing this blockyness on the lock screen. So far there has been no fix other than reboot... She's been a couple of months now with this annoyance, but luckily it doesn't seem to affect the usability, you just have to know which numbers are which Side note: I have a Nexus 5 and use Swiftkey but don't have this problem.
This is apparently just a general lollipop issue, not really tied to anything just a glitch in android, i dont know a fix just thought id throw that out there.
Sent from my Tw5ted SM-G900A using Tapatalk
Related
Well, it started yesterday and it keeps driving me nuts. It's present both in the system as well as 4ext or even the splash screen so it is definitely a hardware issue. Is there any way to get rid of them because my contract ends in november but I was going to stay with my DHD and get myself a PS3 (very nice offer from my carrier)
It looks like that, it's not a screenshot but it looks exactly like that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what seems to be an officer problem?
the faint horizontal lines on the screen. That is only a picture but live they also flicker.
You could try replacing the screen yourself, but it could happen that the gpu is the problem, in which case you can't do anything on your own...
Sent from my Desire HD using xda app-developers app
I remember having the same issue right after I bought my DHD and I remember rooting and reflashing it helped I recently changed my Radio software, you think it might have anything to do?
It's not hardware. I get it on the current versions of the 3 kernel. Synergy said it was to do with fb (not sure what it is) and he's working on it.
http://forum.xda-developers.com/showthread.php?p=30407780
FB....hmmm....frame buffer (only thing that comes to mind except FaceBook) Anyway you're a life saviour man! I was worried that I will have to get a new phone.
Hi all,
I've been having a problem with S View over the past few days. When ever the screen changes (like when trying to unlock the phone in S View), it gives this weird ghosting effect, like in the picture below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has anyone else got this issue, and/or has anyone fixed it?
Sent from my Samsung Galaxy Note 3 N9005 using Tapatalk.
BodenM said:
Hi all,
I've been having a problem with S View over the past few days. When ever the screen changes (like when trying to unlock the phone in S View), it gives this weird ghosting effect, like in the picture below:
Has anyone else got this issue, and/or has anyone fixed it?
Sent from my Samsung Galaxy Note 3 N9005 using Tapatalk.
Click to expand...
Click to collapse
On 4.3 yes I experienced it.
Since upgrade to 4.4.2, the issue has gone.
Sent from N9005 NC2 ROM.
Hi guys,
I have a LS980, right now running Slimkat, but was using Cloudys G3 rom.. Anyways since I moved from stock (had 4.4.2 rooted) , when I'm in direct sunlight or another strong source of light and I unlock my phone the screen doesn't get bright, it just stays really dim at the point is not possible to see it, I have to lock it and unlock it multiple times, or reboot to get it to work.
I've tied moving from manual to auto brightness back and forth, but issue is still there, it just seems the light sensor (?) is not working appropriately and it just stays dim.
I've tried flashing the kitkat baseband as suggested in Cloudys thread.. Clean install both Slimkat and G3 ports but still the same. Issue was not happening when I was running stock.
Any ideas or suggestions? Has anybody have this issue?
Something else I noticed, is that my baseband shows unknown even if I flash kit Kat baseband again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I went to setup Android Pay and got this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wiped Android Pay's app data and same results. So I ran a SafetyNet test and it failed.
I'm obviously not rooted or bootloader unlocked. I remember it working before. Any ideas why it won't? Anybody else on G935TUVU2APC have this issue? I'm hoping I don't have to wipe my device via Odin and start over...
EDIT: PROBLEM SOLVED. APPARENTLY USING THE CONDENSED DPI OPTION BREAKS IT. SWITCHING BACK TO STANDARD VIEW FIXES IT.
Sent Via My Samsung S7 Edge
Did you happen to change your dpi?
Just through the Samsung hidden settings. Could that be it?
Sent Via My Samsung S7 Edge
daveid said:
Did you happen to change your dpi?
Click to expand...
Click to collapse
Wow, thanks, that was it. Lmao sucks but I guess if I use Android Pay I'll revert to the standard DPI. Good to know.
Sent Via My Samsung S7 Edge
First a week ago i picked up my s7 edge g935f on 8.0 im in the u.k and the return and recents buttons wouldn't work i tried all kinds im having to use the virtual keys, now i have ringtone, alarms, notification sound but no sound on calls unless i put it on speaker and its still bad, no music will play or sound on videos, now i just used a hidden code to go see info on touch keys and its not even there, ive put two screenshots of how it should look with keys button in middle and mine with it missing, any help would be amazing, thenk you in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL]
[/IMG]
Nobody ?
Nobody know how i can fix this ? If nobody in here knows i've got no chance i've had galaxys since the s3 but i've had enough now, i'm so sick of ota updates supposedly to better your phone putting more problems instead, i've had enough, i had no problems with s3, s4,s5, but the more the phone is meant to improve and the more you pay for it the worse they get, NEVER getting another galaxy.