Hi, I'm using the last version of Greenify on stock marshmallow rom and I'm not able to cut off paths anymore for apps that wake up by themselves.
There is no "scissors" icon anymore.
Wake up tracker is enabled in settings but I can't enable "enhanced wake up tracker" (a message appears "not supported by the rom")
I'm in root + boost (xposed) mode and I bought donation package.
No problems with previous versions.
Euphorion said:
Hi, I'm using the last version of Greenify on stock marshmallow rom and I'm not able to cut off paths anymore for apps that wake up by themselves.
There is no "scissors" icon anymore.
Wake up tracker is enabled in settings but I can't enable "enhanced wake up tracker" (a message appears "not supported by the rom")
I'm in root + boost (xposed) mode and I bought donation package.
No problems with previous versions.
Click to expand...
Click to collapse
Also running a near AOSP stock MM ROM with root/Xposed and have access to both features. Suggest uninstalling/reinstalling Greenify with a reboot between.
Davey126 said:
Also running a near AOSP stock MM ROM with root/Xposed and have access to both features. Suggest uninstalling/reinstalling Greenify with a reboot between.
Click to expand...
Click to collapse
Thanks for your answer. I did that and installed the last new version (3.2.1) but no effects... One change : when I try to enable enhanced wake up tracker a pop-up appears for one second ("Applying... ") but it still failed saying it's not supported by the rom.
I come from LineageOS 14.1 and I flashed the whole stock marshmallow firmware. Maybe it has something to do with this...
Weird : I tested adb commands to enable wake up cut off for non-root devices (although i'm rooted+xposed)
adb -d shell pm grant com.oasisfeng.greenify android.permission.READ_LOGS
adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
Click to expand...
Click to collapse
Results : cut off paths are back (with the scissors icon) and I have informations on the opened apps ("UI opened xx seconds ago" "Service started by..."). With my "issue" I didn't have these informations anymore.
The strange thing is that I still can't enable enhanced wake up tracker in settings (same message as mentioned before).
Long story short : Although i'm rooted there is something that may block greenify to read/write settings in order to track apps so I have to manually enable wake up cut off via adb commands.
Euphorion said:
Thanks for your answer. I did that and installed the last new version (3.2.1) but no effects... One change : when I try to enable enhanced wake up tracker a pop-up appears for one second ("Applying... ") but it still failed saying it's not supported by the rom.
I come from LineageOS 14.1 and I flashed the whole stock marshmallow firmware. Maybe it has something to do with this...
Click to expand...
Click to collapse
Euphorion said:
Weird : I tested adb commands to enable wake up cut off for non-root devices (although i'm rooted+xposed)
Results : cut off paths are back (with the scissors icon) and I have informations on the opened apps ("UI opened xx seconds ago" "Service started by..."). With my "issue" I didn't have these informations anymore.
The strange thing is that I still can't enable enhanced wake up tracker in settings (same message as mentioned before).
Long story short : Although i'm rooted there is something that may block greenify to read/write settings in order to track apps so I have to manually enable wake up cut off via adb commands.
Click to expand...
Click to collapse
Interesting. I'm vacillating between a near-stock MM build and LinOS 14.1 on a couple devices and haven't run into this...yet. Obviously reduced Geeenify functionality on Nougat w/o Xposed. Appreciate you sharing findings; should be helpful should this issue arise. Hopefully others can offer insight into lingering wake-up tracker issue.
I'm on LOS 13 Greenify 3.0.5.
I noticed an app still started somehow even after I manually hibernate it. wake-up tracker is enabled, wake-up cut-off is enabled.
I'm facing the same issue on 2 Motorola G 2014 devices and 1 Moto E 2015, all on MM roms, root + xposed.
Same here, LineageOS 13 with root+Xposed and donation package, the feature is enabled and even enhanced tracker is enabled but the scissors never show up
Same problem here with Greenify 3.2.2 paid version!!
Samsung Note 3 Neo (SM-N7505) Lollipop 5.1.1 Root Xposed.
I hope on next version to fix it...
Related
For what ever reason ever since I went from 4.4.4 to 5.1.1 (TW) on my Note 4 i have not been able to cut wake lock paths. To be more clear I did not upgrade to 5.1.1 it was a clean flash.The option is no longer there, it no longer even displays the path when an app automatically awakens from hibernation. I'm running the latest beta version of greenify with the donation/zoomed features enabled. Can anyone help?
XBlackChaosX said:
For what ever reason ever since I went from 4.4.4 to 5.1.1 (TW) on my Note 4 i have not been able to cut wake lock paths. To be more clear I did not upgrade to 5.1.1 it was a clean flash.The option is no longer there, it no longer even displays the path when an app automatically awakens from hibernation. I'm running the latest beta version of greenify with the donation/zoomed features enabled. Can anyone help?
Click to expand...
Click to collapse
It works for me even on M.
Is Greenify enabled in Device Administrators?
Are you rooted? If not, have you enabled Greenify in Accessibility?
Are you using Supersu latest version?
tnsmani said:
It works for me even on M.
Is Greenify enabled in Device Administrators?
Are you rooted? If not, have you enabled Greenify in Accessibility?
Are you using Supersu latest version?
Click to expand...
Click to collapse
Yes to all 3. This is so weird. I would like to cut a few paths but I can't even see any wake paths let alone cut any.
I'm having the same Problem. For example i start Instagram, Facebook starts, too, but i can't cut off the wakeup pathes. I'm on Resurrection Remix (CM12.1 - Android 5.1.1) Rom on Galaxy S3 GT-i9300 with Xposed.
I flashed this Rom clean today. Before it was working fine! Greenify Version is 2.6.2 (i don't understand the function of 2.7...)
Any idea?
Some ROM may disable the logcat module of Android by default, please check your ROM configuration tool (if any) to enable logcat.
Any idea where i could find it?
Ok, got it: I had to activate "Android Logging" in Boeffla Config App!
I just started seeing a problem that I thought had been fixed - and now I can't seem to find a solution myself. I had previously had Greenify working happily with the Xposed Framework, but now it has stopped doing so. Every time I enter the Xposed-based Features menu and try to enable anything, I'm taken to the Xposed Setup Guide screen, with only the "ACTIVATE MODULE, REBOOT" button enabled. This in turn takes me to the Xposed Installer; clicking on "Framework" tells me that Xposed framework version 86 (previously 85 - I tried updating but it didn't make any difference) is already active. No amount of rebooting, cache-clearing, or re-flashing seems to help. The problem appears to have re-appeared within the last week or two (I'm not sure exactly, since the only way to know there's a problem is to go into Greenify settings and check). Here are the details of my setup:
Samsung I9300
Cyanogenmod 6.0.1, 26 August 2016 "nightly" version
Greenify version 2.9 (I signed up for Beta within the last 24 hours - but I don't see any indication that I've received any Beta updates)
Xposed Installer 3.0 Alpha 4
Xposed Framework V86-sdk23-arm
The only thing I see in the Xposed log that seems at all helpful is this:
Loading modules from /data/app/com.oasisfeng.greenify-2/base.apk
File does not exist
Anyone have any ideas about what's going wrong here?
Thanks in advance for any light you can shed!
Don Radlauer said:
I just started seeing a problem that I thought had been fixed - and now I can't seem to find a solution myself. I had previously had Greenify working happily with the Xposed Framework, but now it has stopped doing so. Every time I enter the Xposed-based Features menu and try to enable anything, I'm taken to the Xposed Setup Guide screen, with only the "ACTIVATE MODULE, REBOOT" button enabled. This in turn takes me to the Xposed Installer; clicking on "Framework" tells me that Xposed framework version 86 (previously 85 - I tried updating but it didn't make any difference) is already active. No amount of rebooting, cache-clearing, or re-flashing seems to help. The problem appears to have re-appeared within the last week or two (I'm not sure exactly, since the only way to know there's a problem is to go into Greenify settings and check). Here are the details of my setup:
Samsung I9300
Cyanogenmod 6.0.1, 26 August 2016 "nightly" version
Greenify version 2.9 (I signed up for Beta within the last 24 hours - but I don't see any indication that I've received any Beta updates)
Xposed Installer 3.0 Alpha 4
Xposed Framework V86-sdk23-arm
The only thing I see in the Xposed log that seems at all helpful is this:
Loading modules from /data/app/com.oasisfeng.greenify-2/base.apk
File does not exist
Anyone have any ideas about what's going wrong here?
Thanks in advance for any light you can shed!
Click to expand...
Click to collapse
Though I don't have any solutions for you, I note from Xposed log that for me what is loaded is "/data/app/com.oasisfeng.greenify-1/base.apk". I don't know why it searches for greenify-2 for you whereas it loads greenify-1 for me. There is no reference to greenify-2 in my log. Further, the file in /data/app/ is named com.oasisfeng.greenify-1 for me and it contains the base.apk file.
Does this info help you in any way?
Please avoid greenifying Xposed app, this may lead to the issue above.
Hey buddy, it's just simple.
Follow the steps:
1.Go to xposed framework app.
2. Go to modules. (From menu at right top corner)
3.Then just enable greenify.
Comment me if it solved your problem.
Hello!
So to make it as short as possible, I'm using greenify on my NON-rooted Nexus6P (7.1.1), and to get more features, I gave greenify the necerssary permissions through ADB. Now.. Even though I gave the permissions the following is unavailable: Shallow Hibernation, Doze on the go and Wake-up cut off... UNLESS I switch into »root« working mode (as if my devices is rooted), then they are available. BUT the app keep telling me to enable root on my device (the features remains enabled though)? One more time, my device is NOT rooted. But will this still work? Since I HAVE given the permissions?
I hope someone can cast some light over this for me!
Thanks!
@leeswagger,
What version Greenify?
Did you run these adb commands? :
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
You should not select root mode if the phone is not rooted.
In non-root mode, what happens if you add apps to the hibernate list, one or more are running, and you press the Zzz button to hibernate the apps immediately? Do they successfully get hibernated?
divineBliss said:
@leeswagger,
I'm on version 3.0 build 5
I did return to non-rooted mode.
Yes they do get hibernated immediately, and successfully.
And yes I ran the commands on the site you linked to.
Click to expand...
Click to collapse
leeswagger said:
Hello!
So to make it as short as possible, I'm using greenify on my NON-rooted Nexus6P (7.1.1), and to get more features, I gave greenify the necerssary permissions through ADB. Now.. Even though I gave the permissions the following is unavailable: Shallow Hibernation, Doze on the go and Wake-up cut off... UNLESS I switch into »root« working mode (as if my devices is rooted), then they are available. BUT the app keep telling me to enable root on my device (the features remains enabled though)? One more time, my device is NOT rooted. But will this still work? Since I HAVE given the permissions?
I hope someone can cast some light over this for me!
Thanks!
Click to expand...
Click to collapse
From what I remember, doze on the go really just turns off the significant motion detector (SMD) so it won't get kicked out of doze.
The problem in 7.0+ is that this is locked behind the DUMP permission which can't be granted to 3rd party apps at all via ADB (must be system/signed as such). Most likely you are getting an error trying to grant this permission, so the functionality is not tre.
Alright.. I didn't get any errors, but I hear what you're saying, guess I have to get rooted at some point... Thanks for your reply though!
I cant give adb permission to greenify please help me
I don't know how to use adb please help me with any video or post. For complete information about adb permission of greenify
Google for "adb tutorial"
AvishekOfficial said:
I don't know how to use adb please help me with any video or post. For complete information about adb permission of greenify
Click to expand...
Click to collapse
AvishekOfficial said:
I don't know how to use adb please help me with any video or post. For complete information about adb permission of greenify
Click to expand...
Click to collapse
I see that you're obviously new to XDA. You double-posted what is usually not well recognised.
You find my reply to your question here.
divineBliss said:
@leeswagger,
...
Did you run these adb commands? :
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Click to expand...
Click to collapse
Hi.
I can't access such link. Seems to be broken.
Oasisfeng, HELP!
leeswagger said:
Hello!
So to make it as short as possible, I'm using greenify on my NON-rooted Nexus6P (7.1.1), and to get more features, I gave greenify the necerssary permissions through ADB. Now.. Even though I gave the permissions the following is unavailable: Shallow Hibernation, Doze on the go and Wake-up cut off... UNLESS I switch into »root« working mode (as if my devices is rooted), then they are available. BUT the app keep telling me to enable root on my device (the features remains enabled though)? One more time, my device is NOT rooted. But will this still work? Since I HAVE given the permissions?
I hope someone can cast some light over this for me!
Thanks!
Click to expand...
Click to collapse
How to Set Up Greenify Without Root & Save Battery Life on Any Android
Despite newer phones having larger batteries, after a few months, my battery life drops significantly. I started researching solutions after my third phone. No matter who I asked, the most recommended solution was always Greenify. And unlike other solutions, you don't need root to use it.
android.gadgethacks.com
divineBliss said:
@leeswagger,
What version Greenify?
Did you run these adb commands? :
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
You should not select root mode if the phone is not rooted.
In non-root mode, what happens if you add apps to the hibernate list, one or more are running, and you press the Zzz button to hibernate the apps immediately? Do they successfully get hibernated?
Click to expand...
Click to collapse
Links not available anymore. HELP!
dan60 said:
Links not available anymore. HELP!
Click to expand...
Click to collapse
https://greenify.uservoice.com/knowledgebase/articles/749142-how-to-grant-permissions-required-by-some-features
Does anyone have the commands to allow extra features for non-root phones?
Found this: https://android.gadgethacks.com/how...t-root-save-battery-life-any-android-0201480/
divineBliss said:
@leeswagger,
What version Greenify?
Did you run these adb commands? :
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
You should not select root mode if the phone is not rooted.
In non-root mode, what happens if you add apps to the hibernate list, one or more are running, and you press the Zzz button to hibernate the apps immediately? Do they successfully get hibernated?
Click to expand...
Click to collapse
Hi,
the link isn't available :
Scoop: Catches a stack trace when an app crashes unexpectedly
This module - as the description says - saves the stack trace of a crashing app and displays all crashes in a list so you don't have to look through a long logcat anymore. Additionally you get a notification on every crash (configurable) which already displays the most important information.
This module is based off the module Cracker which sadly isn't being developed anymore so I made an updated version which catches crashes more reliably (supports custom crash handlers set by apps), features material design and contains more functionality such as:
Search in crashed apps
Search in stack trace
Crash preview in notification
Combination of same crashes / apps to avoid long repetetive lists
Crash blacklist
Quick actions to copy / share a stack trace
Download: http://repo.xposed.info/module/tk.wasdennnoch.scoop
Source: https://github.com/wasdennnoch/Scoop
You can help translate this module on GitHub!
Changelog:
1.6.4
Make app search case-insensitive
Use separate view to select text
1.6.3
Add button to toggle selection mode (to avoid a bug where you can't scroll anymore)
1.6.2
Make stack trace selectable
1.6.1
Portugese (BR) and German translation
Option to force English language
1.6.0
Add option to sort crashes by apps
Fix long app names and crash date overlapping
1.5.0
Add option to selectively delete crashes
Add blacklist to filter out crashes from specific apps
Add about screen
1.4.2
Fix nothing working at all. Sorry for the many versions, but I don't have a device to test the Xposed part anymore (I updated to Nougat) and also this is the first time I enabled ProGurad in an Xposed module.
1.4.1
Completely disable module not activated warning as something seems to be broken
1.4.0
Add compatibility with ancient Xposed versions (52)
Add search to overview
Add option to combine same crashes into one item
1.3.2
Fix constant module deactivated warning again
1.3.1
Fix constant module disabled warning
Fix crash when opening detail view
1.3.0
Add option to limit line width
Add search function to detail view
1.2.0
Added Copy/Share buttons to notification (configurable)
Added module not activated "warning"
Improved stack trace preview in notification
Directly open crash details from notification
Minor fixes and improvements (duh)
1.1.0
Fix devious face
Fix self-crash when catching custom throwable subclasses
Minor fixes
1.0.0
Initial release
Click to expand...
Click to collapse
XDA:DevDB Information
Scoop, Xposed for all devices (see above for details)
Contributors
MrWasdennnoch
Source Code: https://github.com/wasdennnoch/Scoop
Xposed Package Name: tk.wasdennnoch.scoop
Version Information
Status: Stable
Current Stable Version: 1.6.4
Stable Release Date: 2017-04-01
Created 2016-12-23
Last Updated 2017-04-01
Amazing, thanks for this Christmas gift
Could you add line break and search in log? Thank you!
KaMyKaSii said:
Could you add line break and search in log? Thank you!
Click to expand...
Click to collapse
Done and available in v1.3.0
(Disabled by default)
MrWasdennnoch said:
Done and available in v1.3.0
(Disabled by default)
Click to expand...
Click to collapse
Thank you. I upgraded from version 1.1.0 to 1.3.0 and now it says I do not have Xposed installed. I've restarted, cleaned up data, reinstalled, same thing. Before clearing the data, by clicking on the crash log of another app, Scoop also crash. Attached are the logs logs
Word wrap is very appreciated!
Version 1.2 and 1.3 does't work on n910f (note 4) running marshmallow 6.0.1
Definitely a good upgrade from the good Cracker.
I have an old S3 on 4.1.2 (that i use for debugging) with xposed version 54, could this beatiful tool work on xposed version lower than 81 like Cracker?
KaMyKaSii said:
Thank you. I upgraded from version 1.1.0 to 1.3.0 and now it says I do not have Xposed installed. I've restarted, cleaned up data, reinstalled, same thing. Before clearing the data, by clicking on the crash log of another app, Scoop also crash. Attached are the logs logs
Click to expand...
Click to collapse
I fixed the warning (yet have to push it), but I need a logcat to resolve the crash. Your one unfortunately didn't contain any crash info. Make sure to capture it during the crash (because the module doesn't always catch itself ).
MrWasdennnoch said:
I fixed the warning (yet have to push it), but I need a logcat to resolve the crash. Your one unfortunately didn't contain any crash info. Make sure to capture it during the crash (because the module doesn't always catch itself ).
Click to expand...
Click to collapse
I took it with the Logcat Extreme app, I hope to be enough. I configured it as verbose, fresh log, main, brief. Let me know if you have any better. You said that Scoop does not log its own crash logs, but actually once here it happened, before clearing Scoop data
KaMyKaSii said:
I took it with the Logcat Extreme app, I hope to be enough. I configured it as verbose, fresh log, main, brief. Let me know if you have any better. You said that Scoop does not log its own crash logs, but actually once here it happened, before clearing Scoop data
Click to expand...
Click to collapse
I said "not always"
I fixed it in v1.3.1. The fault was a misconfigured Proguard which removed more than it should have. I enabled Proguard for debug builds to avoid such issues in the future.
MrWasdennnoch said:
I said "not always"
I fixed it in v1.3.1. The fault was a misconfigured Proguard which removed more than it should have. I enabled Proguard for debug builds to avoid such issues in the future.
Click to expand...
Click to collapse
No more crashes, but the notification that Xposed is not installed persists. I updated the module, cleaned data and rebooted
Edit: Looking at this screenshot I recommend future features like search in the main screen, grouping of same app logs and individual exclusion
KaMyKaSii said:
No more crashes, but the notification that Xposed is not installed persists. I updated the module, cleaned data and rebooted
Looking at this screenshot I recommend future features like search in the main screen, grouping of same app logs and individual exclusion
Click to expand...
Click to collapse
Now it should be fixed. Problem is I can't test it because I updated to N and thus don't have Xposed anymore, so I had to try different ways. And of course it was Proguard again.
I'll add the search soon, I thought of only searching for different apps though and not searchin the short description. Not sure how I should approach the grouping but it's possible too. With exclusion you basically mean blacklisting?
Xposed bridge version
Xposed installer tells me that I need Xposed bridge version 81. There are no updates for the XPosed bridge for me and the current version is 54, so I think that's a bug.
Fabian R�ling said:
Xposed installer tells me that I need Xposed bridge version 81. There are no updates for the XPosed bridge for me and the current version is 54, so I think that's a bug.
Click to expand...
Click to collapse
The newest available version is 87, but I just remembered: 81 isn't available below LP, right? I'll fix that in the next release.
EDIT: Compatibility down to 52 added in v1.4.0
Compatibility down to 52 is very good, thanks.
The problem is in the image below
Only version 1.1 works for me (n910f note 4 running marshmallow 6.0.1)
The bug of not having Xposed installed continues, but the app continues to intercept the crashes normally
MarioUnoDueTre said:
The problem is in the image below
Click to expand...
Click to collapse
KaMyKaSii said:
The bug of not having Xposed installed continues, but the app continues to intercept the crashes normally
Click to expand...
Click to collapse
That's really weird, it hould be working. I completely disabled the warning and will have a look again when Xposed for N is available.
MrWasdennnoch said:
That's really weird, it hould be working. I completely disabled the warning and will have a look again when Xposed for N is available.
Click to expand...
Click to collapse
I reported with version 1.3.2, although you talk about version 1.4.0, it was not available when I opened the Xposed Installer. I will update now
Edit: The new version is not working, no crash is being logged
KaMyKaSii said:
I reported with version 1.3.2, although you talk about version 1.4.0, it was not available when I opened the Xposed Installer. I will update now
Edit: The new version is not working, no crash is being logged
Click to expand...
Click to collapse
1.4.2 should fix it... Really bad that I can't test it myself, it could've avoided many issues. But hey, at least I now know how to configure ProGuard properly. At least I hope so.
MrWasdennnoch said:
1.4.2 should fix it... Really bad that I can't test it myself, it could've avoided many issues. But hey, at least I now know how to configure ProGuard properly. At least I hope so.
Click to expand...
Click to collapse
Thanks, now it's working. Can you explain to me how the grouping that you implemented works? When I suggested, I wanted to say that after clicking on the crash group of the app, a list of all the crashs with information like date and time appears, and that they expand in the full log when they are clicked. And about the deletion, I'm talking about a button to clear any individual log after a long click on it. At this time it is only possible to clear all logs at once
Yes!
1.4.2 is working; good job, thanks a lot.
hello,
been having this weird bug/problem with com.miui.security center with every miui 9 release for poco(miui 10/pie security app runs fine but i didnt like miui10!)
the strange thing is that xiaomi is sending updates to all its apps on miui 9 exept security center!!(am talking about the app update not about the antivirus defs update etc).
the question is : can i remove the security app?and how?( am on miui 9.6.14 global stable ....rooted).
Install Titanuim Backup and uninstall from there.
P.S you can run into problems and force close issues along with other unbearable ****. so backup Security App on Titanium Backup and then uninstall it
Don't even think of uninstalling the Security app. I tried it twice and ended up in bootloop. I spoke to a miui dev and he said Security app is an essential part of miui rom and messing with it means messing with the ROM.
Right
Same here
com.miui.securitycenter
Need a mod for this can someone help.
How do i mod this so that all undesirable tracking & spyware components can be removed. It is obvious that this of a tracker agent making it unsafe for the user only makes it safer for XIamoi & its partners.
So I opened up the the app components-
Broadcast receivers activities services etc. And here is what I found .....
In something that supposedly claims to be a for security component for the phone
- Dunno if they will let me stick in a screenshot here . There are adware and spyware components down to the core.
Code:
AdsProcessPriorityService
com.facebook.ads.internal.ipc.AdsProcess
PriorityService
AdsMessengerService
com.facebook.ads.internal.ipc.AdsMessen
gerService
That is to name a few
- any attempt to disable this component is futile because even if you run pm disable the component is force enabled
- the other singers if I am rooted and I am ' magiskcally ' I hide magisk from all these redmi components. ..... even Here it forces need to unhide magisk could you see the extent of spyware organisation down to the core
I would like to continue this thread with an invitation to vah word wants to give me an approach and work with me so that a magisk module that will grab his component from the current phone and mod it -let the original spyware component load during boot time and post boot do a swap with the mod
Is it possible to do this kind of modification & unspy MIUI
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Vipxpert said:
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Click to expand...
Click to collapse
i can confirm this , i on miui 13.0.11 , redmi note 10(mojito) . uninstalled com.miui.securitycenter , rebooted . no bootloop. i will let other know if i encounter some bug later
Edit1: cant open battery setting, manage apps show nothing
Vipxpert said:
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Click to expand...
Click to collapse
can i delete miui cleaner ?
Apih95 said:
can i delete miui cleaner ?
Click to expand...
Click to collapse
Well.... Isnt that intergrated into Security Center app as well lol
ron_hyatt said:
hello,
been having this weird bug/problem with com.miui.security center with every miui 9 release for poco(miui 10/pie security app runs fine but i didnt like miui10!)
the strange thing is that xiaomi is sending updates to all its apps on miui 9 exept security center!!(am talking about the app update not about the antivirus defs update etc).
the question is : can i remove the security app?and how?( am on miui 9.6.14 global stable ....rooted).
Click to expand...
Click to collapse
Lucky patcher (slightly sketchy) and De-Bloater appear to work to remove apps on rooted devices
Obviously
Code:
adb shell pm uninstall --user 0 com.miui.securitycenter
will not remove it but if all you need is it to be disabled you can try that
Hello, this probably won't be seen, but to the very few travelers who discover this message on google or something:
As of January 19th 2023, the "Security Center" application on MIUI 13 is extremely sketchy.
I'm planning on trying to decompile it if possible.
Currently (According to the AOSP part of the settings) The app has permissions that are very worrying. Downloading files without permission, proprietary MIUI perms, full network access, etc.
Not only that, the built-in package manager utility (PM), refuses to disable com.miui.securitycenter due to being unable to "disable core miui packages..." and spitting out an exception dump.
This is clearly a protected app, that has too many permissions, for no apparent reasson.
Setting SELinux to permissive dosen't help either.
There are 2 options that people have currently - Either leaving a piece of a PUP (Potentially unwanted program) on their phone, or risking bricking it by uninstalling it.
According to the posts on this thread some people have had success, some got a soft-brick.
Doing so shouldn't result in a hard brick, so if you have backups, a userdata format should solve the issue.
TheMagnificent_Y said:
Hello, this probably won't be seen, but to the very few travelers who discover this message on google or something:
As of January 19th 2023, the "Security Center" application on MIUI 13 is extremely sketchy.
I'm planning on trying to decompile it if possible.
Currently (According to the AOSP part of the settings) The app has permissions that are very worrying. Downloading files without permission, proprietary MIUI perms, full network access, etc.
Not only that, the built-in package manager utility (PM), refuses to disable com.miui.securitycenter due to being unable to "disable core miui packages..." and spitting out an exception dump.
This is clearly a protected app, that has too many permissions, for no apparent reasson.
Setting SELinux to permissive dosen't help either.
There are 2 options that people have currently - Either leaving a piece of a PUP (Potentially unwanted program) on their phone, or risking bricking it by uninstalling it.
According to the posts on this thread some people have had success, some got a soft-brick.
Doing so shouldn't result in a hard brick, so if you have backups, a userdata format should solve the issue.
Click to expand...
Click to collapse
i recommend lineageos rom instead of miui but make backups
Hi I'm struggling with the same problem trying to stop de SecCenter. Maybe there is a way to stop the app to run. I tried on my Note 10 Pro with MIUI12.0.6 Global (Android 11) and it works.
You need root on the phone. You should change the owner of the folder "/data/user/0/com.miui.securitycenter" to a user the is not System. In my case a run the command "chown -R root:root /data/user/0/com.miui.securitycenter". After that you need to kill the process of the "com.miui.securitycenter". So at the end the process doesn't start anymore. In the next boot you need do the process again because the boot change the permission of the folder to the system again.
I'm trying to create a Magisk Module to do that but i don't know how until now.