Database Users

Rogers S5 Lollipop lock screen block text

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

Help N935f root

My phone install SYSTEM, RECOVERY, BOOT mod error
I want root N935f, please help
{
"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"
}

You're not the only one, same for me and some other Note FE SM-N935F/DS users...
Seems like that only the Korean variant doesn't have this problem as they can just flash the standard TWRP without problems.

Anyone able to boot back to main screen without flashing stock ROM?

So there's no working root method yet for N935F/DS. Seems we have to wait for a year? Hope not. I like their phones but I hate Samsung!

toviasrepier said:
So there's no working root method yet for N935F/DS. Seems we have to wait for a year? Hope not. I like their phones but I hate Samsung!
Click to expand...
Click to collapse
Are your next 10 posts going to be the exact same as this one & the three preceding it?
Try reading the existing threads before posting identical questions/threads, it's not as if there's a lot to catch up on.......
Sent from my Sony Xperia XZ Premium using XDA Labs

There is, go read it here:
https://forum.xda-developers.com/note-fe/how-to/sm-n935f-ds-how-to-flash-twrp-root-t3733030

Update delayed if country is changed.

I bought realme 2 pro in flipkart bbd and brought it to nepal and since then it has had only one update. As seen in the attached screenshots my build ends in 06 but the latest build ends in 08. Its nearly time for new update but i am not getting even the old one.
Is this only with me or anyone else is also facing the same problem.
{
"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"
}

Same problem
I have to go back to indian region to update my Realme 2 pro. Some of the Realme 2 pro user told me to use VPN but I haven't yet got the latest November update too.

Use express vpn and change your region to india for update , try clearing data,cache of software update before use vpn
Works for other color device , try it

I got the update
Even if realme said i wouldnt get update, i got one but the annoying notification on enabling accessibility services is not fixed. I git the update normally btw... ??

Is it normal for the camera mask to cut off the screen slightly?

I recently obtained a "New-in-box" V20 and quickly got to work with unlocking the bootloader and loading Alpha Omega Rom. As I've been working with it, I noticed a couple of curiosities that make me question its newness, however, and I wanted to run this by the community to see if anybody had any insight. First and foremost, is this level of cutoff under the camera corner normal for LGs?
{
"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"
}
Secondly, the "hardware info" menu shows over 46 hours of "lifetime calls." Is that counter at all accurate, even after using LGUp to install an exploitable stock rom, Dirty Santa to set up TWRP, and then use TWRP to install the latest available Alpha Omega?
Another odd thing I spotted was that, despite the fact that it is the Verizon VS995 variant, the back cover has the B&O branding instead of the Verizon tramp stamp. Did some of the VS995s ship with this more stealthy design?
Basically, I'm trying to feel out if I have any leverage by which to request an exchange or partial refund for my "brand new" item. I'm still pretty happy with it despite the weird lineup issue, but it's one of those things that you can't exactly un-see .

Huawei Health keeps reverting to Metric (km) units (and impossible to report to Huawei)

Hey guys
Just wanted to see if I am the only person with this problem. In the Huawei Health App on iOS, I have it set to imperial units but every time I close the app from the app switcher and reopen the app, I find that it has returned to metric units even though it is set as imperial units in the settings. I tried to report this bug to Huawei but their bug reporter tool does nothing. I know that my internet isn't the problem because I am able to check for updates and trying with data it does nothing. Does anybody else have the same thing with them?
Using iPhone X on 15.2 and Honor Band 5 Latest firmware. Huawei Health App also latest.
{
"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 have the same exact issue. It will still show “Imperial “ in settings, but shows km on the display.

I just tried to submit as an issue, and got the same “Submit failed “ message as you did.

Same issue here, too. Glad you took the time and trouble to organize us. Definitely looking at another manufacturer for my next band.

Did anyone ever get a fix for this issue?