I've been using POCO M3 for about two weeks right now, and i encountered a really strange thing.
Screen really randomly drops brightness a little bit, not too much, but it's really annoying.
1. Auto-brightness disabled.
2. I tried to reproduce brightness drops by covering/shining a light into all available sensors (doesn't work, so it's not related)
3. Tried to apply gentle pressure to the phone, in case it's an internal connection problem, without any results.
4. Behaves the same with stock, as well as other ROMs i've tried (dotOS, ArrowOS)
I didn't notice any other problems related to this, but i worry it's a sign of things to come.
Tried to ask a couple search engines, didn't find anything similar to my problem.
Some days i don't notice any, some days its driving me crazy how often it does this. Does anybody have any ideas what it might be?
It happens the same to me. My rom is CrDroid. I don't know the reason either. I usually notice it while using chrome
Related
Ok, So I've had my Acer A500 for quite some time now. Couple years in fact. Anyway a few months after getting it I noticed that I couldn't change the display brightness whatsoever. Also the autobrightness did nothing even tho I had tested the sensor and it came out fine. Now I don't know if this problem existed before I rooted and installed a custom rom, however no matter the rom the brightness still will not adjust. I have even taken the tablet apart and made sure the cable to the screen was seated well. I'm wondering if anyone might know if this is a hardware issue what may be causing it? or if it may be a driver/software problem.
I've just noticed that the brightness slider moves from end to end with no change in screen brightness.
Anyone got a fix?
Android 5.0.2
Yes, I have the same problem. Mine is weird though. Mine will sometimes get bright and match the setting, but a majority of the time it goes to the most dim level on the screen regardless of where the brightness level is set. I'm hoping that it is something that I can fix, but I don't know if people will say that it's a hardware issue. My Tab is rooted again after I reinstalled the stock firmware again to try and fix the problem. Hopefully someone can offer an insight to this problem. I'm wondering if taking it apart and heating up the processor with a heat gun would cause it to work. That worked as a temporary fix on an Apple computer.
I have the same problem after I rooted the tablet. The only solution I found is install the app Screen Filter.
Are you on a custom ROM?
Can you reproduce the issue with a stock ROM?
If not,its probably the custom ROM have bugs.
Or maybe sth else
Hey all.
So I got my MXP about a month ago, as my faithful Nexus 6 has long been deteriorating (#RIPshamu), and I wanted to try something a little different. I love the device and have almost gotten it tweaked and set up just the way I like it. However, I'm currently facing an issue that I can't seem to fix.
When I have a dark gray image on screen, such as the dimming when you pull down the notification bar over a white screen, the left side of my screen flickers rapidly from dark to normal, as if changing brightness. It is most noticeable on higher brightness settings, but plenty present enough on lower ones anyhow. I have made sure that no odd display tweaks in GravityBox are interfering with system presets, and I can't figure out what might be causing this.
I'm hoping it is software-related; I bought the device off-contract and without warranty, as I do with all my handsets, but if the problem is with hardware I should be able to fix it on my own so long as I know what part is causing the issue.
I'm running TruPureXMM with FrankenClark kernel. (systemless SU, magisk/systemless-xposed if any of that matters to you). Can provide logs upon request, but things seem normal to me at first glance.
Anyone else experienced this or have a fix?
I too am running TruPure and Frankenclark. I've been having a similar issue with the display, except it's the bottom half of the screen that is dimmed. I've also noticed that the 'dimming' takes on vertical lines of color depending on what the screen is displaying. The 'dimming' has consistently been transparent for me.
I originally thought that it may have started because I changed some settings using kernel adiutor, however changing those settings back did not fix the issue. I've yet to try returning to stock. I've also noticed the same display issue on boot up and in TWRP, which suggests a hardware problem, not a software one.
Some research online suggests that there is a known display bug with the Moto pure, and that the temporary fix is to reboot, but that doesn't solve the problem for me.
I think I'll try reverting to stock first, and if that is unsuccessful, then I'll try to reseat the display connector.
I'm running stock android 7.1.1 on a Nexus 6p and there's a dramatic lag in scrolling response. When the screen is scrolling quickly and I put down my finger to stop the scroll there is a huge lag before the scrolling stops. About half a second or more. It seems to occur in all apps (and even system settings menus). I've had this problem since buying the phone a couple weeks ago. It's driving me nuts. I never have this problem with my iPad, MacBook or even my ancient nexus 4. The odd thing is that if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears, but obviously that's a very awkward thing to do, especially when none of my other devices require it. Does anybody else have this problem (and hopefully a solution)?
I've talked to Google customer support. They told me to clear the cache of every app (yes that does take quite a while) and to clear the partition cache. This did not resolve the problem and now they want me to do a factory reset, which apparently is the last step before hardware warrantee measures. I'd love to know if this is a common problem.
Al--g said:
I'm running stock android 7.1.1 on a Nexus 6p and there's a dramatic lag in scrolling response. When the screen is scrolling quickly and I put down my finger to stop the scroll there is a huge lag before the scrolling stops. About half a second or more. It seems to occur in all apps (and even system settings menus). I've had this problem since buying the phone a couple weeks ago. It's driving me nuts. I never have this problem with my iPad, MacBook or even my ancient nexus 4. The odd thing is that if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears, but obviously that's a very awkward thing to do, especially when none of my other devices require it. Does anybody else have this problem (and hopefully a solution)?
I've talked to Google customer support. They told me to clear the cache of every app (yes that does take quite a while) and to clear the partition cache. This did not resolve the problem and now they want me to do a factory reset, which apparently is the last step before hardware warrantee measures. I'd love to know if this is a common problem.
Click to expand...
Click to collapse
Hi, I made some tests in your issue doesn't occur on my 6P with stock 7.1.1.
Sent from my interstellar 6P
same here
Al--g said:
I'm running stock android 7.1.1 on a Nexus 6p and there's a dramatic lag in scrolling response. When the screen is scrolling quickly and I put down my finger to stop the scroll there is a huge lag before the scrolling stops. About half a second or more. It seems to occur in all apps (and even system settings menus). I've had this problem since buying the phone a couple weeks ago. It's driving me nuts. I never have this problem with my iPad, MacBook or even my ancient nexus 4. The odd thing is that if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears, but obviously that's a very awkward thing to do, especially when none of my other devices require it. Does anybody else have this problem (and hopefully a solution)?
I've talked to Google customer support. They told me to clear the cache of every app (yes that does take quite a while) and to clear the partition cache. This did not resolve the problem and now they want me to do a factory reset, which apparently is the last step before hardware warrantee measures. I'd love to know if this is a common problem.
Click to expand...
Click to collapse
You aren't the only person who has experienced this issue but I haven't had it happen. I don't know if anyone found a solution but if you do a search in this section you should find a thread very similar to yours with a lot of responses. I think some people experienced the issue after updating to 7.1.1
jhs39 said:
You aren't the only person who has experienced this issue but I haven't had it happen. I don't know if anyone found a solution but if you do a search in this section you should find a thread very similar to yours with a lot of responses. I think some people experienced the issue after updating to 7.1.1
Click to expand...
Click to collapse
Thanks, I'll have a look. (Tried searching before but didn't find anything.)
For me the problem predates 7.1.1
I found the source of my scroll lag issue. I sometimes enable the magnification gesture in the accessibility settings (because I often use a particular transit app that has insanely small icons). I realized that when I have this setting turned on the scrolling gets laggy. Turning off the magnification gesture seems to solve the problem completely. Not sure if there's any workaround other than disabling the gesture setting.
Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13
Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.
Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.