I've not noticed this before and not sure if it's a glitch in the Oreo beta, however everytime I restart my device (which has been a few times today with beta 2) my accessibility services are turned off, so BxActions stops working until I re-enable it in the settings, the same with Navbar apps.
Can anyone else confirm this?
Thanks,
YES! Same issue. However, I've had this issue dating back to my Galaxy Tab S on 6.0.1
I've just come to live with the fact that apps like Last Pass will never work properly unless I regularly (manually) provide them with accessibility access.
Related
Hi!
I got a new Nexus 6P a few days ago, and I noticed some stuttering while using any app. I enabled the profile GPU rendering graph, and there are spikes regularly, which shows (I guess) that a few frames are skipped: http://i.imgur.com/9qEjRD3.jpg
Scrolling in the launcher (Action Launcher 3), Twitter, Relay Pro, sometimes the Settings app, produces the same result. It seems to happen in almost every app.
After turning the phone on for the first time, it received a bunch of updates that brought it to the last Nougat update (NBD90X, Oct 2016). Then I factory reset and transfered data from my previous phone during the initial setup. Then I noticed the slight stuttering, so I tried another factory reset, and then I set my phone as a new device and I installed a few apps manually. It didn't change anything.
Now I don't know what else to do. Any ideas?
Remiscan said:
Hi!
I got a new Nexus 6P a few days ago, and I noticed some stuttering while using any app. I enabled the profile GPU rendering graph, and there are spikes regularly, which shows (I guess) that a few frames are skipped: http://i.imgur.com/9qEjRD3.jpg
Scrolling in the launcher (Action Launcher 3), Twitter, Relay Pro, sometimes the Settings app, produces the same result. It seems to happen in almost every app.
After turning the phone on for the first time, it received a bunch of updates that brought it to the last Nougat update (NBD90X, Oct 2016). Then I factory reset and transfered data from my previous phone during the initial setup. Then I noticed the slight stuttering, so I tried another factory reset, and then I set my phone as a new device and I installed a few apps manually. It didn't change anything.
Now I don't know what else to do. Any ideas?
Click to expand...
Click to collapse
Do you have any Accessibility Services enabled? Go to Settings -> Accessibility -> Services and see if anything is marked 'On'. I've found that some apps such as Greenify can cause extreme lag when enabled. This is a known issue with the Accessibility Service implementation on Android and Google has said they don't plan on fixing anything as it's not really a bug. If you don't have any services enabled then I'm not sure what's wrong.
dante020 said:
Do you have any Accessibility Services enabled? Go to Settings -> Accessibility -> Services and see if anything is marked 'On'. I've found that some apps such as Greenify can cause extreme lag when enabled. This is a known issue with the Accessibility Service implementation on Android and Google has said they don't plan on fixing anything as it's not really a bug. If you don't have any services enabled then I'm not sure what's wrong.
Click to expand...
Click to collapse
None of the accessibility services are enabled :/
I'm not certain it happens only with restart but I have two apps that use accessibility services. Last pass and an app called text aide.
I've noticed that when I restart my device these are switched back to off. So Everytime I have to go back to accessibility options and turn them both back on.
Is this an issue with the op5 software? Or is this a safety feature of 7.1.1?
Anyone else have this issue?
Thanks
Update
Nevermind. Accessibility services get turned off even without a reboot
My phone was on the whole time and after maybe 4 hours I noticed the accessibility services were turned off again.
What's going on?
Hi there, so I updated my ph-1 to the latest Oreo 8.1 earlier this morning and have been experiencing significant delays when unlocking my screen. Sometimes the phone did not respond at all and the screen just stayed black. I had to restart the phone in such cases. Help! I seem to be the only essential phone user in entire Sydney
If you're using immersive mode, that might be the issue. Try disabling that, and see if the issue persists.
I'm experiencing the same. Setting immersive mode to None does help a bit, but it's still not as snappy as before.
And after all the same settings worked perfectly on the 8.1 beta.
Tried to go back, but on official 8.1 the recovery mode only says "no command"....
I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.
And specialty if you use immersive mode with sytem UI make it very long delay
winstonxyz said:
I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.
Click to expand...
Click to collapse
Same issue here. Sometimes takes so long to unlock that I am unable to answer a phone call that comes in before it goes to Voicemail. Usually happens when the phone has been idle for a while.
Update:
Did the dreaded FDR (factory data reset). Installed the "Tiles" app from plasystore and ran the noted adb command to allow immersive mode, tile display, and enable write secure settings permissions. I chose the action to hide the navigation bar within the Tiles app. I ignored the setting to stop on sleep so the app keeps running when the phone screen goes off. In testing it for about an hour the phone seems to unlock without any issue for now and without any delay. I also made phone calls while the phone screen was off and I was able to answer the call easily. So far so good using the Tiles app!
sounds like the expanded desktop Oreo issue. There's a Xposed module DeepScreen Oreo for it.
Back when Oreo was in beta, I read reports of people finally being able to activate Google assistant while the screen is off. However, now that I have the official update, it still doesn't seem possible. And even more so, I can't even trigger GA to unlock my phone from the lock screen- Google's settings say it is blocked by my phone's administrator, something that was never an issue in Nougat.
Has anyone else noticed the same and/or gotten GA to work from a locked or turned off screen?
Hi. I didn't have any problems to unlock or activate my device with the google assistant on Oreo. But I had the same issues like you with Nougat.
DerOlleFuzzy said:
Hi. I didn't have any problems to unlock or activate my device with the google assistant on Oreo. But I had the same issues like you with Nougat.
Click to expand...
Click to collapse
Is there a setting to enable in Google settings that I'm not seeing? Did you need to disable Bixby or something?
Ahh dang! I got it working to turn my screen on, but I can't get it to unlock my screen. Looks like it is most likely due to my "Work Mode" profile for my job, it seems like Smart Lock itself is disabled.
ryanpm40 said:
Is there a setting to enable in Google settings that I'm not seeing? Did you need to disable Bixby or something?
Click to expand...
Click to collapse
On nougat I tried everything to unlock my phone with google assistant. It worked only 1 or 2 times and then Bixby or some other Samsungstuff dominated GA so the GA couldn't recognize my voice.
On Oreo it works fine. I have never activated Bixby Home and Bixby Voice after flashing and wiping my actual ROM.
I experiencing one rare bug with my new Nokia 5 phone. There is Wi-Fi Scanning option in Locations settings, that allow to scan Wi-Fi networks even if global Wi-Fi toggler is off. This option turning itself off after 2 hours of phone inactivity. I think it is something wrong with deep sleep mode in the last updates for my phone. I need this option being on for better location quality. But I can't to find any solution to keep this option turned on constantly. For a while I use global Wi-Fi option enabled as a workaround. How can I t fix this problem? Or is it inner program bug and I should wait for any luck in updates? Thanks.
Nokia 5, Android 8.1.0 with December security patch. I tried safe mode, factory reset, but nothing helped me.
P.S. This issue is somehow linked to known bug with removed by Google menu item "Keep Wi-Fi on during sleep". Some people reported it wasn't worked even if turned "Always". In our device it is always on by default (and hidden).
This issue is not linked to deep sleep or doze mode. It is linked with Google Play Services and device administrators. I removed all updates for Services and problem was solved if I'm right. For it I disabled all two device administrators in Security settings (Google Pay and Remote Controls). Now I installed updates again. I will test further.
Unfortunately issue returned after Google Services update. But I found another solution. I disabled idle (sleep) mode using adb. And Wi-Fi Scanning work all time now.