Database Info

[IDEA] Know when you can start using your phone after booting

Hi all,
I have an apps idea but I am not a developer and thus will really love if a developer will try to do it for the communities.
It's to check when is your phone ready to be use after a reboot.
Often the time, I must look at my widget continuously to know if the phone has gotten stable to use after a reboot or not. So, I guess this would be a nice addition.
The idea is that the apps should start very early in the boot up process and monitors the CPU usage continuously.
If the CPU usage is less than 10% (or any other value) for 10 seconds (or longer), then the apps will prompt the user, either by a toaster, or via notification, or via sound/vibrate etc.
After the user learns that, the apps will shut down itself and no longer takes up any memory or juice.
What do you all think?

I had the same idea, and solved it with this tiny and handy application : CPU Notify
https://market.android.com/details?id=com.beemer.cpunotify&feature=search_result
It is loaded at boot time, and you can observe that the CPU is at 100%. When it goes down to botton (green) steadily, the phone is ready.
I keep this application constantly since it is very small and battery friendly. It shows your phone activity like task manager in tray icon in Windows world.

TaskPanel, Autostarts, and when to use a task killer

Please dont 'quote' this as it VERY lengthy, just copy and paste the this first sentence.
I wanted to write up a definitive posting on task killers as I think they are way to often misused and misunderstood and I am getting quite tired of reposting this same information.
I use a task killer called TaskPanel XTRA (its free). BUT, I ONLY use it for killing tasks that are misbehaving (an app that has slowed down or nearly hung your phone or an app that is CLEARLY causing battery drain or sending copious data via your cellular connection). If an app continues to misbehave, switch to a different app that offers the same functionality, do NOT continue to use a task manager / task killer to kill an app continuously.
Task killers should NEVER be configured to automatically kill an app (as I will explain later in the post) and should NEVER be used to manually kill apps UNLESS it is a small emergency (as in major battery drain, copious cellular data, massive processor usage/memory usage preventing the user from using the phone normally).
Android is a VERY powerful operating system which gives YOU THE USER the control to manage your phone (hence the major reason I dont like the IPhone or Windows Phone), but with that control comes responsibility. As I will explain shortly, Android has many built-in features in place to help you manage your phone's precious memory. While there has been much nonsense one way or the other as to whether task killers should be used for anything other than a misbehaving app, I tend to listen to the creators of a product before I listen to some jackass who bases a decision on pure speculation or a 'feeling' he has. I can tell you that I have not used Task Panel in the last 4 months (with the exception of I believe Pandora which I used about a month ago and could not find a way to actually exit the app - guess what...this app is no longer on my phone - both because of privacy concerns that recently came up about Pandora AND I dont keep apps around that I cant manually exit the app cleanly).
For a VERY good write up (with a brief 'readers digest' summary at the bottom with plain English bullet points, since most of the article is taken directly from the Android developer FAQ and is very techy for non-programmers), have a gander thru this.
http://geekfor.me/faq/you-shouldnt-b...-with-android/
And for the FAQ they quote most of the above article from (but I do recommend you read the above FIRST as it will give you some context - much of the reasons are 'cherry picked' from different areas of the FAQ to help you understand why this is important and give you the information that is relevant to the discussion as to why task killers are not a good thing). All of the relevant information is in the page that will load up (in the rightmost panel / frame) so you dont need to click any links to read the relevant article. I am only providing this link as a reference to the original source material so you dont think I am just making this up - this is straight from the horses mouth so to speak (again, for most people, dont read this FAQ, read the one above first to get context and then if you feel you want to know more, read this link below).
http://developer.android.com/guide/t...damentals.html
Alright, enough about task killers, now to deal with how to manage those pesky apps that seem to always be running (even if you never started them) and how to keep them from starting up using a method that will NOT affect Android and how it manages your memory but will keep your phone in peek performance.
For managing the conditions when an app starts up, use an app called Autostarts, do NOT use a task killer to 'auto kill' tasks. Autostarts literally allows you to control the conditions of when an app starts.
Android has built in functionality for managing the memory footprint of various apps and will manage your phones memory quite nicely. Much of the functionality of the built in memory management came in Android 2.2 (also sometimes referred to as Froyo) and is really quite good 'if' you allow the phone to manage processes rather than just quickly killing everything.
There is a reason you can no longer just 'kill' system level processes, Google wants you to allow Android to 'learn' how to manage itself.
Android has a very powerful feature, the ability for app writers to start their app when certain conditions occur. The problem with this powerful feature is, often times, apps are bloated or poorly written, many times being started for any little thing your phone does (wifi on or off, Bluetooth on or off, location changes, screen on or off, USB connected, cellular connection, headphones connected, a cow fart, a bird poops, etc.). Even Google itself has been guilty of this, Google Maps (until recently) would be started in nearly 20 different conditions as a background process for very trivial things and was a major source of battery drain (it still is to some extent). This is where Autostarts comes in. Use Autostarts to control the conditions of when/if an app will start up automatically based on a certain condition.
Most ancillary apps (apps that are not integral to the core functioning of the phone - although it is probably more appropriate to refer to these as 'user apps', it isnt quite accurate because many 'system apps' (which in the technical description are apps that are installed with the rom) are not core apps either. For example, many roms come with Youtube pre-installed (meaning you do not manually have to go to the market and install them) which is not integral to the core functioning of the phone), these apps do NOT need to ever start under ANY condition for that app to function normally. The only considerations for an app starting itself would be the widget updating, the app has a scheduled event (for example, an alarm, a podcast client downloading podcasts at a certain time of day, Titanium backup performing a scheduled backup, etc.), or an app that has to be running in the background to perform a task when certain conditions arrive (for example, an app called Sanity needs to be available to run and monitor for incoming/outgoing phone calls so that it can start itself and perform its function during a phone call).
Using Autostarts, I have disabled nearly 80% of EVERY condition that all NON-system apps start under (I havent counted but for 70 apps, this is probably 55 apps or so that I disabled EVERYTHING these apps would start under). This includes Google Maps (yep, even Google is guilty of having an app needlessly running when it doesnt need to).
By taking control of your apps (in essence, disabling as many apps from 'auto starting' until YOU the user launch the app manually) and properly quitting an app when you can (within the app, find a way to click a 'quit' or 'exit' button to allow the app to remove itself from memory) rather than just allowing apps you launch to run in the background, you can save yourself massive amounts of battery life, limit cellular data usage, AND allow Android to properly manage itself.
Think of it like this, if I were trying to learn something but you (the user) kept doing it for me, Id never learn. And if you read the above linked article, you will begin to understand why there is more to this than just allowing Android to learn.
To give you an idea, using Autostarts to disable any non-system app that does not need to be running, if I am using the stock battery, I can run my phone for 2 days pretty easily if I simply turn off cellular data, Wifi and Bluetooth when I dont need it, maybe even stretch it to 3 days.
My ram usage is almost always around 50% (150 MB free) on a fresh reboot (around 2 minutes to allow the phone to stabilize) and it remains this way during the day because I exit apps when I am done using them, even tho I have around 80 apps installed, and I dont allow apps to just start themselves because they sensed a fart in my general direction.
For those of you that use a Windows PC, you can think of Autostarts as a proper 'msconfig'. Keeping your PC clean of apps when windows starts keeps your PC running much more smoothly. Autostarts takes this to the next level and keeps apps from ever starting in the first place rather than a task killer 'auto killing' a task, the app restarting, the app getting 'auto killed' again by the task killer, the app again restarting, etc. (a vicious cycle that both kills your battery because the phone has to crank up the cycles on the processor to both start and stop the app, the power used to write and clear the data written to both ram and 'perma' storage (if an app needs to store any data), and cellular data (if an app 'phones home' so to speak when it initially launches (which is both a cause for additional battery usage to send data and also adds to the amount of data your phone transmits over the cellular network, which is a problem given most cell plans have a monthly data cap).
Autostarts is fairly easy to use but does require root.
The app is $2 and here is a brief synopsis of how to use it:
When you initially launch the app, read any dialog messages that appear and click ok thru them. Then, wait for the app to finish loading (there is a progress bar at the top that will fill with yellow - on my phone it takes about 45 seconds to a minute to finish loading in).
Once it is loaded, you need to configure a few things BUT, you might want to just scroll thru the list of things currently on the screen. These are the 150+ conditions that apps currently installed on your phone are starting up under (dont click anything just yet, just browse the list if you are curious).
Right now, the app is configured to show a list categorized by conditions. This unfortunately is not very helpful. We need to change it to sort this list by apps rather than by conditions (so that we can literally disable EVERYTHING an app will automatically start under rather than scrolling thru every condition).
So, hit your menu button and the top left most icon in the menu that appears is an icon 'Group by application'. Hit that icon and magically, you are now seeing every app. You can now click an app and see all the conditions every app starts under. Neat.
But there is one more setting to change first in order to help keep you from doing something you should not.
(Optional but HIGHLY recommended!) Hit your menu button again (if you exited out of the menu already) and hit the upper right most icon, the 'View' button. Tick the topmost checkbox, 'Hide system apps' and hit the 'Ok' button. This will keep you from disabling anything that 'may' be critical to your phone operating.
Now, exit the menu (the 'back' button on the phone itself).
If you decided not to hide system apps, these will appear in YELLOW. It is probably not a good idea to mess with these unless you know what you are doing. Messing with these can cause a soft brick or make your phone unusable in certain conditions (for example, if you prevent the phone.apk app from ever starting, you will never be able to take phone calls).
Now, start scrolling thru the list (start at the top). If it is an app that does NOT need to run in the background, expand the app by selecting it and starting with the topmost condition that app starts under, tap each condition and in the menu that appears, select 'Disable'. Do this for ALL conditions for each app you want to manage. When you are done disabling the conditions, go to the next app and decide again whether that app needs to run in the background or not.
As a brief summary, to consider whether an app should be allowed to run in the background, ask yourself the following:
Does the app:
a. ...have a widget that you are actually using on your home screen that needs to update? For example, a media player or weather widget should NOT be disabled...
b. ...have a scheduled event such as checking the weather, downloading new podcasts, checking email, etc?
c. ...need to perform a certain task or provide some extra function(s) when a specific event happens (such as recording a phone call when it comes in, an eq when audio is playing, etc.)?
My recommendation is, if you answered YES to any of the above questions, leave all the conditions that app starts under alone (unless you know what you are doing, its best not to mess with it as I will explain in a moment).
If you answered NO to all the above, DISABLE ALL of the conditions that app starts under (again, DONT mess with system (yellow) apps and certainly dont disable every condition for these).
I recommend an all or nothing approach for each app is because if an app doesnt behave properly, it can become a major pain to continue to open Autostarts and try to track down a specific condition you disabled that is stopping / preventing that app from functioning the way you want it to.
Every time you update or install an app, if you remember, try to open autostarts and review the conditions the app starts under. Updated apps often times will add something new and if you have this app completely disabled, it may find a way to start itself again.
And, dont worry, you cant permanently screw anything up (unless you are messing with system apps - get the reason why I recommend not playing with system apps?). If an app stops functioning correctly, just re-enable the conditions that app starts under. Pretty easy.
Hopefully, this is complete enough, I will now just link to this post everytime I need to mention autostarts. I am getting quite tired of posting this same information .

Good information for people. Well done.
Sent from me to you using stuff

[App] Floating battery temperature and % monitor (for use while on GPS)

Note - this App requires root (to allow floating a display on top of another application)
Why do you need it:
When you’re using GPS for navigation, battery % can drop rapidly if not charging. Battery temperature can increase rapidly if you are charging.
This App will allow you to monitor those without leaving your GPS or navigation (or any other) application
What does it look like:
(see screenshot)
This app places a small transparent indicator block “floating” on top of all other applications.
The indicator includes the following (see screenshot)
Battery % remaining (was 50% in the screenshot)
Battery Temperature in degrees F (was 95F in screen shot).
Time of last update (was 20.34 = 8:34pm in screen shot).
Updating and closing:
The values are automatically updated every 2 minutes (%, temperature, and update time)
If you get impatient, tap the top number (% remaining), and you will force an update.
To close the application and remove the floating display, click on the red X on lower right-hand corner of the indicator block.
Tips:
Open this App (floating battery temp/% monitor) before you open your GPS / navigation application, so you don't have to leave GPS/Nav and come back to it.
Possible Future Enhancements:
Allow the location of the scene to be moved.
Allow customization of the info displayed on the floating bar.
Audible alarms for high-temperature or low % remaining based on user-programmable setpoints
How was it created:
Using Tasker and App Factory by Crafty Apps
http://tasker.dinglisch.net/
http://tasker.dinglisch.net/userguide/en/appcreation.html
Personal:
I am not a programmer, but Tasker and App factory make it easy.
This is my first "App" that I have shared.
I found it useful. Hope you will to. But interested in any comments...
Feedback sought:
Is it a helpful app?
Are there other apps that already do the same thing?
Any problems or unexpected behavior using this app?
Any suggestions for improvement?
Thanks
Changelog:
9/16/12 - Post Rev 0 (BattFloatScrR0.2.apk)

Memory Impact
I have noticed that this App is not particularly memory-friendly. Specifically:
1 - It auto-loads whenever you boot your phone
2 - It has an associated "service". (Services are generally higher priority than Apps and not readily unloaded from memory,once loaded)
3 - The combined size of App and service is 8MB
I'm not sure whether this is the default behavior for Apps generated using Tasker App Factory, or whether it is instead a result of some input that I provided to App Factory. I will that investigate that further and report back.
In the mean time, for anyone concerned about memory usage for this app, I would suggest to use Gemini Apps manager (*) to disable all auto-run features for this App. Also, once you have manually launched and later closed the the Floating Battery Monitor App, if you want to gain back the 8MB memory without rebooting you'd have to go into Settings/Applications and kill the service/application.
* Gemini Apps manager is a great free App to accomplish blocking apps/services that auto-run at boot and at other times. I also use it to prevent Google Maps from auto-loading on boot (in the case of Google maps, blocking autostart saves not only memory, but also battery due to partial wakelocks from google maps application when loaded). Preventing an App from auto-loading at boot doesn't interfere with operation of the program at all (it may take a fraction of a second longer to load the first time you manually launch the program after boot, but it's well worth it to avoid loading unneeded programs/services at boot imo).

[APP][2.x-5.x] [APK] BATTERY SAVER ULTIMATE

Overview
Battery Saver Ultimate application provides the best power settings to saves the battery time of your device or your tablet. Whenever the battery runs low or goes too much down, just tap the power saver app to turn on the saving mode.
Battery savers help you to switch off all the extra functions like WiFi, Bluetooth, GPS, sound and other energy consuming apps on the device. The app will notify when the power gets down in percentage and it even shows the charging stages.
Charging Stages:
Free Battery Saver Ultimate app regulates the manner in which your device is charged with a Unique 3 Stage Charging system to ensure you get the most out of your battery and reminds you not to over charge.
Types of Mode :
1. Saving Mode: (Use in lowest Battery Status)
Device Brightness set to 10%
In Activate WiFi of the Device
Stand By time to 15 seconds
2. Sleep Mode: (Use when you sleep)
Turn Off Call & SMS and turn ON the Flight Mode
Set Vibrations Off.
Airplane Mode.
Sound Off and mute media sound too.
Brightness set to 10% or minimum level.
3. Customized Mode
You can Customize app usages as your need to save Battery Power.
Can adjust the battery saving setting freely depend on your need and usage.
Can adjust WiFi, Bluetooth, vibration, sound, device brightness, synchronization and stand by time.
Features and Requirements
Accurate battery remaining time
Shows Standby Time.
Accurate charging remaining time
Schedule power saving modes for work/class/sleep and more!
3 Stage Charging system 1. Fast charge 2. Continuous Charging 3. Tickle Charging.
Wifi/Data/Bluetooth/GPS/Flight Mode toggle!
Brightness control!
Shows Battery Health, Current Battery Power in mAH, Temperature, Voltage and Battery life status.

Interesting app. I installed it on my tablet. Look up how it will work. Pity that application is not in material design...

Can I say dodgy app here full of ads and nothing as you say it is. Gives me to play games and full of ads. Avoid

Looks very Good though

Full of ads, nothing like advertised. Avoid.

mr_stax123 said:
Looks very Good though
Click to expand...
Click to collapse
Please state more

i want to prevent apps to auto start to save battery and ram, which app should i use, grrenify or autorun manager or any other?

First, you need not concern yourself with free ram on an Android device. Android manages resources better by itself. As for the apps that launch on startup, you can got to menu>settings>apps and select the "running" tab to show you exactly what is really running. Then, the easiest way is to uninstall the app in question.
Automated task killers do nothing but cause more problems than they can potentially solve.
You might find this thread enlightening.

mr_stax123 said:
i want to prevent apps to auto start to save battery and ram, which app should i use, grrenify or autorun manager or any other?
Click to expand...
Click to collapse
The task killer discussion gets old. I think there is risk of oversimplifying both sides. ie on one side people want to treat it like pc...not correct. On the other side people seem to imply any discussion of memory management considerations is irrelevant/rejected because "android will handle it all"....which is not always entirely correct either. The latter may be closer to the truth especially for new devices, but there is still room for middle ground. Not all programs are equal, some launch "services" which takes priority over other app processes. Too many of those services can eventually crowd out cache and slow your phone down. Maybe most people with newer phones will never get there, but there are still people with older phones (including the op for all we know) and also some folks with new phones who (if they listen to the oversimplifications) may get carried away on the number and type of apps they install over the life of their phone
---------- Post added at 12:47 AM ---------- Previous post was at 12:43 AM ----------
Even so, killing off those services is not the answer. If an older phone has too many running services so it taxes it's resources then it's either time to uninstall some or get a device that can handle it. If it's a problem with the app itself hogging resources, then let the developer know and find an alternative.
If you try to tow a boat with a bicycle, the answer isn't to throw away the boat's engine to make it lighter. Similarly, a task killer may make the phone's performance improve briefly, but over time it will make things worse. And it fixes nothing.

An app preventing another app from "auto-starting" is a task killer. Look at it this way: The phone boots up and runs it's processes. The auto-start blocker detects an app it doesn't want to run, so it kills it. Now, depending on what app it is, the phone may call for it again and thus running it later, which defeats the purpose of an auto-start killer, unless that app is a task killer which again kills said flagged app to keep it killed.
The way to properly manage an app you don't want to have enabled on the phone at bootup is to disable the app on the system manager (newer phones have it AFAIK), freeze the app via Titanium or similar apps, get into the app settings and disable certain features like auto-sync and set everything to manual.
However, the OP did not specify what phone and which apps. It may be apps which the phone requires to run at some level, like Maps (which several apps call for), or maybe the apps he is seeing are just RAM cached, which really don't matter at all.

Adjusting with app settings is preferred if you can, but does not always solve the problem (I referred to wakelock/battery drain problem with a certain version of Maps on my previous phone ... many people we having the same problem at the time and the only way to stop it was to block the app from starting as indicated in link below, or else to freeze it). Freezing has the disadvantage that you cannot run the program easily (requires you to launch TiBu to thaw the program). If you have blocked the program from autostarting, then it does not start at boot or other automatic time, but it remains available to manually launch the normal way (clicking the program icon). At that point (if it's a program like Maps), it will probably stay running until next reboot. It was my preferred solution when maps was giving me wakelocks and battery drain on my phone. Maps didn't run automatically on boot and never started until I manually started it. After that point I could live with the battery drain or reboot

Rom Toolbox Pro is a great app with many features and of course, there's an auto start manager that allows you to disable various receivers off the apps that start on boot. There's also a freeze/deep freeze feature as well. Great app

Explanation of Nougat Battery Consumption and Workarounds for Better Battery Life

Hello guys. This topic is pretty long and it is hard to read all of it but try to read all of it till end.
Well, let me begin. The main problem of the nougat update is the dramatic increase of battery consumption (for me at least) But why this is happening?
Actually this is a matter of battery managers. Huawei had created a great phone but obviously they messed things up in the software side. Google announced "Doze" feature with Marshmallow. If we could have a brief explanation of "what doze is" is it is basically a battery protection policy created by google. In Android, apps have the ability to use what’s called a “wakelock” to prevent your phone from going into a power-saving deep sleep mode. This deep sleep mode usually kicks in when your phone’s screen is off, but that can get in the way of how some apps work. For example, if you’re using a fitness tracker, you don’t want your phone turning off GPS or your accelerometer just because your phone is in your pocket with the screen turned off.
In principle, this is a good concept. Apps keep your phone awake and working when they need to, and let it sleep when they don’t. This is a problem, though, when every developer thinks their app is important enough to keep your phone on all the time. That’s why apps like Facebook kill your battery, even when you’re not using them.
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device). Here is a graphical explanation of how doze works versus time:
http://itresan.com/wp-content/uploads/2016/05/doze-header.jpg
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device)
If we turn back to the main topic, as I mentioned before, Huawei has some difficulties combining it's own features with google's. Huawei has its own battery manager. That's why you are not receiving some notifications from facebook or whatsapp. That is because that freaking battery manager shuts everything off but still, since it has a very poor approach, the system drains battery. It is basically a matter of doze does not kicking in. As you can see, the battery usage when the screen is turned on is about the same. However, the same thing cannot be seem when the screen is off.
So what to do in order to save some juice?
-There is some workarounds for doze kicking in like these ones:
https://play.google.com/store/apps/details?id=com.yirgalab.dzzz
https://play.google.com/store/apps/details?id=com.suyashsrijan.forcedoze
These two apps have different approaches. I prefer ForceDoze as it seems the google's intended way.
I want to highlight this item because this might be the most important thing in this topic. If you don’t do anything with your phone, Doze will still do its job. It runs almost invisibly in the background. Occasionally you’ll get a few messages at once, rather than spread over a few minutes, but for the most part there’s no noticeable change. In other words this is a bit different from the conventional full deep sleep and you do not have to afraid from doze as you do with the full deep sleep.
-DO NOT CLEAN YOUR RAM TOO OFTEN. This will cause closed apps re-open and hence, more cpu usage.
-No! Cleaners, Task managers and other stuff does not work! As I mention before, they even lead more battery consumptions.
-Huawei has poor google service implementations. Even one or two implementation has some bugs that causing battery drain(for example: google backup). Try to turn them off.
-Know when to reboot your phone. Too frequent reboots may do the same thing as you cleaning your ram. However, rebooting cleans app caches so the system will work smoother. Once a week or two weeks is fine I suppose.
Please hit the "Thanks" button if you like and please point out the missing things and if you see a mistake please warn me for correcting it. I hope you liked the topic.
Have a nice day!

Doze is problem for me. I don't have push notification by the night.

darrr1 said:
Doze is problem for me. I don't have push notification by the night.
Click to expand...
Click to collapse
It's probably not because of the doze but the huawei's power manager itself.

Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem

darrr1 said:
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
Click to expand...
Click to collapse
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.

I did everything what I can without succes.

furkey said:
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
Click to expand...
Click to collapse
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?

xtcislove said:
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
Click to expand...
Click to collapse
Doze is not on kernel level but it is on software level. Programmatically we can activate what is left from doze or at least simulate it. However, if there is a certain need for doze we should cook a whole new rom and yes, it requires open source too.
But, let's clear a thing here: Huawei did not completely removed doze. Actually, I think they can't do that if they wish to use Android. Just some settings of Huawei conflicts with doze and prevent its functioning.

I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.

antimatter.web said:
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
Click to expand...
Click to collapse
Could you finally solve this?
I also have and Honor 9, and have the same problem with aplicacition radardroid. Is getting killed, and also have all configured to prevent this...

Try by having both in the Settings
-Battery/Close apps after lock screen (uncheck in the list)
-Apps/Settings gear/Special access/Ignore battery optimization (make it allowed)

Thank szgfg,
Both are already well configured, but still closing the app.

mikicl said:
Thank szgfg,
Both are already well configured, but still closing the app.
Click to expand...
Click to collapse
Check also is not being closed by the automatic cleanup (so add it to clean whitelisted apps) and that is not being closed due to high consumption...disable that on battery settings... Let the advertisement but do not let phone administrator close that apps automatically
Enviado desde mi EVA-L09 mediante Tapatalk

Hi jcalderonv74,
Thanks for your answer. I didn't know about the clean whitelisted apps, was a surprise to find it. But unfortunetly, everything was well configured.
Option to avoid being closed due to high consumption was already OK.
So nothing to change, everything was as it has to be. Seems more a software problem in EMUI 5.0

After some days without touching anything in the phone's configuration, finally observed that everything is working fine. All aplications configured keep opened, and it's only Radardroid aplication that sometimes closes alone (only sporadically after a recent update)
Seems more an error in Radardroid aplication that in telephone's software. So I'm not worring more about that.