Has anybody tried installing the Xposed module? There's a few modules I would like to use, like Greenify, but was wondering if it is safe to install.
What is the advantage to greenify on a non-battery operated device? If you're worried about power consumption, just limit the # of background processes via the developer menu.
There's apps running in the background that I rarely use, so I don't want them running all the time. I also use youtube adaway to get rid of the ads, App Settings to set the DPI of certain apps.
Related
I'm looking for an app that helps kinda show off the S-pen for the Note 3 whether it's games or features. I also am looking for an app that helps stop all services or apps that aren't necessary to run the device when I turn the screen off. Something just to save battery ya know?
buckeyestilidie said:
I'm looking for an app that helps kinda show off the S-pen for the Note 3 whether it's games or features. I also am looking for an app that helps stop all services or apps that aren't necessary to run the device when I turn the screen off. Something just to save battery ya know?
Click to expand...
Click to collapse
All the apps that feature the S Pen come preinstalled, I haven't found any games that will show it off or really benefit from its use however that doesn't mean there isn't one. There are similar non-Samsung note taking apps that have handwriting mode which allows you to use the S Pen but nothing really special other than MindBoard.
As for battery Greenify is a great app management app. With root and Xposed framework you can greenify system apps. Basically this is a hibernating app that allows you to hibernate apps at command or automatically with various settings based on your needs. The free version doesn't require root or Xposed, and the paid version is only a dollar or two. I would recommend this over a task manager/killer because it works around Android's behavior of restarting apps that get force closed.
Hey guys,
Today I installed Lollipop 5.0.2 in my XT1068 and so far I'm really happy with it.
I'm testing the Battery Saver mode, one of the features of Lollipop that I was really intriged for. When it's on it seems to stop all background data from Whatsapp, an app that's more important than SMS for me. You don't receive any data while the phone screen is off, and you have to go specifically to the app to receive a message.
The problem here is that I don't see the option to add this app to any "whitelist" of background data and receive messages even when sleeping, as usual.
Is there any way to set that up? It's hard to believe Google would let that feature out, so I'm asking here first because I don't see any info in the Internet about this.
Thanks!
Currently you cannot whitelist apps on the Stock Lollipop Battey Saver mode. Hope Google comes out with that feature in the next L release.
Meanwhile you can download Greenify app from Playstore. It works similarly, you select the apps which you want to hibernate and then click hibernate. The apps which are running in the background will get force closed thereby reducing CPU and RAM consumption. It saves battery tremendously. If you are rooted then Greenify will auto-hibernate the apps after your screen turns off.
Hope this helped
Yes, I have Greenify Donation Package, but as of now Greenify support in Lollipop is not at 100%, because the lack of Xposed in this version. Without Xposed Framework you don't access all features I'd like to have.
I already seen some incomplete work from Google in Lollipop, like the not-so-polished notifications profiles, and RAM problems are not solved by any means.
Anyways thank you!
I'm running a rooted 6P with TWRP and a custom kernel. Just got a notification for an OTA. Obviously, I can't run this update. How can I disable the update check? I have ROM Manager and know how to disable apps, but don't see any obvious update check system app.
Sent from my Nexus 6P using Tapatalk
I use disable services for this purpose. Download this https://play.google.com/store/apps/details?id=cn.wq.disableservice
Open and click on the system tab, then Google's play services, then scroll down to bottom and un check system update service and then reboot phone. Just don't go around disabling other things unless you know what you're doing .
Won't this create the dreaded systemupdate wakelock?
EDIT:
The tool doesn't work at all. It may be due to the fact that Amplify is installed and is blocking due to having similar functionality. I tried disabling it in amplify instead and it does remove the notification but adds a wakelock that keeps the phone awake from systemupdate. The only way of getting rid of it right now that I know if is:
A) Hold notification and choose block all notifications from google play framework but this will also block other potentially useful and relevant notifications coming from there. All notifications regarding your watch probably, plus update notifications for the framework when it's outdated etc. Disabling it all is probably not a good idea at all.
B) Using Notifyclean xposed module. Feels like an overkill for this one job but it works I guess.
NOT working methods:
A) Disabling the service: leaves a wakelock that keeps your device awake. Some says it's not "active" but showing up in bbs but that's not right, I've noted the count from screen off to screen on again and it does indeed increase when screen is off. Tried in Amplify, service disable won't work for me when Amplify is installed anyway.
B) Disabling 3 service receivers. First of all autostarts won't work on 6.0, rom toolbox lite says it works although won't show the entries unticked after reboot. It seems to work in the sense that the notification is removed. Same result here though: wakelock.
C) Combining A and B: same result.
Untried methods:
Combining A with also disabling the wakelock in Amplify.
Let me know if anyone has better/other ideas. I went for solution number B. I worry that notifyclean might cause some other issue but I'm trying it out for now. Only thing I've noticed so far is a notification synced by mighttext that is empty from notifyclean which I blocked.
hello.
i have so many apps installed and i don't use lots of them much So i force close them.i used to use hold back button to force close on other roms.but on oos there isn't this option.
now i am searching for an app that can force close a list of apps at once when i tap.
is there any app like this or am wasting time searching ?
my phone is rooted ( with supersu ).on open beta 6 and franco kernel.
thank you.:fingers-crossed:
Use Greenify App
vip57 said:
Use Greenify App
Click to expand...
Click to collapse
it doesn't conflict with nougat doze mode or make any problems ? i have root.
i have to forbid access root to greenify ?
Rhodesgod said:
it doesn't conflict with nougat doze mode or make any problems ? i have root.
i have to forbid access root to greenify ?
Click to expand...
Click to collapse
No greenify doesn't conflict with it the opposite it is made to be comptabile with doze mode
You have to grant access to greenify to use it properly
And greenify the apps that you see that they must not work in background
Will greenify conflict with nap time?
sakumaxp said:
Will greenify conflict with nap time?
Click to expand...
Click to collapse
I think You can use both but the 2 apps have options for aggressive doze you can't enable it in the two apps
You can configure aggressive doze with naptime
And hibernate apps with greenify
Why would you want to do this in the first place? OOS handles it just fine by itself. No need to constantly force close apps...
You have 6GB of ram, force closing apps will only cause the OS to cache all the apps again eating CPU and I/o resources. If you really need more juice I know greenify has a "shallow hibernation" mode that keeps apps in memory but stops apps background activity. I have never needed these apps with this phone as android is getting better with background tasks.
i used greenify,
set on " No root " and it force close list of apps just with one click.
thank you.
Alternatively, you can go to Settings>Advanced>Recent App Management and select "Deep Clear". It may seem like a bit much at first due to its very aggressive behavior but once you get the hang of it, it just might become your native app killer and best friend !
And if you really look into it or if you use it complementarily with others apps (SDMaid, NapTime, ...) You can manage to work around its (sometimes) annoying effects (like forcing to relaunch an app after a Deep Clear) or even make it event more efficient by preventing the killed app to launch again (bootflags and broadcast receivers for instance)!
I believe that apps should complete or expand your OS, but (almost) never substitute for your OS
A little bit of a shot in the dark here, but here goes...
In Lineage OS, there is an advanced permissions function in settings that allows one to set more detailed permissions for each app. It's organized in columns by Location, Media, and other categories, including Run In Background, and Run on Boot.
It's the Run on Boot I'm most interested in as a lot of times apps install and run on boot in the background and don't need to be.
I don't think this functionality is in OOS, or if it is, I can't find it. I also can't find an app, Xposed Module, or Magisk module for this.
I used to use XPrivacy but that's been abandoned?
Does anyone know of an app or module that would work for this level of permissions?
App Ops
Try App Ops, works great and is so much more userfriendly than Xprivacy. There is a Magisk Module for running process, but the app you'll find in play store.
I don't see any point. Boot time is already fast in oxygen os. & About the background apps after boot, they get killed if battery optimisation is on.
exis_tenz said:
Try App Ops, works great and is so much more userfriendly than Xprivacy. There is a Magisk Module for running process, but the app you'll find in play store.
Click to expand...
Click to collapse
Thanks - this app is helpful for a lot of reasons.
I don't see an at-boot setting though.
ASB41 said:
I don't see any point. Boot time is already fast in oxygen os. & About the background apps after boot, they get killed if battery optimisation is on.
Click to expand...
Click to collapse
Not boot-time related. Many apps load at boot and don't need to. They stay in memory, trigger wakelocks, and snooping areas in the background that shouldn't happen. They also re-start themselves after killing them because the OS thinks they should be running all the time. Youtube is one example. I have a photos app that does it. Several travel apps. Killing apps from loading at boot solves all of those problems, and when you kill them, they don't restart.