Hi everyone, I've had my Moto Z for a couple of days now and am pretty happy with the device - even with the battery life I have one small problem, however.
Sometimes, when the screen is turned off, the Moto Display approach action won't work. In these cases, I also notice that the bottom right IR sensor isn't lit up - which it usually is when the display is turned off. The approach action only starts working again when I pick the phone up. This is very inconvenient and not how it's meant to be.
Is anyone else experiencing this bug?
At first I thought it might be an issue with Doze putting the process responsible for the Moto Actions to sleep, but after whitelisting all Moto apps the issue still sometimes occurs. I have not yet found out under which circumstances this happens.
Any help would be greatly appreciated!
EDIT: It seems this issue only occurs immediately after turning off the screen, after which there is a slight delay (a couple of seconds) before the IR sensor is activated. I will observe if this is really the case, which of course would render it a non-issue.
Related
The accelerometer on my Razr Maxx works promptly and perfectly except under two conditions. The first -- if I'm lying down, say on a couch or in bed, and holding the device over my head facing down. In this position the device will almost immediately shut off over and over. It won't reboot, just shut down. I can always restart it the same way I would from any "sleep". I can get the device to stay on merely by rotating it to face "up" no matter whether I change position or location or run or do not run any particular application. Is this common? Is it by design for some reason? The second -- if I have Button Savior installed, the Maxx accelerometer will work but there will be a significant delay in responding. Like 15-30 seconds delay! No Button Savior - no delay. Install Button Savior - delay. Uninstall Button Savior again - no delay. This troubles me as I really like Button Savior even on devices that have "hard" buttons. Having these controls right under my thumb is the fastest way to navigate, for me. Button Savior (updated) works perfectly for me on other Android phones, on my rooted Nook Color (CM7), even on my rooted Nook Touch. Any cures for either ill?
Hi
The accelerometer issue... does this happens from the first day you bought it? I trying searching similar issues, could not find anything. I am almost sure it is physical defect of some kind, you should probably take it back for replacement.
I don't know if the accelerometer issue related to Button Savior began when I first installed the app (as opposed to coming from a particular app update, for instance) as it took a long process of elimination to find the connection. As to the "upside down" issue I believe it has always done that. However -- it only does it if I TURN ON the device while it is upside down. If I start using it facing up, say watching a video, and then turn it upside down the video continues to play flawlessly. Bizarre!
I know there is an option to use the light sensor to detect when your phone is in your pocket, and turn off. Maybe it's on on your phone, and it's detecting lower light when you flip it over and shutting the screen off?
ok, so i misunderstood the issue, i thought the phone turns off completely...
if it only goes into "silent" or "lock" mode... maybe you installed some kind of app that does that when you flip? or maybe your player has one of those settings? like... say you are in a meeting, with your phone on the table, it rings... you just flip it and it goes silent.... some android build have that as a default setting already...
here, check this so u understand better what i mean :
http://www.appbrain.com/app/flip4silence/org.failedprojects.flip4silence
hope this helps!
tried updating yet? i had the same problems prior to the 65.1.40 update
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
For a week or two now,* I have been having some funny things happen with my Redmi Note 4 (Qualcomm, Global) phone.
Before that it had gotten water in it and basically shut down entirely, but they fixed it and got it up and running. When I picked it up they showed me watermarks on the screen, saying that the screen had frozen only once but that it may just be lagging.
Since then I have had a few symptoms of an issues, perhaps hardware issues, but potentially something that I can fix without paying more for parts.
Here are the things that happen:
- Music stops suddenly (screen on or off) and the music app has to be reopened (DoubleTwist, Miuiu's Music app, etc); Somes while in Doubletwist, if I click to visit home screen (square button) than the music stops. (this is the first issue that I noticed).
- 1-2 seconds of white screen before already-open apps appear after selected; Sometimes problems with apps loading or screen goes black when loading
- When closing apps or returning to home screen, it looks like the desktop(?) background comes up and then a second after is is re-populated with icons as if system is refreshing the home screen
- Once any of these issues begins, it usually worsens and the cell phone gets slower, behaving more and more strangely until not even useful to me; Reboot clears it right up for an hour or two or whenever this wierd stuff starts to happen again
-It seems like if I make a point of using the phone modestly, slowly, I can avoid these issues from starting up
- Sometimes reboot rometimes hangs on initial black loading screen
- Sometimes if I hit the power button to turn off the display, I can not turn it back on with that button (neither does the battery-dead orange light flash), so I have to reboot.
-When I turn the phone screen off while it has been working fine, I come back later, turn on the screen to find that it is now on the boot logo screen and it stays until I hard-reset the phone.
So, these are potential issues I have guessed at:
* Screen damaged? So far, other than watermarking at the top and some backlight bleed, sensistivity is perfect on the phone, and symptoms involving screen always seem to be triggered more by apps or pressing buttons.
* Apps or Android corrupted/internal memory damaged? I backed up via Settings and did a Hard/Factory Reset, then restored from backup. I still have the problems.
* RAM partially damaged? I test RAM with two apps and none of them showed issues. Namely my available RAM and used RAM reported always add up to the 4GB my phone has.
*Other Hardware Components failing? I used 3 apps to check all of the hardware devices and sensors that I could think of. Vibration is the only thing that does not work, and honestly, I don't care much about vibration.
Today I have suspected that settings may being at fault, and/or battery savers turning off my audio. Battery savers often identify my music apps as using "excessive amounts of power," perhaps because the speakers at involved, but it does make me think... I removed any battery-related and security apps, then turned off all battery saver options in settings earlier today. In 2 hours of music listening after that, I have not had any shutdowns, but I am not convinced I have solved the problems. In the weeks after this, the issue is back and the audio issue is always followed by the phone operating very sluggishly.
I have done a factory reset and restore, and the issue persists. Do you think there's any point in trying to do a clean reflashing of MIUI? Could it be a software issue or definitely hardware?
What advice can you give me?
Thank you for reading.
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Lazy_Pickachu said:
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Click to expand...
Click to collapse
Miui 9 does not have safe mode to boot in.
I purchased my S21 about 5 weeks ago and I am not sure if I have been experiencing this issue since I bought it but in the last week, I have noticed this issue. When my phone is locked, the AOD will either show for a few seconds to a minute or just won't show. I've ensured it is set to always show, power-saving not set to turn it off, no Bixby routines and any updates are installed for phone/AOD. I've even factory reset my phone and removed the case and screen protector and the issues are still persisting. Does anyone else experience this issue?
Disable all power management... it screws up all kinds of things.
Does AOD show if you tap the screen?
I have disabled all power management that I am aware of and still experiencing issues. I've set it to show on tap and while it worked the first time, subsequent taps do not show the AOD
Video demonstrating AOD tap to show issue
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
blackhawk said:
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
Click to expand...
Click to collapse
I normally use AOD always on, I'd tried the tap on the option to test. Going to try flashing it today to see if that helps despite the factory reset not helping.
So I've flashed the stock firmware back onto my device and the issues are still persisting. I've contacted support through the Samsung Members app and it's been escalated to the Research and Development team and am just waiting to hear back.
Did you update any Samsung apps after the reload before testing it? Go with the factory app loads.
Try disabling the lock screen... they tend to end up locking out the intended user anyway, sooner or latter.
If no one else is having this issue it very well maybe a hardware issue.
Did you ever wonder what happens when one or two micro transistor junctions out of the millions in a phone fail? Yes, well...
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
The you
brodieb321 said:
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
Click to expand...
Click to collapse
Did you ever get this fixed. I have the exact same issue on my s20 ultra
Edit: Nevermind just fixed it after 3 days troubleshooting. Oddly it was the the disable AOD while in power saving mode that needed to be disabled even though I don't use power saving mode. Samsung never seem to amaze me with these dumb persistent bugs.
Glad to see you solved the issue. I'd already confirmed this setting was off for me. It's still happening. Looks like it's something to do with the level of light detection as the issue only happens when I have auto brightness set for the AOD. The problem is it's not even that dark when it's happening and never occurred with my S20 FE.
Good Day Everyone,
I have early stage Age-related macular degeneration. Right now, it is in the early stage, but I'm running into an issue with my OnePlus Nord N10 5G.
The center field of my eyesight is getting darker. For example of your phone is at the maximum brightness level, it would appears around something like 60% brightness to me.
So see a beautiful photo of an evening skyline, but I see a post sunset view. It's still there, I just see it darker.
Anyway, I really need to make my screen brighter then the factory set maximum level. Yes, I know that will effect my battery life l, but I simply need it.
The Google Store does have some Apps that "claim" that to do that, but the reviews always are always very mixed. Alot of the reviewers saying they don't work and they believe the app developers just want access to their phone data.
I have already gone to the "accessibility" section of "Settings". "High Contrast" and "Color Correction" have helped some, but not enough.
So after all that, my question is, dose anyone know of an app for the OnePlus Nord N10 5G that can legitimately increase the maximum screen brightness? In the alternative dose anyone know how trick the Android 11 (Red Velvet Cake) into increasing what the maximum brightness level is set at?
Jeff B
Hey @ARTEST4ECHO,
You maybe encountering the screen brightness/dimming problem that the OnePlus Nord N10 5G has. If you have noticed that occasionally the screen seems dimmer than usual, but the brightness control is turned all the way up then this might be the problem.
Unfortunately this is a super common issue with this phone. I'm very surprised no one else has replied yet. The Forum on Oneplus's website there is multiple threads about this issue with hundreds of people complaining. Unfortunately it seems that OnePlus either refuses or is unable to fix the issue!
There is one "workaround" that I have found that seems to work. At first it seemed to work every time but lately it's hit or miss. Which is very strange though because I never update my device, so I'm not sure why it used to work all the time and now it doesn't.
Here is that solution that someone posted on the OnePlus website forum. (Again it used to work every time until lately so your mileage may vary. Unfortunately this seems to be the only option that helps/resolves the issue temporarily, besides rebooting the phone. Oh in case you did not know if you turn the phone off and back on the issue goes away until it happens again... )
Temporary Fix How To:
How to temporarily readjust screen brightness when dimming issue occurs:
1. Swipe down from the top of the screen to bring up the notification bar and turn on automatic ambient lighting (the small sun icon with the letter "A" next to the brightness slider)
2. After turning on automatic ambient lighting, manually slide the brightness control up. (increase the brightness - it will still be low brightness even after doing that)
3. Then finally power down the phone screen and power it back up. (just short press the power button to power off the screen, then press it again to turn the screen back on)
4. The screen brightness should be back to normal. Then be sure to "disable" ambient brightness as mentioned in the first step.
Hopefully this solution will work for you. Unfortunately if it doesn't there's no other method that I'm aware of to resolve the issue. I've had the phone for now going on 2 years and have been searching for a solution to this problem ever since.