I have a strange problem with google play services 7.5.71. As you can see in the image SystemUpdateService is disabled and that's the problem that phone can't go in deep sleep. If i enable it is ok but after restart it is disabled again.
What can i do for this? (I don't want the solution to disable receivers as i have seen it)
You can do the solution to deny two permission that avoid the deep sleep
@manthes
Settings-Privacy-Privacy Guard-Advanced-Google Play Services-Keep Awake-Denied
Kirya12347 said:
@manthes
Settings-Privacy-Privacy Guard-Advanced-Google Play Services-Keep Awake-Denied
Click to expand...
Click to collapse
It didn't help and as i said the problem with deep sleep is that SystemUpdateService is disabled. I want it to be enabled to solve the problem but after reboot it disables itself
Maybe a script to enable it if someone know how to do it
manthes said:
It didn't help and as i said the problem with deep sleep is that SystemUpdateService is disabled. I want it to be enabled to solve the problem but after reboot it disables itself
Maybe a script to enable it if someone know how to do it
Click to expand...
Click to collapse
What rom do you use? If one of mine, this service disabled in overlays. But for me it didn't caused any problems.
[email protected] said:
What rom do you use? If one of mine, this service disabled in overlays. But for me it didn't caused any problems.
Click to expand...
Click to collapse
No i am using Carbon.
manthes said:
No i am using Carbon.
Click to expand...
Click to collapse
Maybe there it's also disabled in overlays...
Anyway, try to uninstall updates of play services and update it manually from play market.
It didn't help. I have done it and installed also 7.5.73 but it is the same. Because i like this rom do you know if it will help a script to enable it every time phone boots?
And something strange. As i said enabling it deep sleep problem disappeared on Carbon rom. However i restored liquid smooth, it has also disabled systemupdate service but it goes to deep sleep
I have gone back to liquid and until a few days i didn't have any problem with 7.5.73 but it starts with 7.5.74.
Until now i disabled the automatic updates of google services but because i want a more permanent solution can any developer help me in which file of framework-res.apk i can find the lines fo SystemUpdateService?
Related
I've been having this wakelock for a while and I can't figure it out. Haven't found anything about it online. Cleared all apps turned on airplane mode and everything. Nothing works. It only stops with a reboot and then appears at random times. Any help would be greatly appreciate!
It's the emergency broadcast thing. I've unchecked all of them and I still get it. The only way to fix it is to poweroff/on.
Does anybody know a way to control this wakelock? Maybe using amplify?
It's been persistent for me, keeps coming back...
leffer said:
Does anybody know a way to control this wakelock? Maybe using amplify?
It's been persistent for me, keeps coming back...
Click to expand...
Click to collapse
Having the same issue.
The only way to fix it is to reboot, but after few hours it will come back.
Disabled in franco kernel
I can't install 3rd party sources all of a sudden. I can load the Install or Cancel screen. Cancel works, but it won't let me install, what could be wrong? Obviously unknown sources is check.
Edit: it seems that the UI for install is broken. I can't active device administrator apps either, can't cancel or activate. I am 100% stock rooted.
roberto15359 said:
I can't install 3rd party sources all of a sudden. I can load the Install or Cancel screen. Cancel works, but it won't let me install, what could be wrong? Obviously unknown sources is check.
Edit: it seems that the UI for install is broken. I can't active device administrator apps either, can't cancel or activate. I am 100% stock rooted.
Click to expand...
Click to collapse
Try deactivating any screen related apps like LUX, or any screen filter apps
I agree with the previous post. I've experienced this exact issue in the past with other phones and it was frustrating until I finally figured out what was happening. I've had it happen with Lux and CF.lumen (though not with CF.lumen in quite some time). Temporarily disabling these apps should enable the install button.
dcdruck1117 said:
I agree with the previous post. I've experienced this exact issue in the past with other phones and it was frustrating until I finally figured out what was happening. I've had it happen with Lux and CF.lumen (though not with CF.lumen in quite some time). Temporarily disabling these apps should enable the install button.
Click to expand...
Click to collapse
Lol yupp, it was at night was using screen filter lmao!
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,
I have a OnePlus 3 which is about 7 months old now. I'm running stock 6.0.1 (OOS 3.2.7) with Xposed. ElementalX kernel and TWRP recovery (if that matters) ... I use Kernel Adiutor for a few misc tweaks (vibrator, LED, hostname) and AKT Profiles is set to Fusion Conservative - which limits GPU as well. I have been using various Xposed modules without any issue until the following happened.
I had installed Parallel Space - an app which allows dual WhatsApp capability. I started experiencing random soft reboots and shutdowns. So I uninstalled it. Then I cleared cache and ART cache. I also uninstalled a few apps that I had installed in the past month.
I am still experiencing reboots and I cannot pinpoint the cause. The reboots/shutdowns occur when the screen is off. Always when the screen is off.
I'm bad at reading logs, so can't figure out from the logcat either.
Anyone who can help me out, will be greatly appreciated! I will provide all logs as necessary.
[EDIT] Solution: Do not let any app make use of the proximity sensor to manipulate the screen. For example, apps which switch off the screen when flipped might be the culprit.
Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something
cl0g said:
Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something
Click to expand...
Click to collapse
Nope, no Magisk. Only Xposed.
Providing logs from logcat. Will provide anything else if required.
A few more logs containing fatal errors.
I thought the problem was solved by uninstalling this app called "Pixoff", but no, it still persists. Also, the LED is glowing orange, without any notification pending. During screen on as well as off.
Can you please flash stock ROM and check once if the same problem persists?
hrishikeshgramani said:
Can you please flash stock ROM and check once if the same problem persists?
Click to expand...
Click to collapse
That is what I'll have to do if changing settings or regular fixes don't work... But I don't want to jump to it right now because there's a lot of tweaks I'm running and they will be destroyed.
Also, it was running perfectly until last week. I have uninstalled all apps that I got in the last month. Cleared ART cache and normal cache. Haven't restored to factory settings yet.
I'm experimenting with disabling Xposed modules one by one, although I don't think it's a module problem - because I've had them since eternity.
What I have concluded is - I downloaded a rogue app from the Play Store which has left it's data and that is the cause of reboots... I might be wrong though.
Hence, I would really appreciate if someone would go through the logs and figure it out.
I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.
cl0g said:
I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.
Click to expand...
Click to collapse
Will do that next time, thanks!
Okay, so I figured this out. Proximity sensor is having issues. I had enabled "Proximity wake" in GravityBox and that was causing problems. Disabled it and Everything was fine as ever.
To verify that proximity sensor was at fault, I tried Pixoff's flip to Black screen feature - it uses the proximity sensor to figure whether device is in pocket or flipped... And yes, phone rebooted there too.
Phone is running fine as long as the sensor is used only during calls (to switch screen off)
But what I cannot understand is why this is happening in the first place! I mean, proximity sensors are supposed to be used in this manner only, right?
Nevertheless, if anyone wants to help, they are welcome. Otherwise my issue is solved.
I've only noticed this since running the August security updated and its happened across three ROMs so far (Screwed, Pure Nexus, LOS (No gapps)). Sometimes the screen takes for ever to power up. Once it is up the lock screens responsiveness varies greatly. Not always in the same instance as the screen issue but when unlocking the device it will momentarily freeze. Sometimes locking itself again..
Curious if anyone has seen anything similar.
How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.
jhs39 said:
How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.
Click to expand...
Click to collapse
I'm restoring from tibu.
pcriz said:
I'm restoring from tibu.
Click to expand...
Click to collapse
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.
jhs39 said:
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.
Click to expand...
Click to collapse
It's happened without any apps installed as well. I haven't tried safe mode yet no
are you using immersive mode?
diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.
pcriz said:
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.
Click to expand...
Click to collapse
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug
diabl0w said:
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug
Click to expand...
Click to collapse
Yeah that would make sense if you are seeing the same thing. I may jump back to a known good build and see what happens
I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.
pTeronaut said:
I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.
Click to expand...
Click to collapse
Thank you, I'll try that!
diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?
p1r473 said:
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?
Click to expand...
Click to collapse
Check this thread. ?
https://forum.xda-developers.com/pi...e-problems-t3666479/post73629247#post73629247