I am using CM11c0_codina.nova plus ace2nutzer.kernel.4.4 codina
Using the CM launcher without the Privacy Guard enabled seems to have been the
cause of the back button's failure. I could feel the buzzer but nothing happens.
I installed a button remapper.
Why would the problem go away if the privacy guard was enabled?
In an earlier question I thought the cause was the keyboard app loosing its tick. Is there
a way to ensure that the keyboard app does not get unticked, without my specific action?
R
Related
I have run into a strange behaviour with my Z2.
I've now tried 2 cleanly flashed ROMs (AICP and RR) and with both I get the exact same issues:
Every now and then U-touch functions seem to reset to some predefined actions without the settings itself being changed nor is the keylayout file changed:
Tap is back, press does nothing, double press opens camera, swipe left does nothing, swipe right opens menu. Screen rotation stops working as well and advanced reboot options are gone as well. There might be other issues as well but when ever I run into the previously mentioned issues I just restart the phone and all settings are back to normal.
What could be causing this? It does not seem to be a hardware issue per se, as I would imagine the touch button would to stop responding altogether. Now it just resets to some weird predefined actions.
Could this be about the baseband ppl seem to be mentioning everynow and then?
I've attached screenshot of my baseband.
This has something to do with the "system profiles". I have been using them once I understood how handy they are.
I just got the bug again when my profile changed from "default" to "home". I changed back to default and disabled the whole profile system and my screen started to rotate and u-touch actions returned to those that I have set.
Is this "system profiles" thingy a CM/LOS feature? Where should I nag about this?
This is indeed a LOS14 issue.
Faster workaround than rebooting is to switch wifi off ( or what ever is the trigger u got) and lock and unlock the phone one time normally and then activate wifi to enable "home" profile again.
Hey all, my ring doorbell app wakes the screen anytime I get an alert. I want to keep the notifications on but don't want the screen to wake. It wakes even in my pocket which I want to of course avoid. It may just be a bug in the app but I should be able to limit that from happening. Or so I hope anyway.
I have tried the following.
1. Switched all notifications pertaining to the app and individual cameras to "sound only"
2. In the app I have disabled "alerts open full screen video"
3. I have disabled heads up notifications globally through ADB.
4. Disabled ambient display.
5. Disabled notifications on lock screen.
I'm at a loss on what to do next. Any ideas are appreciated at this point.
TIA
ifly4vamerica said:
Hey all, my ring doorbell app wakes the screen anytime I get an alert. I want to keep the notifications on but don't want the screen to wake. It wakes even in my pocket which I want to of course avoid. It may just be a bug in the app but I should be able to limit that from happening. Or so I hope anyway.
I have tried the following.
1. Switched all notifications pertaining to the app and individual cameras to "sound only"
2. In the app I have disabled "alerts open full screen video"
3. I have disabled heads up notifications globally through ADB.
4. Disabled ambient display.
5. Disabled notifications on lock screen.
I'm at a loss on what to do next. Any ideas are appreciated at this point.
TIA
Click to expand...
Click to collapse
I've struggled with the same thing for months. It never used to do it, but after an update earlier this year it became the new normal for me.
I'm glad I'm not the only one. Hopefully somebody chimes in with some sort of work around.
I'm having the same problem with a Sony XZ1 phone (Android 8.0.0). I spoke with Ring at length and it's 'apparently' a problem with my phone, not their App.
I think that's a load of rubbish and something they need to address and fix. I installed the App on another Android phone running an earlier version of software, the App installs with different options and doesn't wake up the screen. So it's obviously dependent on the OS version but as other Apps don't have the same problem I can only conclude that it's an issue with the Ring App.
Has anyone tried uninstalling the app and then install an older version from APK mirror? Not even sure its on there but it's worth a go
hatdrc said:
Has anyone tried uninstalling the app and then install an older version from APK mirror? Not even sure its on there but it's worth a go
Click to expand...
Click to collapse
That's a great idea. There are plenty of versions to try on APK mirror, one or two per month from 2018. Not a good sign for a reliable and stable app.
I'll give it a go later unless anyone gets there first and can suggest a 'good' version to try
Were you able to find an older version that doesn't have the screen wake behavior?
edit: Pixel 2 - going back to 2.0.66.8 still has the screen wake behavior regardless of notification setting.
edit 2: 2.0.57.2 does the same thing...
Looks like the latest ring version finally let's you fix this. Select your devices, go to notification settings, then select sound only. The default is sound plus pop up. I no longer have the issue after making the change.
Can anyone confirm if turning off the 'plus pop' in the ring app settings works? I have a new pixel 3 on Android pie and the app is still turning on the screen at every alert event with settings set to just sound or just silent.
I'm having the same issue with the ring app. It wakes the screen. Really sucks when phone is in my pocket. I have tried every option and or combo of options. I have a pixel 3a on Android 10. Android 10 does have a option to wake screen for notifications found under display advanced, lock screen. But it is turned off
Still a problem on Android 10, No combinations of settings has been able to stop this for me. Of course Ring denies this even though I have sent a logcat to them.
Recently (last week or two) tilt-to-wake has stopped working, and the option to enable it no longer exists on the on-watch settings menu.
The toggle for tilt-to-wake is still present in the Wear OS phone app (under Advanced settings) but even when on, the tilt-to-wake functionality no longer worked. The only way to wake the watch is to tap the screen or press the side-button.
Anyone else noticed this? It is driving me mental!
Cheers
Uhh... scratch that. After rebooting watch, new Google App was installed and it is back to working as normal! Should have tried that first.
Hey guys, anyone else using gestures and samsung pay? It appears that there used to be an option to only allow swipe up at the lock screen but I cant find it.
Thanks.
You've got to go into the pay app itself (open it up), go through the initial stages of the app's setup and then once you're on the main screen of the app - go into settings and you can turn that part off which interferes with the gestures at the bottom of the screen.
peteri8706 said:
You've got to go into the pay app itself (open it up), go through the initial stages of the app's setup and then once you're on the main screen of the app - go into settings and you can turn that part off which interferes with the gestures at the bottom of the screen.
Click to expand...
Click to collapse
Thank you very much Sir!
Very odd that they make you reset the app to get to those settings.
peteri8706 said:
You've got to go into the pay app itself (open it up), go through the initial stages of the app's setup and then once you're on the main screen of the app - go into settings and you can turn that part off which interferes with the gestures at the bottom of the screen.
Click to expand...
Click to collapse
Thanks for that! Hadn't realised it was active from the lock screen until now! Disabled it
Or you can just uninstall Samsung Pay which is the easiest way if you don't use it. I never use my phone that way so I don't need it.
Hi,
Since the April update I got an issue with my pixel: every time I cover the front sensor (camera and/or light sensor), the screen goes off for a little time. This is like a pocket mode, but I don't find the setting in the Pixel menu. Does anybody knows how to fix this?
Interesting.....not experiencing the same. GL!
I just rebootet my phone and the issue was gone! Strange...
daniel.1983 said:
I just rebootet my phone and the issue was gone! Strange...
Click to expand...
Click to collapse
I assume you are using the default Google Dialer and you've checked it's the default dialer when you go to Android Settings --> apps --> default apps: Phone App.
If this happens again, clear storage on the Phone App and then enable all permissions including advanced options. The way to get into app permissions: long-press on phone app shortcut, app info, then under storage; clear storage. in the same 'app info' window, enable any options under 'advanced' such as display over other apps.
I did experience this a few weeks ago when using a different dialer/phone app (Koler).