I know there are tons of threads complaining about the display, this isn't one of them.
I had a droid x2 and didn't really have any issues with the display and recently upgraded to the bionic.
The specific issue I've noticed is that after restarting my phone the display is fine (I don't notice the cross hatching) when I do notice it is after locking/unlocking my phone.
I'm not sure if its just my phone... Anyone know if there is a way to fix it or what might be happening behind the scenes following an unlock?
Related
Hey guys, I've been off the forums for about a week or so now...can anybody briefy bring me up to speed regarding the issues of the wifi bug, and the auto rotation bug? From what I very hastily just skimmed, I didn't see anything indicating there has been a fix yet. Is there at least any news regarding the status of these issues, and when they may possibly be fixed?
I'm quite fond of ROM flashing, and we all know our small Droid 4 following is pretty limited in the amount of dev support it recieves, compared to several other phones; and continue to appreciate the few devs that have remained faithful to providing the Droid 4 with the few ROMs it does have. So, the not being able to use any custom ROMs because of these few critical glitches has been horrible.
Any insight from anyone on the status of these issues would be much appreciated. Thanks.
Hello,
Sorry to but in, but I'm also experiencing an issue with the Accelerometer not producing any data. I can only switch to landscape mode by sliding the phone open, but I have to turn the screen off and back on to restore back to portrait. Not a huge problem, but one I'd love to see a fix to. Any updates on this would be appreciated. Thanks.
if your on CM10 download his latest version. This should have a fix
Hello,
I on lollipop (soak test) build on my moto maxx. It was working great until one day there was no vibration. The vibrator wasn't working at all. The phone then was super laggy. Every action took a good 2-3 seconds to execute.
2 reboots failed to fix it. A final 3rd reboot fixed the issue. I have not faced the issue since.
I don't really know what the issue was about but it was annoying.
I just want to put this out there because there was not a single post about it.
Cheers !
- Navneet
Problem persists
After the official 5.0.2 update..things were looking good for a few days.
The vibration issue is back and it takes numerous restarts to get the vibrator to start working again.
There is nothing about this anywhere else. I've tried safe mode and it doesn't seem like a software issue.
A lot of Motorola users (Droid MAXX and few others) have been complaining about vibrator motors being faulty which just shows the quality of parts being used here.
Verizon has been replacing the motors or handsets if within warranty. However Motorola doesn't seem to acknowledge the issue.
Anyway this is my last Motorola device. I've picked up an S6 Edge and extremely happy with it.
rednav said:
After the official 5.0.2 update..things were looking good for a few days.
The vibration issue is back and it takes numerous restarts to get the vibrator to start working again.
There is nothing about this anywhere else. I've tried safe mode and it doesn't seem like a software issue.
A lot of Motorola users (Droid MAXX and few others) have been complaining about vibrator motors being faulty which just shows the quality of parts being used here.
Verizon has been replacing the motors or handsets if within warranty. However Motorola doesn't seem to acknowledge the issue.
Anyway this is my last Motorola device. I've picked up an S6 Edge and extremely happy with it.
Click to expand...
Click to collapse
never heard about this issue, try installing official firmware from rsd, to play safe.
So recently, mostly on swipe enabled keyboards, I have been seeing a ghost swipe register when typing. This happens on all keyboards I've used so it is not a keyboard issue. I saw someone on reddit recently with the same issue and was wondering if it had been reported prior for this phone. I'm coming from a nightmare experience from the OPO's touchscreen so I'm here looking for advice.
I started to notice it about a week ago when texting. At certain occasions, it could act as though i was dragging my fingertips instead of individual taps. Now I have tried this with and without a screen protector and gotten the same issue. I have also only been using 5.1 since I got this phone, so I cannot say that it is an issue with the software since I have nothing to compare it to. I device is unlocked but not rooted and is running the D revision of 5.1.
Anyone seen this corrected, or should I just go ahead and RMA. My phone was built on 3/7/2015 so it is still very new.
EDIT: RMA'd.
Hi, sorry if this was posted before, but with XDA moving to XenForo, search seems messed up, i did several searches and nothing comes up for "flicker" in this whole Pixel 4 XL Forum...
Has anyone else dealt with the low brightness screen flicker? I know it can't be just a bad phone, since i just bought three pixel 4 XL phones and they all exhibit this same behavior.
They are all running LineageOS (Official builds) so I don't know if this just affects the ROM or stock as well (although I've read it might affect stock phones too elsewhere).
It makes the phone pretty difficult to use in very low light situations, the screen will constantly flicker (more noticeable on darker backgrounds).
At first I thought it was just the Opera browser (as that's what I prefer), but it's operating system wide... Apps like "Darker" help.... because you can crank up the phone brightness and use a filter to dim the screen.... but it doesn't get the top & bottom menu/buttons, so those remain like spotlights in your eyes with that workaround.
Just curious if anyone knows whats up with this... it's the only phone I've ever seen this behavior on (and i've used Pixel 1,2,3 XL phones all with Lineage, and a myriad of other devices back in the Cyanogenmod days.... I've never seen a screen flicker issue like this).
Thanks for any help
edit / update-
the pro version of "darker" app works to fix this.... you crank the phones brightness to 100% and with the pro version you can dim the rest of the interface.
hopefully this helps anyone else suffering from this HUGE flaw (again i don't know if its just LineageOS or not, i didn't run stock on these except to unlock bootloader etc)
Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.
edwinek said:
Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.
Click to expand...
Click to collapse
hmm.... you running stock i guess? i don't see smooth display option in lineage
Hi everyone, I know this may be a rather silly question, but from what I saw, not all devices (S9/S9+) were affected by the green screen bug due to the software error. Has anyone tried to "catch" software from one of these unaffected devices and test it on one that was affected? So far, we still have no official statement from the company and a problem with cell phones. I tried several roms and they all gave me the same error on the screen :/
RennorFithel said:
Hi everyone, I know this may be a rather silly question, but from what I saw, not all devices (S9/S9+) were affected by the green screen bug due to the software error. Has anyone tried to "catch" software from one of these unaffected devices and test it on one that was affected? So far, we still have no official statement from the company and a problem with cell phones. I tried several roms and they all gave me the same error on the screen :/
Click to expand...
Click to collapse
I've installed OLED Saver to go around this bug.
I wanted to learn how to downgrade the version, this happened after the Sep 18 update for me.
RennorFithel said:
Hi everyone, I know this may be a rather silly question, but from what I saw, not all devices (S9/S9+) were affected by the green screen bug due to the software error. Has anyone tried to "catch" software from one of these unaffected devices and test it on one that was affected? So far, we still have no official statement from the company and a problem with cell phones. I tried several roms and they all gave me the same error on the screen :/
Click to expand...
Click to collapse
Bloody annoying, only way to solve it for now is to set always on display to on, then when screen is off you have to tap screen to come on then unlock with fingerprint, phone screen is now perfect.
This proves a software bug all along.