Related
At least on cm11 with supersu 2.14.
Back to the version before and all is working.
iamnotkurtcobain said:
At least on cm11 with supersu 2.14.
Back to the version before and all is working.
Click to expand...
Click to collapse
I also use CM11 (20141019) and also SuperSU 2.14
Greenify 2.5 beta 1 is going well with me. :good:
Carpe Noctem 11 said:
I also use CM11 (20141019) and also SuperSU 2.14
Greenify 2.5 beta 1 is going well with me. :good:
Click to expand...
Click to collapse
Wait til you reboot...
iamnotkurtcobain said:
At least on cm11 with supersu 2.14.
Back to the version before and all is working.
Click to expand...
Click to collapse
What's the detailed error and behavior?
oasisfeng said:
What's the detailed error and behavior?
Click to expand...
Click to collapse
I updated greenify to 2.5 beta 1. All seemed good. Then after a reboot it always had this triangle symbol next to the apps that should be hibernated. I tried to reinstall greenify, wiped cache and data of the app and even flashed supersu again.
Nothing worked. It didn't hibernate. Not in root and not in non root mode.
Installed 2.4.4 and all is good again..
iamnotkurtcobain said:
I updated greenify to 2.5 beta 1. All seemed good. Then after a reboot it always had this triangle symbol next to the apps that should be hibernated. I tried to reinstall greenify, wiped cache and data of the app and even flashed supersu again.
Nothing worked. It didn't hibernate. Not in root and not in non root mode.
Installed 2.4.4 and all is good again..
Click to expand...
Click to collapse
Can you confirm root privilege is still granted to Greenify?
oasisfeng said:
Can you confirm root privilege is still granted to Greenify?
Click to expand...
Click to collapse
I deleted root privilege and grand again
iamnotkurtcobain said:
I deleted root privilege and grand again
Click to expand...
Click to collapse
A serious question, have you installed Greenify as a system app?
oasisfeng said:
A serious question, have you installed Greenify as a system app?
Click to expand...
Click to collapse
No. User app. I updated to 2.5 beta 1 on my Samsung Tablet too. Same issue. So it's not just my S5
Beta 2 seems to work ???
I always add Greenify to the administrators list and enable accessability.
Sent from my Nexus 4
Nexus 5, Lollipop 5.0.2. Greenify always tells me 'something is blocking the Greenify service' but I've got all the services enabled and things like that. I checked accessibility, and the greenify option is unticked. It becomes unticked after every reboot.
I'm using the donation and Xposed package, does anybody have any tips to fix this?
Is your Greenify running in root or non-root mode?
Accessibility service only make sense in non-root mode.
oasisfeng said:
Is your Greenify running in root or non-root mode?
Accessibility service only make sense in non-root mode.
Click to expand...
Click to collapse
I too am having the same issue on cm12 nightlies. All my greenify experimental settings are getting unticked after reboot. I'm using built-in root with Xposed and donation package
Accessibility setting- Greenify Off
I am using Xiaomi Redmi 1s and I am also facing this issue. I noticed that the setting get unchecked even without reboot. It will run for some time and when I check greenify , it will be showing greenify (no auto-hibernation..) and several apps will be listed under "waiting for manual hibernation". When I go to accessibility setting, Greenify will be off
I have same issue, was there a fix for this?
Sent from my HTC One_M8
Same problems in cm12s yureka...
I think,
you should make SELinux to permissive mode.
Hello,
I have the same issue. When I reboot the phone all experimental features are unticked/unchecked. I use boost mode (I also try with root mode), Greenify 2.6.2. I have the donation and Xposed package. My phone is a Elephone P7000 on Android 5.0, with SuperSU.
Do you have any solution? What is SELinux?
Thanks
zukŠ° said:
Nexus 5, Lollipop 5.0.2. Greenify always tells me 'something is blocking the Greenify service' but I've got all the services enabled and things like that. I checked accessibility, and the greenify option is unticked. It becomes unticked after every reboot.
I'm using the donation and Xposed package, does anybody have any tips to fix this?
Click to expand...
Click to collapse
oasisfeng said:
Is your Greenify running in root or non-root mode?
Accessibility service only make sense in non-root mode.
Click to expand...
Click to collapse
n30wav3 said:
I too am having the same issue on cm12 nightlies. All my greenify experimental settings are getting unticked after reboot. I'm using built-in root with Xposed and donation package
Click to expand...
Click to collapse
snizams said:
I am using Xiaomi Redmi 1s and I am also facing this issue. I noticed that the setting get unchecked even without reboot. It will run for some time and when I check greenify , it will be showing greenify (no auto-hibernation..) and several apps will be listed under "waiting for manual hibernation". When I go to accessibility setting, Greenify will be off
Click to expand...
Click to collapse
ahac85 said:
I have same issue, was there a fix for this?
Sent from my HTC One_M8
Click to expand...
Click to collapse
remortr said:
Same problems in cm12s yureka...
Click to expand...
Click to collapse
slayer03 said:
Hello,
I have the same issue. When I reboot the phone all experimental features are unticked/unchecked. I use boost mode (I also try with root mode), Greenify 2.6.2. I have the donation and Xposed package. My phone is a Elephone P7000 on Android 5.0, with SuperSU.
Do you have any solution? What is SELinux?
Thanks
Click to expand...
Click to collapse
I followed this guide and everything seems to work.
ROM should have init.d support
Create the 08setperm
Add the lines... Change the permissions with root explorer and Jet set
Follow this guide
http://forum.xda-developers.com/xposed/how-to-set-selinux-to-permissive-boot-t3034245
Sent from my MI 2S using Tapatalk
snizams said:
I am using Xiaomi Redmi 1s and I am also facing this issue. I noticed that the setting get unchecked even without reboot. It will run for some time and when I check greenify , it will be showing greenify (no auto-hibernation..) and several apps will be listed under "waiting for manual hibernation". When I go to accessibility setting, Greenify will be off
Click to expand...
Click to collapse
In MIUI, you need to whitelist Greenify for auto-start settings. MIUI may block and kill the cleaner service of Greenify unless explicitly whitelisted.
NightHeron said:
I followed this guide and everything seems to work.
ROM should have init.d support
Create the 08setperm
Add the lines... Change the permissions with root explorer and Jet set
Follow this guide
http://forum.xda-developers.com/xposed/how-to-set-selinux-to-permissive-boot-t3034245
Sent from my MI 2S using Tapatalk
Click to expand...
Click to collapse
Hi,
I've follow this guide, but on my Elephone P7000 greenify options are uncecked every reboot
Modality Boost.
Edit: I talk about experimental function, of course
Hello,
I have the same phone and I have the same problem...
Sent from my Elephone P7000 using XDA Free mobile app
Skynet969 said:
Hi,
I've follow this guide, but on my Elephone P7000 greenify options are uncecked every reboot
Modality Boost.
Edit: I talk about experimental function, of course
Click to expand...
Click to collapse
If you are using CM then all such users are experiencing this. Go through the other threads.
tnsmani said:
If you are using CM then all such users are experiencing this. Go through the other threads.
Click to expand...
Click to collapse
I use the stock rom, and I have this issue.
Sent from my Elephone P7000 using XDA Free mobile app
tnsmani said:
If you are using CM then all such users are experiencing this. Go through the other threads.
Click to expand...
Click to collapse
I use stock ROM too...
I've just tested 2.7 beta 6 (Xposed alpha-arm64, mod. boost, without setenforce 0,) on my Elephone P7000, and it work perfectly! No lost options.
Skynet969 said:
I've just tested 2.7 beta 6 (Xposed alpha-arm64, mod. boost, without setenforce 0,) on my Elephone P7000, and it work perfectly! No lost options.
Click to expand...
Click to collapse
It's working! Thanks
Sent from my Elephone P7000 using XDA Free mobile app
On my Galaxy Note (the first one) running lineage OS (Android 6.0.1) I get a boot loop as soon as I try to update Greenify to the latest beta version. Currently I'm running an older version from a backup I made in Mars 2017. Any ideas what could be the reason for this issue? By the way, the device is rooted and xposed framework is installed. Any help would be highly appreciated.
I had this problem with the latest beta (3.5.4) and CM 13 (6.0.1) on my Nexus 4. I decided to nuke everything and finally go to Nougat So far no boot loops, however, my Nexus 7 is still on CM 13 so I uninstalled Greenify before it caused the 7 to bork. There seems to be quite a few that had to go through TWRP and remove the Greenify APK manually.
colin p said:
I had this problem with the latest beta (3.5.4) and CM 13 (6.0.1) on my Nexus 4. I decided to nuke everything and finally go to Nougat So far no boot loops, however, my Nexus 7 is still on CM 13 so I uninstalled Greenify before it caused the 7 to bork. There seems to be quite a few that had to go through TWRP and remove the Greenify APK manually.
Click to expand...
Click to collapse
Yes, that's how I fixed it too. Is this thread the right way to let the devs of Greenify know?
I would think so, however, there is a couple postings about this issue in the Beta 3.5.4 thread anyway.
edit: nevermind
I was wondering if anyone else aside from people in https://forum.xda-developers.com/apps/greenify/beta-greenify-3-1-build-1-1-23-2017-t3544311 were experiencing bootlooping with the latest beta. Guess the answer is yes.
Today I updated the app from the play store (no BETA) and get bootloop on my Moto E2 with CM13.
azul12 said:
Today I updated the app from the play store (no BETA) and get bootloop on my Moto E2 with CM13.
Click to expand...
Click to collapse
me too.. yo bro @oasisfeng help us please... :crying:
azul12 said:
Today I updated the app from the play store (no BETA) and get bootloop on my Moto E2 with CM13.
Click to expand...
Click to collapse
I got it, too, on CM12.1
This version is made compatible with Android Oreo, so I believe that it's the compatibility issue.
On my phone, crashed everything and entered infinite bootloop.
You guys with bootloops might want to post in the Google+ Greenify group. Oasisfeng doesn't seem to be monitoring XDA based on no recent posts here. He does monitor Google+ Greenify.
altae said:
Yes, that's how I fixed it too. Is this thread the right way to let the devs of Greenify know?
Click to expand...
Click to collapse
colin p said:
I would think so, however, there is a couple postings about this issue in the Beta 3.5.4 thread anyway.
Click to expand...
Click to collapse
azul12 said:
Today I updated the app from the play store (no BETA) and get bootloop on my Moto E2 with CM13.
Click to expand...
Click to collapse
DhaniBaho said:
me too.. yo bro @oasisfeng help us please... :crying:
Click to expand...
Click to collapse
elenhil said:
I got it, too, on CM12.1
Click to expand...
Click to collapse
azul12 said:
Today I updated the app from the play store (no BETA) and get bootloop on my Moto E2 with CM13.
Click to expand...
Click to collapse
Yea for me too. Moto G, CM13.1
Btw what is the google+ page?
https://plus.google.com/communities/103850238949791125024
Pupet_Master said:
Yea for me too. Moto G, CM13.1
Btw what is the google+ page?
Click to expand...
Click to collapse
Greenify causes Boot Loop on Galaxy Note 8 + RR MM
seems to kill all 6.0 devices
Boot into TWRP, mount system and then use the built-in TWRP file manager to delete the app's containing folder from system/app, then reboot.
heroftimedark said:
Greenify causes Boot Loop on Galaxy Note 8 + RR MM
seems to kill all 6.0 devices
Click to expand...
Click to collapse
Latest updates work fine on my two very different devices (one being a Moto G4) running Android 6 based ROMs. What you are seeing in the forums does not reflect the much larger community that is not experiencing a problem.
I am not being dismissive; just trying to keep things in perspective. Hopefully a fix comes out soon.
Davey126 said:
Latest updates work fine on my two very different devices (one being a Moto G4) running Android 6 based ROMs.
Click to expand...
Click to collapse
Happened to my lg g3 and samsung note 8 (old) running cm13 and RR 6.0 Roms. I also use xposed and many other apps but managed to pinpoint the problem with greenify's update from playstore. Im running an older apk for now.
My Huawei phone that bootloops with the latest Greenify beta is Android 6 rooted with Xposed also.
I was wondering if the other phones bootlooping here are also rooted with Xposed.
I have another Huawei with Android 6.0.1 rooted with Xposed that doesn't bootloop with the latest Greenifys .
heroftimedark said:
Happened to my lg g3 and samsung note 8 (old) running cm13 and RR 6.0 Roms. I also use xposed and many other apps but managed to pinpoint the problem with greenify's update from playstore. Im running an older apk for now.
Click to expand...
Click to collapse
heroftimedark said:
Happened to my lg g3 and samsung note 8 (old) running cm13 and RR 6.0 Roms. I also use xposed and many other apps but managed to pinpoint the problem with greenify's update from playstore. Im running an older apk for now.
Click to expand...
Click to collapse
I have noticed many (clearly not all) of those experiencing bootloops traceable to Greenify are running CM or Lineage based ROMs. RR also shares roots with CM. Not sure there is a connection or coincidental. Something to consider.
So, did the latest update solve the problem?
Nope, not for me. I still cannot update...
Gesendet von meinem GT-N7000 mit Tapatalk
Hello, im using samsung galaxy note 2 (n7100) i tried install greenify on 2 custom android 5.1.1 rom first rom unoffical cm12.1 (from ivan meler) second rom aosp (maybe wrong) based android 5.1.1 rom (rom's name is " Nameless 2.1". I got bootloop in the first 5.1.1 while try install greenify 3.6 on package installer. A pop up appear and it said google play crashed and my phone freezed and i got bootloop. In second rom i got random reboot while installing greenify 3.6 on package manager but my phone succes booted but my all apps start to crash if i open they. And i see the greenify in app menu i tried open it but i got random restart again. Then i go to Twrp's file manager and i deleted the greeinfy and my problem solved. Then i go to play store and i tried download the greenify but play store gave error -505 (maybe 501 i dont remeber) code. Then i tried install greenify 3.5.4 but again same error.
In Two rom i installed Xposed 3.1.1 And i get the logs on second rom. And my last words Please help me i want install the greenify it is a magic for android for me.
Same here... I'm using CM 12 on Samsung Galaxy S3 Neo and after 3.6 update everything just crashes. I tried to disable all xposed modules and uninstall some apps but it is still crashing :/
Maivkrzr said:
Same here... I'm using CM 12 on Samsung Galaxy S3 Neo and after 3.6 update everything just crashes. I tried to disable all xposed modules and uninstall some apps but it is still crashing :/
Click to expand...
Click to collapse
S3 Neo here too running CM12.1. Everything crashes after installing either Greenify or Nova Launcher. Disabling with adb makes everything normal again.
Also, are you getting "There is an internal error with your device ...." error too?
No I don't get that message. My phone just crashes when I install Greenify and then he reboots itself. After reboot every app stops working.
It seems that more and more of us is getting this problem. Hope someone will help.
Maivkrzr said:
No I don't get that message. My phone just crashes when I install Greenify and then he reboots itself. After reboot every app stops working.
It seems that more and more of us is getting this problem. Hope someone will help.
Click to expand...
Click to collapse
Greenify v3.6.x seems to cause issues to some people. Try an earlier version.
tnsmani said:
Greenify v3.6.x seems to cause issues to some people. Try an earlier version.
Click to expand...
Click to collapse
I tried earlier versions and same thing happens.
Does Greenify knows about this?
Maivkrzr said:
I tried earlier versions and same thing happens.
Does Greenify knows about this?
Click to expand...
Click to collapse
I don't think that anyone had this issue with the earlier versions. If you have this issue on earlier versions also, then it is possible that the problem lies elsewhere.
I didn't have problems with earlier versions before 3.6.x update. I downloaded older version and same thing happens
Maivkrzr said:
I didn't have problems with earlier versions before 3.6.x update. I downloaded older version and same thing happens
Click to expand...
Click to collapse
In that case check whether the update of ROM, kernel etc have anything to do with it.
If not, do a clean install of your ROM and then install an earlier version of Greenify.
tnsmani said:
In that case check whether the update of ROM, kernel etc have anything to do with it.
If not, do a clean install of your ROM and then install an earlier version of Greenify.
Click to expand...
Click to collapse
Ty, will try
Greenify 5.1 is working.
Maivkrzr said:
Same here... I'm using CM 12 on Samsung Galaxy S3 Neo and after 3.6 update everything just crashes. I tried to disable all xposed modules and uninstall some apps but it is still crashing :/
Click to expand...
Click to collapse
I am also facing this problem on my s3 neo..
and Hey dude which rom do you using now??
---------- Post added at 11:19 AM ---------- Previous post was at 11:16 AM ----------
Maivkrzr said:
Ty, will try
Click to expand...
Click to collapse
Does it work bro??
Greenify!!
When clean install of rom and installing greenify again?
same here guys, updating greenify, nova launcher, faceapp or wikipedia results in bootloop in cm12 and cm13
i found this on google
https://issuetracker.google.com/issues/64434571
Ccr Sharma said:
I am also facing this problem on my s3 neo..
and Hey dude which rom do you using now??
---------- Post added at 11:19 AM ---------- Previous post was at 11:16 AM ----------
Does it work bro??
Greenify!!
When clean install of rom and installing greenify again?
Click to expand...
Click to collapse
No it doesn't work on clean rom... But older versions of greenify work. Download it from apkmirror.
Thanks. And...
Maivkrzr said:
No it doesn't work on clean rom... But older versions of greenify work. Download it from apkmirror.
Click to expand...
Click to collapse
Thanks for your suggestion. And which rom do u now using for the s3 neo i9301i ??
You know about any other stable and best rom for our device??
I have the same problem on my Samsung Galaxy S1 Plus ( i9001 ) with CM 12.1 fresh clean install. Current version Greenify 3.9.5 crashes everything and I end up in a bootloop with optimising apps.
What version did you guys use???
Edit: Authy via YalpStore ends up the same. -.-" I deleted everything with authy in it's name via TWRP File Manager and it booted up again normal.
having the same problem with all pie roms. messenger and whatsapp keeps getting closed in the background, also doesn't give me notifications. I made them "not optimized" in battery optimization but it didn't help.
Same problem here. Running AEX 6.1. with DA kernel.
DragonTerror said:
Same problem here. Running AEX 6.1. with DA kernel.
Click to expand...
Click to collapse
yeah I am on AEX too, but its a common problem through out all roms for me.
@DragonTerror do you use Titanium Backup?
q.sadid said:
@DragonTerror do you use Titanium Backup?
Click to expand...
Click to collapse
No. Never used it...
q.sadid said:
yeah I am on AEX too, but its a common problem through out all roms for me.
Click to expand...
Click to collapse
Try dark ages kernal
Fixed same problem for me on oreo roms
bot88 said:
Try dark ages kernal
Fixed same problem for me on oreo roms
Click to expand...
Click to collapse
DA gives me screen ghost/burn in problems. okay I will try DA again and see if it works. thanks for the reply.
q.sadid said:
DA gives me screen ghost/burn in problems. okay I will try DA again and see if it works. thanks for the reply.
Click to expand...
Click to collapse
As far as i know ghosting problem is related to older firmware, try to update that as well
Cheers
bot88 said:
As far as i know ghosting problem is related to older firmware, try to update that as well
Cheers
Click to expand...
Click to collapse
Tried DA kernel, still the same problem ?
qazi_sadid said:
Tried DA kernel, still the same problem
Click to expand...
Click to collapse
Then it maybe caused by several issues,
1. Old firmware
2. Malfunctioning core gapps
3. Maybe a hardware related problem
4. Restoration of apps using titanium backup
5. Wrong Wake lock blocker settings which prevent phone form waking up on critical wakelock such as gmscore wake locks, which will definitely results in delayed notifications (tested by myself)
Maybe gms dose for magisk can also be responsible.
bot88 said:
Then it maybe caused by several issues,
1. Old firmware
2. Malfunctioning core gapps
3. Maybe a hardware related problem
4. Restoration of apps using titanium backup
5. Wrong Wake lock blocker settings which prevent phone form waking up on critical wakelock such as gmscore wake locks, which will definitely results in delayed notifications (tested by myself)
Maybe gms dose for magisk can also be responsible.
Click to expand...
Click to collapse
Here's my situation:
1. I placed latest global firmware I could get my hands on. I'm not sure was it beta or stable.
2. This is a GApps issue?
3. I'm pretty sure it's not since I came from Havoc 2.0 just 2 weeks ago. Before AEX 6.1 it worked normally.
4. I used Migrate to restore apps.
5. I don't use any wake lock blocker whatsoever
DragonTerror said:
Here's my situation:
1. I placed latest global firmware I could get my hands on. I'm not sure was it beta or stable.
2. This is a GApps issue?
3. I'm pretty sure it's not since I came from Havoc 2.0 just 2 weeks ago. Before AEX 6.1 it worked normally.
4. I used Migrate to restore apps.
5. I don't use any wake lock blocker whatsoever
Click to expand...
Click to collapse
Try latest gapps, or different packages, (mini or micro)
Maybe that can help
:fingers-crossed:
bot88 said:
Then it maybe caused by several issues,
1. Old firmware
2. Malfunctioning core gapps
.............................
Maybe gms dose for magisk can also be responsible.
Click to expand...
Click to collapse
tried everything. tried your solution. tried this Post too : https://forum.xda-developers.com/redmi-note-5/development/rom-havocos-t3807696/post78675837
BUT nothing is working. either its the dosing system they are using in the rom is responsible for this, or the hardware of my phone. I am currrently one AEX 6.2 with DA kernel
q.sadid said:
tried everything. tried your solution. tried this Post too : https://forum.xda-developers.com/redmi-note-5/development/rom-havocos-t3807696/post78675837
BUT nothing is working. either its the dosing system they are using in the rom is responsible for this, or the hardware of my phone. I am currrently one AEX 6.2 with DA kernel
Click to expand...
Click to collapse
I'm pretty sure it's a ROM problem. Tried running without DA kernel and literally nothing changed, except my battery life which worsened a bit. Hoping for a solution or I'm going back to Havoc OS
DragonTerror said:
I'm pretty sure it's a ROM problem. Tried running without DA kernel and literally nothing changed, except my battery life which worsened a bit. Hoping for a solution or I'm going back to Havoc OS
Click to expand...
Click to collapse
I will go back to MIUI 10 tomorrow and see if the problem remains, it will make sure its a pie rom problem.
q.sadid said:
I will go back to MIUI 10 tomorrow and see if the problem remains, it will make sure its a pie rom problem.
Click to expand...
Click to collapse
try havoc os 2.1
latest change log suggest addition of "xiaomi doze" maybe that will help.
bot88 said:
try havoc os 2.1
latest change log suggest addition of "xiaomi doze" maybe that will help.
Click to expand...
Click to collapse
Will do tommorow if I find time for it
I will post my results.
I tried every rom pie rom but couldn't get any of them to work