[Q] Status on CM Based ROM Screen Rotation Issues? - Motorola Droid 4

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

Related

[Q] Display crosshatching after unlock

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?

ghost swipes / input on various ROMs?

Folks,
unsure what might be causing this: I am rather frequently experiencing ghost swipes and ghost input on my Optimus 4X HD. Right now I am back to cm11 nightlies and see this behaviour same as on the stock ROM or any other ROM I tried so far. Behaviour's all the same: At some point the phone will start responding to phantom input - randomly starting applications from the launcher, randomly entering text in case I am in writing a message, randomly scrolling up or down in the current application, randomly opening and pinch-zooming-in-out pictures, ... . Usually, powering screen off and on again two or three times resolves this, but it's kinda annoying especially in situations in which the phone starts randomly making calls...
Any idea what could be causing this? Hardware issue? Defect? Dirty display? Issues with using a screen protection foil? Any input or feedback greatly appreciated.
Cheers and thanks,
Kristian
Not sure whether _anyone_ else does experience this on this device. My insights, so far, is that ghost swipes and this kind of input issues seem to be shared by other users on other devices, too, but they don't seem to appear on all devices of a certain kind running a certain piece of software. As far as I am concerned, these issues still happen then and now - but considerably less often after upgrading my p880 to another ROM (using EuphoriaOS 5.1 unofficial instead of nightly CM builds now). So if you see this problem on a p880, maybe this might help you too.

New Mi5 owner here! Does anybody else experience erratic capacitive button behaviour?

Hey there everyone, I got my Mi5 a couple of weeks ago. I flashed Slim7, but right now I use the latest Lineage OS as my daily driver.
Although, user experience has been great I faced a bug in both ROM which I believe is firmware related, but I don't really have a solution. I am not sure if it happened in stock, but in both custom ROMs that I used, sometimes the capacitive keys (back and recents) would stop working. This happened every 5 minutes or so and it only gets fixed if I lock and unlock the device or if I navigate to somewhere else, hence the reason I believe this is software related.
I did a bit of digging around and some people who were also affected by this concluded that might have to do with certain panels being incompatible the kernel, since Xiaomi uses both LGD and JDI panels for the Mi5.
Has anybody managed to solve this issue? A workaround would to enable on screen navigation but I would prefer not to.
Cheers!

Low Brightness Flicker (LineageOS & Stock too?)

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

Question [HELP]Fingerprint hardware not available

Initial Problem​The issue arose after having been on Pulkit's LineageOS (unofficial) for weeks. One fine morning i get the following message on my lock screen: Fingerprint hardware not available. To respect the rules of the forum and since I had already gone into detail about it here and found a temporary fix for it, I refrain from reiterating the same.
TLDR​The fingerprint hardware issue came up abruptly, wasn't fixed with changing kernels. Switched to a miui 14 port for a week, everything was working fine, switched back to an aosp rom (Voltage os), runs fine for a day and on the second half of the second day, the fingerprint sensor stops working again.
Help?​I've scoured through the forum in search for a solution to this but seems like it's a truly unique problem x | Has anyone encountered something like this? Were you able to solve it or was there any permanent fix to this? I really don't want to have to use miui if I can help it and after having been on aosp roms for almost a year now, I absolutely can't daily drive miui T.T
Any advise or suggestions on the matter are really welcome!
Attaching the lock screen screenshot...

Categories

Resources