I installed greenify yesterday, and it has caused my phone crash two times. First time was when I clicked experimental features, second time was when I tried to hibernate a weather app. Both time my phone got stuck, and I can't even turn off the screen. What's the problem?
zhjn921224 said:
I installed greenify yesterday, and it has caused my phone crash two times. First time was when I clicked experimental features, second time was when I tried to hibernate a weather app. Both time my phone got stuck, and I can't even turn off the screen. What's the problem?
Click to expand...
Click to collapse
What is your device and what ROM do you have?
Have you installed the correct version of Xposed installer and APK and is it working?
Is any other Xposed module working on your phone?
If so, please post logs of the crash.
tnsmani said:
What is your device and what ROM do you have?
Have you installed the correct version of Xposed installer and APK and is it working?
Is any other Xposed module working on your phone?
If so, please post logs of the crash.
Click to expand...
Click to collapse
Samsung s6 edge SM-G9250, stock rom. My phone doesn't support Xposed. BTW, where can I find crash logs?
zhjn921224 said:
Samsung s6 edge SM-G9250, stock rom. My phone doesn't support Xposed. BTW, where can I find crash logs?
Click to expand...
Click to collapse
So are you running it on "Unrooted" mode? Have you enabled it in Accessibility and Device Administrator?
Some functions of Experimental Features will not work without Xposed.
For crash logs, you can use ADB if you know how, or Logcat from Play Store.
tnsmani said:
So are you running it on "Unrooted" mode? Have you enabled it in Accessibility and Device Administrator?
Some functions of Experimental Features will not work without Xposed.
For crash logs, you can use ADB if you know how, or Logcat from Play Store.
Click to expand...
Click to collapse
Oh I'm sorry, I rooted my phone and I'm running Greenify on "root" mode. Since my phone freezed and rebooted right after, can apps like Logcat record the crash log? I haven't crashed since I installed "aLogcat" though.
I'm afraid no tool apps on device could log the reboot. You need a connected computer running "adb logcat -v time" to capture logcat around the reboot.
Related
For quite some time I have been using Tasker to do an automatic reboot at 4 am every day. Since upgrading to the new firmware, it no longer seems to work. I check the Superuser log, and it shows that access was granted at the time it was supposed to run, but nothing happened. When go in to try and manually test the reboot command in Tasker, nothing happens there, either. Can anyone else confirm whether this is a problem on their updated phone?
Thanks.
ElMadre said:
For quite some time I have been using Tasker to do an automatic reboot at 4 am every day. Since upgrading to the new firmware, it no longer seems to work. I check the Superuser log, and it shows that access was granted at the time it was supposed to run, but nothing happened. When go in to try and manually test the reboot command in Tasker, nothing happens there, either. Can anyone else confirm whether this is a problem on their updated phone?
Thanks.
Click to expand...
Click to collapse
I am running sense 5.5 v4 and just tried and tasker reboot isn't working for me either, you can probably use a shell script as root to reboot if you can find the command
Hello, I just started getting random reboots from my generic kitkat tablet and I know it's from the ads that's build in the tablet and nothing else because when I turn off Wi-Fi the tablet is fine no reboots what so ever. Now I did download and install an ad blocker it stops the Ad from loading up completely but a loading screen still comes up and that's when it reboots the tablet. As the title states this is a constant thing and it's really annoying, I wish I could install a custom rom or even CWM recovery but since the tablet came out not long ago there aren't any available at the moment.... So if anybody experienced the same issue my question is are there any other way to get the ads to completely in order to stop the reboots? Thanks in advance
i've narrow it down to it being an issue with the Wi-Fi (i've tried factory reset and that didn't work either) and I see that some are having issue with this as well :crying:
If you are familar with ADB I can try to help you if you can get a logcat so we can see what is happening right before the reboot.
timmytim said:
If you are familar with ADB I can try to help you if you can get a logcat so we can see what is happening right before the reboot.
Click to expand...
Click to collapse
THANKS!! but it's been a couple of years since I really dealt with ADB that i think I would need a refresher on how to set it up (which im trying to look up now) and since my tablet came out early during the summer and there's no custom recovery for it im actually curious to create my own for it
Logcat
here's the logcat of my tablet for anyone that may be interested in helping me, thanks in advance
sketch2k278 said:
here's the logcat of my tablet for anyone that may be interested in helping me, thanks in advance
Click to expand...
Click to collapse
You neglected to tell us that you are running Xposed Framework on your tablet :silly:
First, disable all your Xposed Modules and reboot then see if you can duplicate the random reboot problem.
- If yes, uninstall the Xposed Framework and reboot then try again.
- If no, Reenable your Modules one at a time while trying to duplicate until you find the moduile that is causing the reboot.
Can you list the modules that you are running?
If you want to get rid of the advertisements just add the ips to the hosts file in system/etc
timmytim said:
You neglected to tell us that you are running Xposed Framework on your tablet :silly:
First, disable all your Xposed Modules and reboot then see if you can duplicate the random reboot problem.
- If yes, uninstall the Xposed Framework and reboot then try again.
- If no, Reenable your Modules one at a time while trying to duplicate until you find the moduile that is causing the reboot.
Can you list the modules that you are running?
Click to expand...
Click to collapse
Xposed didn't cause it because it was rebooting on wifi once I did a factory reset I attached another logcat this time factory reset settings
I did notice something though... if I disable the wifi then reset the tablet, let it sit for a minute then turn the wifi back on it don't seem to reboot itself like 5-10 seconds it takes a few mins to reboot (unlike if i was to leave the wifi running while resetting)
CLINTZ9 said:
If you want to get rid of the advertisements just add the ips to the hosts file in system/etc
Click to expand...
Click to collapse
how do I do that?
thanks for the help
http://pgl.yoyo.org/as/serverlist.php?showintro=0;hostformat=hosts
add these lines to your hosts file in system/etc/hosts
In my N7, after applying the OTA from 5.0.2 to 5.1 , the tablet is "semi bricked" since it can't boot into the system (well gets into a systemui crash loop not showing anything on the screen but the power off menu..).
I remember that I had an app called "Lockscreen Policy":
https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.deviceadminkeyguard&hl=es
Which did some stuff on 4.2 about hiding lockscreen widgets or something like that.
Now I think this is the app that made this mess, and I want to uninstall it via ADB.
The problem is that it gives out an error saying it's a device administrator (it was indeed)
adb uninstall com.wordpress.chislonchow.deviceadminkeyguard
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
I am not rooted and can't root here without unlocking the bootloader and wiping, which I try to evade. Since I am no root, I can't just pd disable it or something like that..
Anyone could help me? how can I "deactivate" this device manager so I can uninstall it?
Thanks in advance!
Please, can anyone help me with this?
I'm on a urge to deactivate a device manager in ADB and im not rooted (the Ota for 5.1 in my N7 made it semi brick since an app with device manager (lockscreen policy) makes Ui crash it in a loop before it even gets to the lockscreen, so it's absolutely unusable..)
RusherDude said:
Please, can anyone help me with this?
I'm on a urge to deactivate a device manager in ADB and im not rooted (the Ota for 5.1 in my N7 made it semi brick since an app with device manager (lockscreen policy) makes Ui crash it in a loop before it even gets to the lockscreen, so it's absolutely unusable..)
Click to expand...
Click to collapse
Bump.
Anyone?
Newyork! said:
Bump.
Anyone?
Click to expand...
Click to collapse
Thanks for the help. I tried but no info anywhere, and no help here, so I ended up saving and wiping.
RusherDude said:
Thanks for the help. I tried but no info anywhere, and no help here, so I ended up saving and wiping.
Click to expand...
Click to collapse
BTW if that screen lock isn't a system app than you can uninstall it with safe mode
Newyork! said:
BTW if that screen lock isn't a system app than you can uninstall it with safe mode
Click to expand...
Click to collapse
How? If you can't interact with the UI, how do you turn safe mode on ADB so it lets you uninstall it?
RusherDude said:
How? If you can't interact with the UI, how do you turn safe mode on ADB so it lets you uninstall it?
Click to expand...
Click to collapse
If this screen lock comes built in then safe mode won't help you... but if it's a third party app you can boot into safe mode with a button combination (most samsungs it's the power and volume up and middle button) and then you should be able to remove that device admin...
Newyork! said:
If this screen lock comes built in then safe mode won't help you... but if it's a third party app you can boot into safe mode with a button combination (most samsungs it's the power and volume up and middle button) and then you should be able to remove that device admin...
Click to expand...
Click to collapse
No. If the app makes the lockscreen UI crashing (like the one that caused me the problem), safe mode just adds a "safe mode" label in the lowest left part of the screen, it doesn't fix any UI stuff or changes anything . It's useless..
RusherDude said:
No. If the app makes the lockscreen UI crashing (like the one that caused me the problem), safe mode just adds a "safe mode" label in the lowest left part of the screen, it doesn't fix any UI stuff or changes anything . It's useless..
Click to expand...
Click to collapse
Usually third party apps don't run in safe mode....
Newyork! said:
Usually third party apps don't run in safe mode....
Click to expand...
Click to collapse
This one does:
https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.deviceadminkeyguard
Did you find the solution lately?
RusherDude said:
In my N7, after applying the OTA from 5.0.2 to 5.1 , the tablet is "semi bricked" since it can't boot into the system (well gets into a systemui crash loop not showing anything on the screen but the power off menu..).
I remember that I had an app called "Lockscreen Policy":
https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.deviceadminkeyguard&hl=es
Which did some stuff on 4.2 about hiding lockscreen widgets or something like that.
Now I think this is the app that made this mess, and I want to uninstall it via ADB.
The problem is that it gives out an error saying it's a device administrator (it was indeed)
adb uninstall com.wordpress.chislonchow.deviceadminkeyguard
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
I am not rooted and can't root here without unlocking the bootloader and wiping, which I try to evade. Since I am no root, I can't just pd disable it or something like that..
Anyone could help me? how can I "deactivate" this device manager so I can uninstall it?
Thanks in advance!
Click to expand...
Click to collapse
Have you succeeded?
Maybe try to disable using adb?
Even with adb, you needed root in order to fix the problem. It was so retarded, an app made the tablet semi brick after an official OTA..
Try to factory reset but think before you do...
I am using greenify in my mi3 for quite sometime and haven't faced any issue with auto hibernate. But now i don't see greenify service is getting started. My device is rooted but sill it's not working. When i tried to manually hibernate it takes me to the application info screen.
Is this a bug?
Please change the working mode to root, in main menu - Experimental features
oasisfeng said:
Please change the working mode to root, in main menu - Experimental features
Click to expand...
Click to collapse
I didn't notice that option. The issue is resolved.
Thanks...
greenify auto hibernate not working
I have rooted Sony m2 aqua with Android 5.1.1 .I have paid greenify and not working.As i said phone is rooted,service is working,it had administrators privileges,accessibility is turned on greenify is in root mod and autohibernate is enabled but simply dont work.I dont have xposed becouse my bootloader is locked and i dont want to unlock him.
UPDATE app not working with last version on store but it work with 2.8 beta.
what is accessibility? can you explain please?
Black_Focus_X said:
what is accessibility? can you explain please?
Click to expand...
Click to collapse
Accessibility is Device>Settings>Accessibility on your phone. But the Dev had clarified that you need to enable Greenify in Accessibility if you are running Greenify in non root mode and not otherwise.
hi, I am running latest version of greenify (2.8 beta 1), have donation version enabled + root operating mode (i am rooted indeed).
I am running sony concept MM rom (it is a aosp like rom by sony, so no stamina mode or other features by sony, it is mostly aosp marshmallow)
when I try to assign hibernation + lock screen action to a nova launcher gesture, it doesn't work. I can see the toast notification saying greenify was granted root access though. and when I started greenify, I got this message
in LP it worked fine even if stamina was enabled..
I did click on troubleshooting to investigate about the problem, but can't find out what is happening, as there is no stamina mode at all in the rom I am running.
no xposed installed of course in MM (is this the problem maybe?)
I have greenify enabled in accessibility settings EDIT: and greenify is set as device adminstrator in security settings
I don't see anywhere any permissions to enable for granting greenify lock screen permissions
can you guys please help in fixing this? really miss this feature.. TIA! :fingers-crossed:
moly82 said:
hi, I am running latest version of greenify (2.8 beta 1), have donation version enabled + root operating mode (i am rooted indeed).
I am running sony concept MM rom (it is a aosp like rom by sony, so no stamina mode or otheri features by sony, it is mostly aosp marshmallow)
when I try to assign hibernation + lock screen action to a nova launcher gesture, it doesn't work. I can see the toast notification saying greenify was granted root access though. and when I started greenify, I got this message
in LP it worked fine even if stamina was enabled..
I did click on troubleshooting to investigate about the problem, but can't find out what is happening, as there is no stamina mode at all in the rom I am running.
no xposed installed of course in MM (is this the problem maybe?)
I have greenify enabled in accessibility settings
I don't see any permission to enable for locking the screen anywhere
can you guys please help in fixing this? really miss this feature.. TIA! :fingers-crossed:
Click to expand...
Click to collapse
Device>Settings>Security>Device Administrators>Greenify
Enable that.
thanks for the answer and sorry, I forgot to tell in my first post that I had already checked that too (and it is enabled )