I've rooted my Pixel XL and today an update became available and keeps a notification in the left corner. How can I disable this?
I have this question too. Is blocking all notification from Google play services the only way?
dinkoh said:
I have this question too. Is blocking all notification from Google play services the only way?
Click to expand...
Click to collapse
Developer Options. Hit the slider for automatic updates.
TonikJDK said:
Developer Options. Hit the slider for automatic updates.
Click to expand...
Click to collapse
Hmm, I still get it? Regardless of "Automatic software update" switch is on or off. I'm unlocked and rooted. Does that have anything to do with it?
dinkoh said:
Hmm, I still get it? Regardless of "Automatic software update" switch is on or off. I'm unlocked and rooted. Does that have anything to do with it?
Click to expand...
Click to collapse
Odd. I don't get them. Slider off and unlocked and rooted also.
After turning off automatic updates in developer's settings, look in Settings/Notifications/Google Play Services and Block Notifications. You'll never see it again.
Sent from my Nexus 6 using XDA-Developers Legacy app
Related
Has anyone else seen this nag screen coming up randomly asking for permission to share everything.
. This is the app. So no one else has seen this?
I did this morning after update
Sezmar said:
I did this morning after update
Click to expand...
Click to collapse
I decline it every time and it keeps nagging me. Sometimes popping up every few seconds.
There is a setting in the messaging app to turn it off.
kleen3r said:
There is a setting in the messaging app to turn it off.
Click to expand...
Click to collapse
Thanks for the reply, but its already off and I use google messenger and hangouts instead.
Hi,
I am using OP3 from last 1 month. Some app required accessibility service to be on, I observed that accessibility service being off automatically. Like applock, voodoo, freecharge, 360 security. Because of this applocks fingerprint is not working
Also sleep(turn of display) sometimes not worked
Any other faces this issue??
What is the problem? Can someone help me to solve this.
Phone is not rooted.
Thanks in advanced
I'm facing the same problem since updated to 3.2.0. In 3.2.1 the problem persist.
Till now the only solution was to boot in safe mode and grant to apps access everywhere.
Also not rooted, 100% stock.
If anybody knows a different solution I will also appreciate.
Sent from my ONEPLUS A3003 using Tapatalk
been having this issue myself - another relevant issue is that when you enable an accessibility service the PRE-BOOT PIN screen gets disabled.
O don't know how many people have this problem, I've tried to report also on oneplus.net but there till now, nobody reacted.
Forgot about pre-boot pin, your right buddy.
Sent from my ONEPLUS A3003 using Tapatalk
3.2.2 is coming let's see, it it resolves
got 3.2.2 - have't had the issue come up yet but it's only been a few hours
Both the start up pin and the accessibility randomly turning off are google issues and not directly related to the oneplus.
For the accessibility service randomly turning off. try turning off the battery optimization for the app that needs access. see if that works.
This might work for the pin. Also might have to redo it every time you reboot your phone.
If you have Require Pin At Boot enabled: disable "require pin at boot" option, enable Accessibility Service, and re-enable the security option.
2x4 said:
got 3.2.2 - have't had the issue come up yet but it's only been a few hours
Click to expand...
Click to collapse
use the groom icon in recent apps and you will see it happen even on 3.2.2
lparcshinoda said:
use the groom icon in recent apps and you will see it happen even on 3.2.2
Click to expand...
Click to collapse
Yes it is happening after using groom,
skavangar said:
Both the start up pin and the accessibility randomly turning off are google issues and not directly related to the oneplus.
For the accessibility service randomly turning off. try turning off the battery optimization for the app that needs access. see if that works.
This might work for the pin. Also might have to redo it every time you reboot your phone.
If you have Require Pin At Boot enabled: disable "require pin at boot" option, enable Accessibility Service, and re-enable the security option.
Click to expand...
Click to collapse
It is not google issue, before this i was using nexus 6 and i didn't feel it. Also i checked on various mobiles
skavangar said:
Both the start up pin and the accessibility randomly turning off are google issues and not directly related to the oneplus.
For the accessibility service randomly turning off. try turning off the battery optimization for the app that needs access. see if that works.
This might work for the pin. Also might have to redo it every time you reboot your phone.
If you have Require Pin At Boot enabled: disable "require pin at boot" option, enable Accessibility Service, and re-enable the security option.
Click to expand...
Click to collapse
It is not google issue, before this i was using nexus 6 and i didn't feel it. Also i checked on various mobile.
ONE PLUS replies my mail as follow
"we don't suggest any third party application so hence I request you to please uninstall the third party application. "
niranjansahu009 said:
ONE PLUS replies my mail as follow
"we don't suggest any third party application so hence I request you to please uninstall the third party application. "
Click to expand...
Click to collapse
wow
You have to turn off the battery optimisation for the app that uses the accessibility service. This will fix the issue.
This fixed it for me at least.
I tried this, after cleaning apps from recent app option. After this service being off, even if battery optimization is off for that apps,
lparcshinoda said:
use the groom icon in recent apps and you will see it happen even on 3.2.2
Click to expand...
Click to collapse
Now i not used that groom button. And it is going perfectly
adding the app that uses accessibility to the white list for battery optimization solved this issue for me
2x4 said:
adding the app that uses accessibility to the white list for battery optimization solved this issue for me
Click to expand...
Click to collapse
No I din for me
Hi all,
After updating my unrooted OP3 to official Nougat, I am noticing that Google app can no longer run in the background. That is, any Google Now or Google search that I do in the phone dissappears from the multi-tasking windows as soon as I navigate away!
I tried clearing Google app's cache, data, opted out of the beta program. Doing so does get the app to run in the background as it should but only for a few minutes before the issue persists.
I reported the issue as a bug to OnePlus days ago but no response yet!
Can anyone help with this please?
try removing google from aggressive dose. go to battery, click the three dots on top right side and you can disable aggressive dose from there.
bonham1988 said:
try removing google from aggressive dose. go to battery, click the three dots on top right side and you can disable aggressive dose from there.
Click to expand...
Click to collapse
Thanks.
Aggressive dose isn't enabled.
Actually, I have even tried freezing the app from the multi-tasking windows (clicking the lock toggle at the tip right corner of Google app window) and even that doesn't work.
a77med said:
Thanks.
Aggressive dose isn't enabled.
Actually, I have even tried freezing the app from the multi-tasking windows (clicking the lock toggle at the tip right corner of Google app window) and even that doesn't work.
Click to expand...
Click to collapse
The lock toggle is useless. Half of the time apps are cleared even after that lock. But still your situation seems quite odd. Are you using updated version and if your rooted you can try uninstalling the app and reinstalling it.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
The lock toggle is useless. Half of the time apps are cleared even after that lock. But still your situation seems quite odd. Are you using updated version and if your rooted you can try uninstalling the app and reinstalling it.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
The thing is that I'm not rooted. First phone not to touch since the Galaxy S ?.
Did anyone else lose the dark mode option in the most recent Phone app update? Been running it in dark mode since they released the option but after the last update it's no longer there and I'm back to the stock white.
I've tried force closing, restarted, uninstalling updates, clearing cache. Nothing seems to help and I'm not seeing it being reported anywhere else. I'm running version 26.0.222848963.
hahajoker said:
Did anyone else lose the dark mode option in the most recent Phone app update? Been running it in dark mode since they released the option but after the last update it's no longer there and I'm back to the stock white.
I've tried force closing, restarted, uninstalling updates, clearing cache. Nothing seems to help and I'm not seeing it being reported anywhere else. I'm running version 26.0.222848963.
Click to expand...
Click to collapse
Yeah I did, that sucks
Weird because the changelog mentions the addition of dark mode. Maybe it's a server side rollback again.
Same here. Lost it before I did the December update.
Thankfully have pitch black theme installed via substratum.
Mine is working.
Sent from my [device_name] using XDA-Developers Legacy app
Eudeferrer said:
Mine is working.
Click to expand...
Click to collapse
Same mine is working
hahajoker said:
Did anyone else lose the dark mode option in the most recent Phone app update? Been running it in dark mode since they released the option but after the last update it's no longer there and I'm back to the stock white.
I've tried force closing, restarted, uninstalling updates, clearing cache. Nothing seems to help and I'm not seeing it being reported anywhere else. I'm running version 26.0.222848963.
Click to expand...
Click to collapse
Gone here too.
I don't see the option to enable it either
I never had the option.
I got my phone two weeks ago with the November update and have never seen the option in the phone app, same in December.
Try this: Settings/Display/Advanced/Device theme - set to dark
Sent from my crosshatch using XDA Labs
They disabled it in the official v26 update. Enroll in the beta program here and it should reappear.
Sent from my Pixel 3 XL using Tapatalk
bigdave79 said:
They disabled it in the official v26 update. Enroll in the beta program here and it should reappear.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Thanks, that did it for me.
What's annoying for me is i sideloaded the beta APK, which gave me dark mode, but took away call screening!
Crepusculi said:
What's annoying for me is i sideloaded the beta APK, which gave me dark mode, but took away call screening!
Click to expand...
Click to collapse
I signed up for the beta, let it update itself, have dark mode which is great, and call screening works just as before.
samnada said:
I signed up for the beta, let it update itself, have dark mode which is great, and call screening works just as before.
Click to expand...
Click to collapse
Wonderful! Worked!
I went back to OOS 11 without any real issues.
The problem is that I keep getting the notice to update to 12. Automatic updates is turned off in Developer and download over wifi is off in settings so I'm not concerned about the update downloading, but how do I stop getting the update notification every tine I reboot?
https://www.reddit.com/r/oneplus7t/comments/ttr2c9/_/i3cm8pf
... with adb and a pc.
Regards
Check out the app called TidyPanel Notification Blocker in the Play Store. That's what I always used.
thor2001 said:
https://www.reddit.com/r/oneplus7t/comments/ttr2c9/_/i3cm8pf
... with adb and a pc.
Regards
Click to expand...
Click to collapse
Thanks
Do you still get the notification?
wfred said:
Thanks
Do you still get the notification?
Click to expand...
Click to collapse
You only see the notification, if you go into settings menu at the top (blue circle) but not in the notification area (2nd picture).
If you click on the notification (inside the settings), nothing happens because the called app can't be executed.
Regards