Is anyone else experiencing their camera app no longer functioning? I can't open the app without it closing immediately. I'm on stock ROM and first started to experience this last night out of the blue while using cR Droid. I haven't done anything to cause this type of behavior, so I'm not sure if the latest version is just buggy. I've tried uninstalling updates and reinstalling but I still have the same problem.
RetroTech07 said:
Is anyone else experiencing their camera app no longer functioning? I can't open the app without it closing immediately. I'm on stock ROM and first started to experience this last night out of the blue while using cR Droid. I haven't done anything to cause this type of behavior, so I'm not sure if the latest version is just buggy. I've tried uninstalling updates and reinstalling but I still have the same problem.
Click to expand...
Click to collapse
it just closes? or shows a blank screen? (you checked camera access is enabled in QS).
Go to play store and hit uninstall on the camera (it'll revert the camera back to the default version the phone came with).
Also try the camera in another app (it doesn't use gcam but the camera api). Also try gcam in safe mode..
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
RetroTech07 said:
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
Click to expand...
Click to collapse
Tasker/Automate script to detect when you're connected to your car's particular Bluetooth (assuming it has that), and when so, turn sensors off, and when not connected to your car's Bluetooth, then turn sensors on.
RetroTech07 said:
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
Click to expand...
Click to collapse
there is an adb command to do this
Code:
adb shell settings put secure doze_quick_pickup_gesture 0
Related
I seem to be having an issue with the screen turning on at random. I have Always-on screen set to ON and tilt-to-wake set to OFF, but the screen will turn on sometimes seemingly at random and multiple times in a row. I have done Factory Reset a couple of times and it does not help.
Is there anyone else with this occurance and is there a fix for it?
Sent from my VS980 4G using Tapatalk
I have this issue too. I've tried several configurations and it keeps doing it.
Sent from my SM-N910V using Tapatalk
Any apps that send a lot of notifications or any notifications that are automatically dismissed/very briefly show up? Can't think of anything else that would wake your watch.
No, not on mine.
Sent from my SM-N910V using Tapatalk
I have the exact same issue. At first I thought it was tilt-to-wake having poor gesture recognition so I turned it off. However I noticed without touching the screen it would turn on and then turn off after the stand-by time. To verify that was the case I left it sitting on my desk all day and observed that it would in fact randomly turn on and off. I also noticed that when the issue occurs the battery life decreases rapidly.
Also this issue will continue to occur even in theater mode.
Have you find a solution yet? My smartwatch 3 does the screen turn on randomly and then also touch screen issue occurs, and it makes random touches, swipes going into settings and so on, without touching the screen. I'am on the latest wear version mwd49b.
For more info search on youtube for my video about this problem: Sony SmartWatch 3 screen problem.
I recently began having the same problem. The screen does not turn off after it randomly turns on - I have to manually press the button to turn it off. Needless to say, this tend to run down the battery. I did a factory reset this morning, but the problem persists.
EDITING POST JULY 20:
After factory reset, I actually had the watch doubly connected to the phone, so I have corrected that now. However the problem with the random turn-ons began occurring well before the factory reset. I'm not sure what triggers it, or what stops it, but when it begins to happen, it drains the battery very quickly. The problem only began recently (within the past few weeks), so I'm not sure what changed to bring this on.
A bug in Android Alarm Clock keep the watch active after alarm ring. Just corrected yesterday by an update on Google Alarm/Clock app.
On the phone > android wear app > settings icon on top right > device settings (smartwatch 3) >tilt to wake set to off
I have no rules set for switching into power save modes, yet I keep finding my phone in power save mode with all the radios turned off. I'm using a case with a viewing window if that means anything. Anyone else having this issue?
I had this issue, and my wife had it too. I ended up disabling the power saver on both our phones. I have since enabled it again on mine, and it has been behaving properly. No idea what causes it or why mine now seems to be working OK, but it is a very annoying bug.
How did you disable it?
Dan
I use the "Disable Application" app by BIZKAI Apps from the Play Store. You need root, obviously.
I was afraid of that. I've not rooted the phones yet.
Dan
This has been happening to me also and i dont have it set to switch but it will randomly do it and turn off my network. This phone is really pissing me off.
Something you might want to try is to go to power saver-> smart switch-> switch by schedule and change it from battery saver to normal. It sounds like a bug that someone mentioned a while ago: smart switch's switch by schedule runs even when it is not turned on.
Sent from my ASUS_Z00AD using XDA Free mobile app
Not related to OP's issue as they have the View Case which I hope prevents this, but I have found that the phone activates in my pocket and often enables flight mode, power saving mode, and other random toggles. Noticed that when the phone is in a pocket facing my body, wild things happen. facing away and nothing happens.
Take your phone out, turn the screen on and rub it on your knee. You will see that the touch screen is so sensitive that it responds through the fabric of your plant leg. This seems to be a problem for me from time to time, but the new slide to unlock on the view window has fixed some of the issues.
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Not So Pro said:
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Click to expand...
Click to collapse
Is AOD on or off? What happens when it's on?
Badger50 said:
Is AOD on or off? What happens when it's on?
Click to expand...
Click to collapse
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Not So Pro said:
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Click to expand...
Click to collapse
Quite possibly so. I know nothing about snap face, snap chat, or whatever these social media apps do. Although, you may try clearing the app data and cache on said app to see if it helps. No guarantees though. As is the case with many things android! ??
I've had the same issue ever since I installed, I believe, the nav bar immersive mod. Not sure, around same time. I was able to hurt power button twice for camera and that would pull it up and u could switch back to screen. I don't have xposed or Snapchat, so I don't think either of those are it. It's random when it happens to me.
I've had similar issues. I'm not rooted and have never used Snapchat or AOD. I do use immersive mode for some apps so I've thought that might be causing it. Like stated above, I can get the screen to come on my double tap to open the camera or just holding the phone face down and tap the back a couple times then flip back over and the screen comes on.
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
shmity said:
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
Click to expand...
Click to collapse
Ok so a little more testing. When Ambient display is set to always on, I have no issue, maybe a slight lag when waking/unlocking. When ambient is set to tap or pick up i get issues, when ambient display is set to off at all times, i have no issue. Plugging the phone in to charge seems to force the issue to happen.
Edit: Seems that even with ambient display off totally the issue pops up. Strange thing is if i unlock the phone and take a screen shot, its totally black.
I to have this happen and like sportytony I use camera to wake device. Sometimes that too takes a bit. Most of the time when it finally does wake there will be a notification that systemui isn't responding. So I wonder if it's related.
Ok, I've been having this issue happen multiple times a day. I use this immersive app: https://play.google.com/store/apps/details?id=in.tsdo.elw
Since I have turned all ambient display options off and made sure that System UI is unchecked in the immersive app i haven't had an issue at all.
Its definitely related to system UI, com.android.systemui to be precise
i used to try to set up Power Nap on this device, but it can't find System UI in app list, make me unable to whitelist it, thus causing same issue like yours,
Screen wont turn on after sleep, since System UI wake up is blocked
I was using hide navbars and had this issue
I uninstalled and never had that problem again
Sent from my Google Pixel 2 XL using XDA Labs
Didn't expect all these replies but I'm going to try to untick system UI and see what happens. Thank you all!
Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)
Frans1897 said:
Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)
Click to expand...
Click to collapse
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?
xprzs said:
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?
Click to expand...
Click to collapse
Hey! Thanks for the answer, I can confirm we have the exact same issue. I also have the same brightness issue you described
Anyway, I have always used fingerprint unlock though so I don't know what to answer you.. I only recently noticed the weird behavior. I did a couple things to test and I found out that enabling the "fingerprint" icon showing in the always on display seems to "fix" the issue of the flicker but not the one of the brightness change (after enabling it i've yet to see the problem occur), you should try it and let me know if you see any improvement. It's probably on samsung's end though and hopefully we get it fixed with android 10 or earlier
I'll take this chance to ask you another question; two weeks ago I received a software update and ever since that day I noticed my battery to be lasting waaaay less than it used to, did you update your phone as well? Did you notice a battery drain?
I have the issue both of you talking about.
hello, I had this same issue and what I did was turn the phone off, and booting it up while pressing "Volume Up", after entering a black screen with many options, I selected wipe cache. It has worked without a flaw since then. There's lots of bugs with this phone. I recently had a problem where the USB port will detect a device and "plugged and unplugged" it, making my phone unable to dim. Thankfully I was helpful.
My phone keeps waking up, not to the ambient display but to the OG lock screen, it happens within 10 to 20 seconds after turning the screen off, and keeps happening over and over again. I guess it must be a third party app because it doesn't happen in safe mode, so my question is, is there an app I can use to determine the culprit? I don't see any option to disable third-party apps, only uninstall them, which is highly inconvenient, to keep uninstalling apps to see if they are keeping the phone awake, then having to reinstall them if they don't seem to be the culprit.
Is anybody else having this problem?
I got lucky on a Google search and learned that it was the Ring app! Apparently there's been a little bug where it turns the screen on even when it's not supposed to give you a notification.