Related
Hello!
On my DHD I got some Apps that keeps running in the background:
Settings -> Applications -> Running Services:
- Music: DownloadManager$ & JumperService (from Honeycomb Music Player)
and in Advanced Task Killer:
- Stocks & Music
My question: Is there a way to stop the above apps (but also any other app) from starting automatically in the background and keep them closed?
From what I understand and forgive me if you are already aware of this but what your speaking about are actually services and not running programs/apps. Services are running to assist the app or program to open much faster than if not. They dont take nearly as much drain on the system as your may think and these phones were made to handle the multi tasking. I think we all get caught up in keeping our phones clean of nonsense and useless (at the time) running programs but in actuality they are there to help us. I suggest you uninstall ATK and give yourself some ease of mind and let the services run when they want lol....thats what I am starting to do.
So i saw many posts on which people have asked as to which task killer should be used !
and then i stumble upon this site which provided me the details,
i just complied info
sources-by Chris Hoffman
http://www.howtogeek.com/127388/htg-explains-why-you-shouldnt-use-a-task-killer-on-android/
Android Doesn’t Manage Processes Like Windows
Most Android users are familiar with Windows. On Windows, many programs running at one time – whether they’re windows on your desktop or applications in your system tray – can decrease your computer’s performance. Closing applications when you’re not using them can help speed up your Windows computer.
However, Android isn’t Windows and doesn’t manage processes like Windows does. Unlike on Windows, where there’s an obvious way to close applications, there’s no obvious way to “close” an Android application. This is by design and isn’t a problem. When you leave an Android app, going back to your home screen or switching to another app, the app stays “running” in the background. In most cases, the app will be paused in the background, taking up no CPU or network resources. Some apps will continue using CPU and network resources in the background, of course – for example, music players, file-downloading programs, or apps that sync in the background.
When you go back to an app you were recently using, Android “unpauses” that app and you resume where you left off. This is fast because the app is still stored in your RAM and ready to be used again.
Why Task Killers Are Bad
Proponents of task killers notice that Android is using a lot of RAM – in fact, Android stores a lot of apps in its memory, filling up the RAM! However, that isn’t a bad thing. Apps stored in your RAM can be quickly switched to without Android having to load them from its slower storage.
In summary, you shouldn’t use a task killer – if you have a misbehaving app wasting resources in the background, you should identify it and uninstall it. But don’t just remove apps from your phone or tablet’s RAM – that doesn’t help speed anything up.
Empty RAM is useless. Full RAM is RAM that is being put to good use for caching apps. If Android needs more memory, it will force-quit an app that you haven’t used in a while – this all happens automatically, without installing any task killers.
Task killers think they know better than Android. They run in the background, automatically quitting apps and removing them from Android’s memory. They may also allow you to force-quit apps on your own, but you shouldn’t have to do this.
Task killers aren’t just useless – they can reduce performance. If a task killer removes an app from your RAM and you open that app again, the app will be slower to load as Android is forced to load it from your device’s storage. This will also use more battery power than if you just left the app in your RAM in the first place. Some apps will automatically restart after the task killer quits them, using more CPU and battery resources.
Whether RAM is empty or full, it takes the same amount of battery power – decreasing the amount of apps stored in RAM won’t improve your battery power or offer more CPU cycles.
hope u understood!
words of wisdom by fellow-mates
go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
I've never used those programs, I like to use what the phones have by default
But is good to know anyways
I agree with that...to an extent
Auto killing apps is plain stupid, but I do believe in killing certain apps. In a perfect world heavy apps would just be uninstalled, but plenty of useful apps without good replacements are fairly heavy, and it helps to kill them. E.g. after exiting a game I will kill it because its hogging up valuable ram by running in the background, while still using he same resources it uses at the forefront.
I understand that android, and Linux should manage ram well, but more often then not some app is just out there slowing my phone down. Even an hour later of not using that app, it'll still be in the background using up a lot of CPU and ram I don't have (more importantly battery). Android is great at managing smaller apps, but in my experience, it sucks at doing the same for larger apps.
Sent from my Desire HD using xda app-developers app
I don't use automatic task killers, those that are constantly running, but i do kill unused tasks and apps with no reason to be still running. Google services is a common example. It will launch at boot and keep running peemanently, even if you never launch a google app, google services is running, why?
A lot of apps, mostly the free ones, get revenue by reporting anonymous usage statistics (not so anonymous in some cases). So they stick a running service even if the app is never launched again (sometimes even if it isn't launched in the first place).
To sum up, killing everything is bad, but leaving everything to run free can also decrease performance. This can be observed on an android device that has been running for a long time, versus an android device that's just been reset.
some unused tasks will repeatedly rerun even if killed.
This will further decrease battery life and affect performance as resources are needed to keep restarting it.
The best way is to ignore if it takes a small portion of resources or to uninstall the app. Rooted users may disable the triggers via certain apps.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
In phones with very low RAM, this becomes a necessity.
Switching programs take up a lot of time to process unless there is a sizable free RAM
Markuzy said:
some unused tasks will repeatedly rerun even if killed.
This will further decrease battery life and affect performance as resources are needed to keep restarting it.
The best way is to ignore if it takes a small portion of resources or to uninstall the app. Rooted users may disable the triggers via certain apps.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
use auto run manager
it is the answer to most of every body's problems
DarthSimian said:
In phones with very low RAM, this becomes a necessity.
Switching programs take up a lot of time to process unless there is a sizable free RAM
Click to expand...
Click to collapse
if u have low RAM, please manually remove the apps!
dxppxd said:
I don't use automatic task killers, those that are constantly running, but i do kill unused tasks and apps with no reason to be still running. Google services is a common example. It will launch at boot and keep running peemanently, even if you never launch a google app, google services is running, why?
A lot of apps, mostly the free ones, get revenue by reporting anonymous usage statistics (not so anonymous in some cases). So they stick a running service even if the app is never launched again (sometimes even if it isn't launched in the first place).
To sum up, killing everything is bad, but leaving everything to run free can also decrease performance. This can be observed on an android device that has been running for a long time, versus an android device that's just been reset.
Click to expand...
Click to collapse
use autorun manager, keep it simple
dxppxd said:
I don't use automatic task killers, those that are constantly running, but i do kill unused tasks and apps with no reason to be still running. Google services is a common example. It will launch at boot and keep running peemanently, even if you never launch a google app, google services is running, why?
A lot of apps, mostly the free ones, get revenue by reporting anonymous usage statistics (not so anonymous in some cases). So they stick a running service even if the app is never launched again (sometimes even if it isn't launched in the first place).
To sum up, killing everything is bad, but leaving everything to run free can also decrease performance. This can be observed on an android device that has been running for a long time, versus an android device that's just been reset.
Click to expand...
Click to collapse
let me tell you something about google services...
when you installed your rom, you had to check two options from google services - location and another one.
if you are on stock, those options are available in settings also.
the google services are needed (you are running a google os, right?) because without it, the location feature will not work, the play store will give you headaches and not to mention, google now that needs that service like water.
if you kill that process over and over again you will not gain anything because that service will keep restarting it until you will give up. ah, you will loose a massive amount of battery if you do so
another thing, the google service is a system app. system apps have priority in resources so even if you kill now, as i said, it will restart after a few seconds because some apps that you are running are requesting that service.
as someone said here, yes, even I kill games after I stop playing, BUT, I do it from the task manager built in. Settings - Apps - Running apps etc.
1ceb0x said:
let me tell you something about google services...
when you installed your rom, you had to check two options from google services - location and another one.
if you are on stock, those options are available in settings also.
the google services are needed (you are running a google os, right?) because without it, the location feature will not work, the play store will give you headaches and not to mention, google now that needs that service like water.
if you kill that process over and over again you will not gain anything because that service will keep restarting it until you will give up. ah, you will loose a massive amount of battery if you do so
another thing, the google service is a system app. system apps have priority in resources so even if you kill now, as i said, it will restart after a few seconds because some apps that you are running are requesting that service.
as someone said here, yes, even I kill games after I stop playing, BUT, I do it from the task manager built in. Settings - Apps - Running apps etc.
Click to expand...
Click to collapse
if u dont want them to restart use, autorun manager
task killer
Well, i think a task killer is useful. It sometimes helps to speed-up the phone a bit.
snelle-eddie said:
Well, i think a task killer is useful. It sometimes helps to speed-up the phone a bit.
Click to expand...
Click to collapse
No that is wrong.....it consumes more ram it self
Sent from my One V
Normally to kill a process I use the Running Tab in Apps, If any recently opened app which I feel should be closed is open I kill it!Though I leave the google services untouched!
Stopped using Task managers and Battery saving apps long time ago!
Want to really save the juice? Try Under Clocking! and killing the bloatware(saves RAM too!)
I used to have a task killer but the more I killed apps, the slower my phone was, so I eventually ended uninstalling it.
great post. lots of usefull info!!
Instead of using a task killer to keep on eating your battery life, simply either delete the app or disable it in your system if it's a system out (eg: default browser, bloatware, etc).
https://play.google.com/store/apps/details?id=com.zomut.watchdog&feature=search_result
its good, but most android users atleaast ppl like me know which apps are usefull and which are not
cybervibin said:
its good, but most android users atleaast ppl like me know which apps are usefull and which are not
Click to expand...
Click to collapse
Assuming you are replying to me, your response is a bit ambiguous...
In windows one can disable useless running services. Is there a way to do the same in Android? Seems that would save some resources - such as battery. I searched, but could find no real info...
Thanks!
Yes and no. In Android only one foreground app can run at a time, but there are background services too. They are usually important system services, but apps can add them too (they're needed to receive push notifications for example).
Go to Settings > Apps, swipe right to "Running". Then you can toggle between "Cached background processes" and "Running services". Killing a cached process (a previously active foreground app) doesn't really make a difference since it wasn't running anyway. Killing a service sometimes has an effect, but usually the service restarts automatically.
To permanently shut down a service, use the app Greenify. It "hibernates" apps with background services but still lets you run the app when you need it. Keep in mind that you lose the functionality of that service (e.g. if you hibernate Facebook, you won't receive notifications when you receive Facebook messages).
But honestly, unless you installed some badly coded apps that use too many services, you probably don't need to.
Thank you very much for the reply and info. I installed the app "Greenify" - and it is great the way it's set up. Like you said, if not all - most apps will start-up if stopped running in the background when not using, and *that*, IMO, is a great way to stop wasting the poor battery performance (mainly because of age) of the TF101 (tablet only).
Many thanks! :good:
Cal
#android 4.4.2 #cyanogenMod 11 M6
I have some applications like skype, mtalk and twitter that must run in foreground all the time. Unfortunately I just started playing seriously with android and I feel lost.
It would be great if:
the listed apps will be auto-started after a reboot
even in the case I accidentally turn off an application, they will be restarted after a few minutes
if these settings will be associated to a user profile (i.e. if "work profile" is selected then those apps will be in foreground)
I've read in some posts that the Tasker app might be useful for this. Any other suggestion?
You can try Advanced Task Killer, this program kill the background processes.
torjai.robert said:
You can try Advanced Task Killer, this program kill the background processes.
Click to expand...
Click to collapse
well killing the application is exactly the opposite of what I want to do
[APP][4.0+][ROOT optional] SystemPanel2: It does not "BOOST". It does not "CLEAN".
SystemPanel is a tool to help manage your device, improve battery life, and keep it running fast by monitoring application activity. SystemPanel v1 has been in development since 2009; this is v2, and is a complete re-imagining of the idea. V2 is beta, under development, and suggestions and bug reports are greatly appreciated!
SystemPanel does NOT "clean" or "boost" your phone. Well, maybe it does, but even having been a full-time independent Android app developer writing system utilities for nearly a decade, I still haven't figured out what those terms mean. It won't magically double your battery life, but SystemPanel gives you the ability to visualize what's consuming resources. It might show you that some game or app is running full-bore long after you think you've stopped playing and turned the screen off. Or it might show you that some tool running in the background to "boost" your phone is actually only boosting your battery gauge toward zero. Or you might find that your phone and its apps are working perfectly, but it can still offer insight into which activities drain your battery most quickly.
Download link: https://play.google.com/store/apps/details?id=nextapp.sp
Overview
.
The main "overview" screen shows a brief summary of device status. Items on this screen include an overview of the top apps/processes right now, CPU/network usage, and a short history of battery drain rate and resource usage.
Tap any section to see more detail. (The hamburger menu can also be used to switch between screens at any time.)
Live
.
The "Live" screen is divided into two sections, "Running" and "Status". The "Running" screen shows a list of active apps and processes. You can tap on any app to see details about its current activity, history, installation info, etc. Long-press for a quick-access menu.
The "Status" screen shows basic device status information. CPU/Network/Memory consumption data, Wi-Fi/Cellular signal, and device temperatures.
History
.
The "History" section lets you see a week-long history of device activity. You can visually observe app/display activity over time and compare it to battery performance. The plots can be scrolled and pinch-zoomed. Switch from the "Activity" tab to "Top Apps" to see a complete list of what was running during a particular time period. The top 3 apps/processes are always shown on the "Activity" tab as well.
Note: you'll need to let SystemPanel record some history for a day or so before you'll see any meaningful data from this feature.
Analysis
The "Analysis" section is a bit experimental at the moment, it's under heavy development. The idea is to show you a picture of the recent history (last two hours or so) of your device in order to alert you to any recent battery-draining applications. In the Analysis section, SystemPanel itself processes history data and calls attention to problem items. There's more to come here.
Apps
"Apps" shows you installed applications on your device. Root users can disable apps directly here.
You can also "archive" applications to user storage and reinstall older versions (it turns out not all updates are good). Currently this feature is limited to backing up the APK itself, but I hope to improve this.
The "Permissions" section of the apps page shows you apps listed by the permission groups they use. Root users can enable/disable permissions for Android 6+ apps.
App Details
.
.
Clicking on any app or process item (of any SystemPanel screen) takes you to the App details screen. Here you can see details of the app's installation and permissions, its current resource utilization, its resource use over the past week, and its current storage use.
A services tab lists all services provided by the app. Root users can disable individual services. This can be useful for blocking OTAs to customized devices or turning off other undesirable items.
Device
.
The "Device" panel shows system information about your device.
NOTES
Privacy: no information recorded by SystemPanel ever leaves your device. Everything recorded is for *YOUR USE* and is not sent to anyone else, ever.
Root Access: SystemPanel does not require root. On Android Nougat (7.0) and later, root is extremely beneficial as Nougat restricts all access to running process information. SystemPanel wll work on Nougat without root, but its capabilities are limited.
Ads: You can use the app in ad-supported mode for free, and there's a "Plus" key if you want to remove the ads. The ads are Google AdMob "Native" ads. They don't animate or annoy, and are designed to blend into the design of the app (all ad content is however specifically marked as ad content). When the Plus key is installed, the ad engine is not even initialized.
Permission Usage
Close other apps: Used for "end process" feature.
Google Services: Required by in-app-billing/AdMob. Not used elsewhere. App does not depend on Google Play Services.
Internet/Network Access: Required to monitor Wi-Fi state and to show network information in device tab. Also required for AdMob.
Location: used only in "Device" section to show GPS location per user request.
Package Usage Stats: Currently not used, but planned for future update to "Analysis" reporting to indicate whether a particular process was in foreground/background state.
Phone/Read Phone State/Identity: Required to retrieve cell signal data, also used to display telephony information in "Device" section. This is used only to display this information to you.
Prevent device from sleeping: Required for recording history data in the background. (Wakelocks are only taken momentarily).
Retrieve running apps: Used to retrieve some minor detail information about running apps on some devices. This permission has largely been inerted on newer Android devices.
Run at Startup: Required to start history recording service (when enabled).
Storage: Used for app archival and application storage usage analysis.
Root access is used/required for the following operations:
Retrieving any kind of information about running processes on Android 7 (Nougat) and later.
Retrieving information about system processes (i.e. processes which are not Android Apps) on Android 6 (Marshmallow) and later.
Enabling/Disabling packages (non-root users may use "control panel" option to use Android preference panel for this purpose, where permitted by the OS).
Enabling/Disabling services
Killing apps and system processes. Root is not required for normal "End Process" feature to request an Android application to stop. Root is only required to send UNIX TERM/KILL signal.
Download link: https://play.google.com/store/apps/details?id=nextapp.sp
[Reserved]
I'll try it
Hey, I remember using version 1 from way back. Definitely on the OG Droid. I never used it to kill apps, but over clocking was the thing to do back then so there were a lot of things I could keep an eye on with your app. Also, it had nice graphs. I'll give this a whirl.
Saw this app at Android Police before. Great feature set.
Great app! The first one which is able to measure CPU load on N. Would be great to a have a widget or a permanent notification with the most usefull data (cpu load, clock, temp and battery temp)
Wonderful to get this tool back for newer system version.
The original systempanel was one of the first (I think THE FIRST) Android app that I've ever purchased and I've been a user for many years.
Great to see v2 out! SystemPanel has always been a great app to help diagnose problem apps.
Thanks everyone!
BTW just discovered a "brown paper bag bug" that can happen the first time you grant SystemPanel root access. There's a case where SystemPanel will attempt to perform a root operation on the user interface drawing thread (a giant "n00b" mistake in Android development). This can cause the device to freeze for 5-10 seconds if it happens to be the first such operation and hasn't been granted root access before. Thankfully it only happens once and will be corrected in next version.
Tiz92 said:
Great app! The first one which is able to measure CPU load on N. Would be great to a have a widget or a permanent notification with the most usefull data (cpu load, clock, temp and battery temp)
Click to expand...
Click to collapse
Widget, notification, and a persistent-overlay are all on the table...I probably just want to implement all three.
SystemPanel 2.0.b3 (r2041) now available in the beta channel.
"Surprise Her with Improved Android Analytics"
(Moved to production)
Changelog:
Added support for monitoring the active foreground application using an Accessibility service. You'll have to grant SystemPanel's service permission to operate via your accessibility settings for this to work (even if you have root). SystemPanel's settings contain a convenient link to turn this on in the "General" section. It's entirely optional. Currently foreground-process data is used on the analysis and specific-app-history screens, but this will be expanded soon.
Fixed bug where it was difficult to scroll vertically on screens with lists of plots.
Fixed startup bug for root users where some devices would hang for a couple of seconds.
Updated chart legends.
More precision added to use percentages in History/Top-Apps.
App-Info screen now differentiates between supported and required features of apps.
App-Info screen now shows when app was last used (if usage access is enabled). More usage stats features will be added soon.
Fixed bug where disabled services hidden on App-Services screen under Nougat.
Added "Tools" screen to "Device" section. Currently provides shortcuts to accessibility and usage stats preferences (some devices don't have any way to access these). Also allows access to device "Testing" screen (some devices support).
I've resurrected the beta channel for those that want early access to new releases, you can opt-in here: https://play.google.com/apps/testing/nextapp.sp
The product itself is of course beta, but opting into the beta channel will get you new releases earlier. Product will move to the main stable channel shortly thereafter.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Look at the circled part.
The 100% is missing and you can only see the bottom part of the number (zoom it).
Sent from my MI 5s Plus using Tapatalk
Thanks, need to remove this... I think I want to leave the 100% indicator off (it's easily implied and would crowd section label).
SystemPanel 2.0.b4 now available in the beta channel.
This release adds a new major section, "Usage". Usage data shows a history of the apps you've used on your phone. This data can be viewed in aggregate form to see which apps you use most and how often you're using your device.
There's still a long way to go with "Usage". E.g. it needs to be more integrated with the history section, so you can quickly see the effect that usage had on the device (i.e., battery drain). There is currently no "overview" section that takes you to the usage screen, it's accessible from the slide-out panel.
Like history data, usage data is visible for 7 days and data older than 10 days is purged from the database. Like all recorded information, data is never sent from your phone to anyone/anywhere.
"Usage Statistics screen", showing app usage in the last 24 hours.
Usage log screens. The left screen shows a raw log of app usage (in this case with launcher/SystemUI stuff filtered out). The right screen shows apps which ran for more than 10 minutes.
.
The "CPU" indicator below the app title shows the average CPU usage while the app was active. The battery indicator shows the net battery drain (or charge) while the app was active. This battery use is simply the amount the device's battery changed while the app was in the foreground, it does not indicate that the app itself consumed that much battery. This will explained in more detail when a help section is added to this screen.
The usage section works just fine on Android 7 without root. It uses the accessibility service (which must be enabled) to work. Once it's more integrated with the history section, this feature may be useful to non-rooted Android 7 users to determine if an app running in the foreground kept running longer than it was being used.
Changelog:
Added Usage section.
Added workaround for bug when scrolling plots when viewing a specific app (unfixed bug in Android widget library itself).
Removed broken 100% axis marker in history section of overview screen.
Fixed min/max clock frequency data in device section.
This release has been initially uploaded to the beta channel. It will be placed in production soon assuming further testing proceeds well.
The beta channel for those that want early access to new releases, you can opt-in here: https://play.google.com/apps/testing/nextapp.sp
The product itself is of course beta, but opting into the beta channel will get you new releases earlier.
No cell signal data
Hello, I'm a big fan of your apps, I've been using FX since 2012 and I was fond of the original system panel. I think the new system panel is just beautiful.
One thing I notice is, I don't seem to be getting any record of cell signal. The LTE bar is always blank and there's nothing in cell signal history. This is on a Verizon Galaxy G7 with Marshmallow.
MKairys said:
Hello, I'm a big fan of your apps, I've been using FX since 2012 and I was fond of the original system panel. I think the new system panel is just beautiful.
One thing I notice is, I don't seem to be getting any record of cell signal. The LTE bar is always blank and there's nothing in cell signal history. This is on a Verizon Galaxy G7 with Marshmallow.
Click to expand...
Click to collapse
Thanks and thanks for reporting this...
OEMs have severely failed on implementing Android's APIs for retrieving cell signal data. Some return nothing and others return random nonsense. Samsung is one of the worst offenders. I have a few Samsung test devices (including as-of-yesterday an S7 Edge) and will be trying to correct this. At the absolute minimum, I need to not display the data if it's out of range (some of this is already in place, but doesn't always work). Would prefer to workaround on popular broken devices though (e.g. Samsung Galaxy S/Note stuff).
I'm very happy I picked this S7 up...gorgeous hardware but somewhat ridiculous software (though slowly improving and debloating). I rooted it before even turning wifi on, and noticed some shortcomings when using SystemPanel to help debloat it (e.g. the UI for disabling packages is too slow.) Next version will also be categorizing apps by whether they're user-facing (have a launcher icon) or not. I think this thing came with 330-something system apps,, I've disabled 50+ already. I'll be tempted to get an international S8 as my own phone if I can put Lineage on it.
New feature request
Two, actually
First and foremost, battery usage rate (e.g. %/hr). To me, this is the most useful battery metric, to see in history and correlate with CPU and signal and so on. I'm always squinting at the battery % graph trying to estimate the slope....
Second, how about some info on sensors? Nothing too fancy, a list with current values perhaps?
tliebeck said:
Thanks and thanks for reporting this...
OEMs have severely failed on implementing Android's APIs for retrieving cell signal data. Some return nothing and others return random nonsense. Samsung is one of the worst offenders. I have a few Samsung test devices (including as-of-yesterday an S7 Edge) and will be trying to correct this. At the absolute minimum, I need to not display the data if it's out of range (some of this is already in place, but doesn't always work). Would prefer to workaround on popular broken devices though (e.g. Samsung Galaxy S/Note stuff).
I'm very happy I picked this S7 up...gorgeous hardware but somewhat ridiculous software (though slowly improving and debloating). I rooted it before even turning wifi on, and noticed some shortcomings when using SystemPanel to help debloat it (e.g. the UI for disabling packages is too slow.) Next version will also be categorizing apps by whether they're user-facing (have a launcher icon) or not. I think this thing came with 330-something system apps,, I've disabled 50+ already. I'll be tempted to get an international S8 as my own phone if I can put Lineage on it.
Click to expand...
Click to collapse
Im with you on international as i have a T-Mobile s7e. I need and miss root. Exynos don't play well with cm based roms that's caf supported. But Samsung really improved
Sent from my hero2qltetmo using XDA Labs
MKairys said:
Two, actually
First and foremost, battery usage rate (e.g. %/hr). To me, this is the most useful battery metric, to see in history and correlate with CPU and signal and so on. I'm always squinting at the battery % graph trying to estimate the slope....
Second, how about some info on sensors? Nothing too fancy, a list with current values perhaps?
Click to expand...
Click to collapse
Need to get the battery rate graph in SP2 (it was in the original). I do want to do a sensor list, undecided if this will be under the "Device" tab or in its own (will have to see how it flushes out). If "Sensors" winds up being its own top-level section, then the "Device->Location" feature will move there as well. I actually am inclined to try to make this section a bit fancy though... should be easy to make it look pretty (and informative) with lots of plots.
milojoseph said:
Im with you on international as i have a T-Mobile s7e. I need and miss root. Exynos don't play well with cm based roms that's caf supported. But Samsung really improved
Sent from my hero2qltetmo using XDA Labs
Click to expand...
Click to collapse
I'm waiting patiently (on MM) for this to update for Nougat... https://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470/page31
I'd really hoped I was done with the locked bootloader thing after leaving Verizon.