Related
Hi all
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
thx
This same problem,
S III, rom > http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
Xposed framework installed
Greenify is device administrator
I have full version
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
If I may make a suggestion?
I started getting the same error message (it started right after I paid for the app). After reading "thousands" of pages I think I may have hit on the answer. Greenify is in "boost" mode, that somehow, even though it uses xposed framework, doesn't need root. So I checked supersu and greenify wasn't listed. Then I changed to "root" method and greenified an app, then supersu asked to allow greenify, thereby now having it listed again in supersu.
I then changed it back to "boost" and so far haven't had that error. Coincidently, Greenify seemed to work ok anyway even with that error.,
edit: well that blows, I started to get the error message again, so disregard what I wrote above. Maybe a fix is coming, or I'll live with manually starting auto-hibernation.
tnsmani said:
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
Click to expand...
Click to collapse
No, I check this 3 times ...
colin p > nothing, still this same problem
anyone has ideas, what else, I can do ?
Just to add additional info, this auto-hibernation error only started after I bought the Donation Package. I don't know if it's something to do with the additional options or not. Before I bought the program, auto-hibernation worked fine.
I have a Nexus 4 (rooted with towel-root) and SuperSu and of course the Xposed framework. I uninstalled/re-installed Greenify, as well as the Donation Package and still the error pops up the first time I open Greenify. I then have to manually start auto- hibernation and it works ok after that, at least it "seems" to as everything is under the hibernated section.
After I re-installed, SuperSu asked to allow Greenify root access, so it is properly listed. I would imagine that if a significant few of us have the issue, a future update will address the error problem.
I would like to try to enable Greenify as root mode. Will the message appear?
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
This is not a definite fix, though in some weird circumstances, it might work
TechnoSparks said:
I would like to try to enable Greenify as root mode. Will the message appear?
The message appears in either root or boost mode on the first time the program is opened after a boot up.
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
Tried your suggestion and still get the "auto-hibernation has stopped" error.
This is not a definite fix, though in some weird circumstances, it might work
Click to expand...
Click to collapse
Unfortunately, no dice. Still get that error, thanks anyway.
By George...
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
colin p said:
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
Click to expand...
Click to collapse
No problem mate. If it really works for a long time, it might be good to report here as I may take your method as a suggestion to other people facing the same problem as well. :good:
romdroid. said:
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
Click to expand...
Click to collapse
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
I had not got this message for quite a long time, but after updating to beta 2, the first time I rebooted and opened Greenify, I got this message. Afterwards, for the whole of today, I haven't got it.
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
gorilla p said:
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
Click to expand...
Click to collapse
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
tnsmani said:
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
Click to expand...
Click to collapse
for me i have to enable it in accessibility after every restart of the phone ....
Anyone found a solution to this? I am getting the same error.
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
HI Oasis - just to reply that I am still getting Auto-hibernation stopped with Greenify v2.5.1
Basically after a while auto-hibernate just seems to stop. I have all my apps waiting to be hibernated even after a few hours of screen off. I do not get the 3rd party message saying auto-hibernation is stopped. I have Accessibilty on and have given Greenify Device Administration rights.
I will get the 3rd party message if I force close Greenify or if I reboot. In those cases Accessibility will have turned itself off. After turning Accessibility back on, the message disappears but I still have apps waiting to be hibernated after seveal hours of screen-off.
After every reboot, I find that Greenify does not seem to ask SuperSU for root access. Even though I've granted Greenify automatic access,the log files for SuperSU never show Greenify as either being granted or denied rights. I know that Greenify is meant to ask for those rights when the screen is off. I guess it might be another app is locking the device when the screen is off before Greenify can ask for access. I've tried removing Device Admin privileges for other apps and remove PIN unlocks but this does not seem to help.
The only way I have managed to get Greenify running again is to uninstall and reinstall, which seems to be the only way when the screen is on that I can get it to request root access via SuperSU. This does mean I cannot use the Xposed installer options, because I would first need to reinstall Greenify, grant it root access via SuperSU, then enable the XPosed module, then reboot. But after reboot SuperSU access seems to be withdrawn and I can't get it to request root unless I uninstall and reinstall.
I'm sure I'm missing something but I'm not sure what. I am not sure if there is a way of forcing Greenify to request SuperSU access even when the screen is on without having to reinstall.
I am rooted with SuperSU 2.4 and Xposed installer, HTC One on Viper 7.02 ROM, Greenify 2.5.1 with donation package.
EDIT: I've found that I can get Greenify to ask for Root Access through Xposed if I first degreenify Facebook, re-greenify Facebook, launch another app which wakes up Facebook (eg Agoda) and then request Greenify to cut-off the wake-up. Seems to be working.
EDIT2: Alas, still having problems. Usually nothing auto-hibernates after charging the phone. Yesterday it was working fine, today I unplugged, started some apps, closed the phone and went for breakfast. 1.5 hours later the apps were still waiting to hibernate. Am completely lost on what to do next.
Dronak said:
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Click to expand...
Click to collapse
I occasionally get this message, generally after an update to Greenify, but just tap on the message and continue on with my day. After exhaustive (I'm rather OCD) research, the general consensus is to forget about it as it is just Greenify's way of letting you know that the auto-hibernation has stopped and needs to be restarted. I have gone without tapping on that message and the service still starts up all by itself.
My advice is to open Greenify after an update (updates have slowed considerably anyway) and just tap on the message and it will be good to go until the next update.
Thanks for the response. I have been tapping on the message when I notice it, but it still seems to appear without updates to Greenify. I've tried checking a little more, though probably not as exhaustively as you did, and I suspect that there's some kind of conflict with Tasker. One of the main things I do with Tasker is alternate between "home" and "work" modes, part of which involves using a screen lock for "work" and turning it off for "home". It seems like when things are working fine at home, I go to work making it switch to work mode, and return home at the end of the day going back into home mode, Greenify complains. Since Greenify only works without a screen lock in non-root mode, I'm guessing this switching may be affecting thing, but I'm not completely sure. I guess I just have to live with it. One thing I've tried doing to mitigate the problem is add a Greenify hibernate action to my Tasker profile for turning mobile data off when the screen goes off. I'm not sure how well it's working, because at work I normally hibernate manually and at home I often don't worry about it, but even if it's not working, I think I get a placebo effect of thinking it's doing *something* so I'm less concerned about checking to see if Greenify has stopped auto-hibernating.
So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
peste19 said:
So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
Click to expand...
Click to collapse
Do you have experimental mode enabled? I think you need the donation pack as well as root to greenify system apps.
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Has anyone noticed some improvements using greenify with s6?
peste19 said:
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Click to expand...
Click to collapse
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
isangelous said:
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
Click to expand...
Click to collapse
how did you use tasker to enable the hibernation? i am a bit new at this
peste19 said:
how did you use tasker to enable the hibernation? i am a bit new at this
Click to expand...
Click to collapse
I just had a look but unfortunately I don't have the profile anymore to export it for you.
Doing it from scratch would be a bit daunting if you have never used Tasker before.
You basically need to:
1. Set a variable for the display state (ie, on, off and unlocked). %DisplayState
2. Have a task for the screen unlock which sets a variable %NeedToGreenify or similar.
3. Have a task for the when screen off event triggers and %NeedToGreenify is set. This task waits 10 minutes. Then check if the screen is still off - this is what %DisplayState is for (Stop if it is not). Clear %NeedToGreenify. Trigger Hibernate (Greenify is a 3rd Party Plugin). Wait 30 seconds. Turn the screen off "SecureSettings - LockDevice".
I think I may have also used SecureSettings to keep the screen on while the process is running. You will also need to set the task options to "abort existing task" if it is already running.
I think this is how it worked, but it was a while ago :/
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Same issue here
Hi there.
Unfortunately I don't have a solution but just wanted to let you know that I have exactly the same problem. My Sony Xperia Z2 updated to Lollipop last friday and since then I get this annoying "capaciteit voor NFC-services is vol" message (it's in Dutch ) When I click on 'change settings' a new window is opened where it is not possible to change any setting. Switched NFC on and off but doesn't seem to do anything. The message keeps popping up irregularly...
Very annoying issue. Hope someone finds a solution.
Exaclty the same issue here
Vanaglory said:
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Click to expand...
Click to collapse
Unfortunately I am also haveing the same issue. It's very annoying.
Vanaglory said:
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Click to expand...
Click to collapse
Try Factory Reset
There must be a better way than just a factory reset, and not sure if that would actually solve the issue.
Just chiming in that I updated to Lollipop on my Z3 last night and am encountering the same issue.
dreamoo said:
There must be a better way than just a factory reset, and not sure if that would actually solve the issue.
Just chiming in that I updated to Lollipop on my Z3 last night and am encountering the same issue.
Click to expand...
Click to collapse
Just got this problem myself this morning on my Z2 running Lollipop. Did you manage to find a fix?
I can't seem to find anything other than this post concerning this issue.
Thanks.
Same Problem
I did a factory restore and I am still getting the same issue.
Same here
I'm experiencing the same thing. Upgraded to Lollipop last month, but this only started a couple days ago. Not after installing a new app. Got low on disk space, which triggered a back up alert. Cleaned out my pics, but then started getting this error.
Xperzia Z3 Compact
Model D5803
Bell Mobility Canada
Android 5.0.2
Kernel version
3.4.0-perf-g72984dd
[email protected] #1
Fri Feb 27 18:06:32 2015
Build Number 23.1.A.0.726
Vanaglory said:
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Click to expand...
Click to collapse
I think I figured it out. Suggested a bunch of apps that had bee recently updated on reddit, and the common denominator was the Scotiabank app, updated a few days ago.
Uninstalled, no NFC errors. I have written the dev, and hope for a response soon. That seems to be the cause, so check it out and post if it works for you.
Solution: Clear Google Play Services and NFC Service Data in Safe Mode
Don't know if this is a solution but it worked for me.
1) Boot into Safe Mode.
2) With NFC off, clear all data from NFC Service and Google Play service via Settings>Apps>All.
2.a) Clear data from any Mobile Payment/Banking App and any NFC enabled app.
2.b) Under the running apps, select via the top right dots to view cached apps.
2.c) Delete (Stop) them all. It can be tedious as some won't stop before others but persist and it can be done.
3) Restart phone and error is gone.
thanx, worked for me as well. remainings of android pay caused the problem on my mobile.
Hi Guy !
Same problem here.
Unfortunately no Scotia Bank, noting...
And when i get this message, it says that is current capacity used is.... 0%!!!
I begin to hate this phone :s
Thanks if you have any tip.
Laurent
I've got a Z3 compact that I recently downgraded from LP to KK (no root). Upon booting into KK for the first time, a toast notification appeared stating that the NFC firmware was being updated. After that, the google play services updated and then this stupid "Capacity for NFC Services Full" message kept popping up. It only seems to pop up randomly and only goes away when I disable NFC, but I can't seem to get rid of it using any of the methods mentioned in this thread. Has anyone else ran into this? I've completely wiped my phone twice and continue to have the same issue.
All google searches result in useless forum threads about the Scotia Bank app causing this issue. I don't have that app, so it's gotta be something else.
PuffDaddy_d said:
I've got a Z3 compact that I recently downgraded from LP to KK (no root). Upon booting into KK for the first time, a toast notification appeared stating that the NFC firmware was being updated. After that, the google play services updated and then this stupid "Capacity for NFC Services Full" message kept popping up. It only seems to pop up randomly and only goes away when I disable NFC, but I can't seem to get rid of it using any of the methods mentioned in this thread. Has anyone else ran into this? I've completely wiped my phone twice and continue to have the same issue.
All google searches result in useless forum threads about the Scotia Bank app causing this issue. I don't have that app, so it's gotta be something else.
Click to expand...
Click to collapse
It's caused by latest versions of google play services app. Older versions doesn't have this bug. Uninstall google play services update and "Capacity for NFC Services Full" message is gone forever. But I know It isn't a solution Only google can fix it...
Makiavell said:
It's caused by latest versions of google play services app. Older versions doesn't have this bug. Uninstall google play services update and "Capacity for NFC Services Full" message is gone forever. But I know It isn't a solution Only google can fix it...
Click to expand...
Click to collapse
Yeah, I figured Google Play Services was the issue, but if I uninstall and roll back to the original version the phone ships with, it isn't compatible with Google apps (music, youtube, etc). I was just hoping there was a better fix. For now, I've simply disabled NFC and turn it on before I use Android Pay. The extra clicks aren't really a big deal since I don't have a fingerprint scanner and need to touch the screen to unlock anyway. Plus, I don't use AP often enough to bother me. Thanks for the confirmation though!
Edit - after further thought, if Google Play Services is the cause, then why aren't more people affected by this and why wasn't my device affected all along. I only recently rolled back to KK and this issue started. The Google Play Services version is still the same, right?
As an Android developer who is working on NFC payment in a mobile wallet, I can tell that our team identified the source of the problem to reside in Sony's Android modifications. No other platform produces these errors. I can't yet link the forum thread, but google for "sony xperia off host apdu service capacity full", the result from talk.sonymobile.com will show further details.
So you can probably stop looking for the cause in Google products, or 3rd party wallet/banking apps. They (we) also suffer from this issue.
Sony isn't responding in the referenced thread, so this may not be fixed soon.
Sorry to tell bad news.
my phone has this issue today, it began right AFTER i did a factory reset... just wanted to clear it off and start again... now this??
davidkeithhaines said:
Don't know if this is a solution but it worked for me.
1) Boot into Safe Mode.
2) With NFC off, clear all data from NFC Service and Google Play service via Settings>Apps>All.
2.a) Clear data from any Mobile Payment/Banking App and any NFC enabled app.
2.b) Under the running apps, select via the top right dots to view cached apps.
2.c) Delete (Stop) them all. It can be tedious as some won't stop before others but persist and it can be done.
3) Restart phone and error is gone.
Click to expand...
Click to collapse
The scary thing is this post was made 30-JAN-2016 and it's still being experienced.
Bought a Chinese Refurb Xperia Z3 Compact.
Android 4.4.4
Build 23.0.A.2.98
I'd only installed FTP Server Pro (to test 802.11ac bandwidth) by The Olive tree on an otherwise stock Z3C and after enabling NFC, the "NFC full" error message started popping up.
I followed the instructions above and managed to clear the cache/data on everything except one Twitter service which I couldn't stop.
After a reboot from safe mode, the phone is not showing the NFC error message.
I have enabled NFC and used it with a couple of NFC Bluetooth speakers and NFC tags around the house and it's working without errors.
Fingers cross, I won't see this message again.
Thnx
My Z3 Compact was running Android 5.0.2 since 2.5 years and I never encountered this pop-up. I never used NFC.
I changed to another mobile operator, and as soon as I replaced the SIM in my phone, I started getting this pop-up, saying that the space is 174% used.
I suspect the SIM being pre-configured for Orange Cash, although the application is not installed on my phone.
I tried the various workarounds mentioned in this thread and on Sony's forum, but none worked.
This phone is rooted, and I often get this pop-up when some "sudo" tasks are launched (kill process, freeze application, ...).
I have run out of ideas...
For those who still strugle with this shi* and clearing cache is not working:
1. Download and install any payment app, doesn't matter, won't use. I have Tap & go
2. Enable NFC
3. Go to Touch & pay in device section
4. Change from google play to installed app.
You can now disable NFC, no popup should occure
Hi, Greenify keeps losing access to the accessibility service for some reason. It happens after a few minutes of using the phone, not even a reboot is required to get it unticked again. Then when I try to hibernate+lock screen again, it says that it requires the service for automation to work.
Phone: Huawei Mate 7
System: KitKat 4.4.4
Greenify: latest version
Root? No (Greenify set on non-root mode)
Accessibility activated for Greenify? Yes but keeps getting unticked all the time and asks me to enable automation again and again!
Greenify device administrator? Yes
Donation package? Yes.
Anyone?
Have you noticed any clue on when and what caused the stop of accessibility service?
If you device memory is running low, it may be killed by Android system for more memory for foreground app, especially when playing large game.
oasisfeng said:
Have you noticed any clue on when and what caused the stop of accessibility service?
If you device memory is running low, it may be killed by Android system for more memory for foreground app, especially when playing large game.
Click to expand...
Click to collapse
No it does it all the time, after a few minutes usually. If I lock the screen within a minute or two, it works fine, it later than that, the hibernation service is normally turned off already.
Other Info
Any other updates on this issue? I was running Greenify on my Galaxy S5 with no issues. I just changed over to an S6 Edge and now I'm getting the same problem with Greenify losing its Accessibility permissions. No rhyme or reason for when it happens. I'm not running any big applications or games. I have a few other apps that need Accessibility authorization and those never seem to lose their access like Greenify does.
Same Problem on my new Galaxy S6 edge. Any help to solve the problem would be greatly appreciated.
This can solved by removing Greenify from Protected Apps or in the case of non Huawei phones by disabling battery optimisation for greenify or the app in question.
On my phone gets it often after I kill the any application with /long press/back button. Rooted, CM13
this happen as well with OOS 3.2.1 on OnePlus 3
if you decide to clear recents and the memory as well, it will straight away losing the accesibility access..
Is there an established reason for this?! Reinstalling and add power-saving exception doesn't seem to being helpful.
Issue started after update to android 8. On previous versions never had a tiny problem.
Sent from taptalk
As the title says I can't disable that service I'm using Package Disabler Pro to deactivated every bloatware in my V30 H-931 but every time I try to disable my phone restarts is there a way to disable without having to root my phone?
RAMONis5645 said:
As the title says I can't disable that service I'm using Package Disabler Pro to deactivated every bloatware in my V30 H-931 but every time I try to disable my phone restarts is there a way to disable without having to root my phone?
Click to expand...
Click to collapse
Using Package Disabler Pro on V30 will probably cause lag in your system. You must be coming from an older phone and you don't yet know how newer LG firmware works? You will end up removing stuff the system looks for, which causes lag.
LG has a lot of firmware intertwined. You yank something out, it's not in an isolated silo like the old days. It's like a spiderweb.
Using Titanium Backup to freeze "unwanted" apps/services is better. If you see lag, then you can UNfreeze. Yes, that requires root.
If you mess things up too badly with Package Disabler, then you'll be factory resetting to bring everything back. Lots of people have had to do that. We've had this phone since 2017, so we know how it all works.