Related
as title really.
some apps i only use every other day auto start. there's no need for it and i have to kill em off.
is there a way yet of preventing them from starting automatically?
tommo123 said:
as title really.
some apps i only use every other day auto start. there's no need for it and i have to kill em off.
is there a way yet of preventing them from starting automatically?
Click to expand...
Click to collapse
Try Autorun Killer, it's in the market
Sent from my HTC Desire using XDA App
Market -> Startup Manager
;-)
be careful though, stopping the wrong things from starting up can bork your phone
tommo123 said:
some apps i only use every other day auto start. there's no need for it and i have to kill em off.
Click to expand...
Click to collapse
Q. Why do you have to kill them off?
Regards,
Dave
they use memory and use the cpu from time to time. for things i only use on occasion it doesn't make sense for them to run all the time.
same with windows, programs add themselves to the startup list. it's pointless if you use those programs only once a week or so
anyhoo, tis working now.
ta all
tommo123 said:
they use memory and use the cpu from time to time. for things i only use on occasion it doesn't make sense for them to run all the time.
Click to expand...
Click to collapse
IMHO, not enough to make any serious difference.
If the apps are not being used, they will consume little to no CPU cycles, and if memory becomes tight the system will automatically kill them off.
same with windows, programs add themselves to the startup list. it's pointless if you use those programs only once a week or so
Click to expand...
Click to collapse
Yes, but the task management on Windows is vastly different to Android, so I don't think you can draw direct any accurate conclusions from the comparison.
My experience with Android stretches back to the US release of the G1 (~ October'08), and so I've been through all of these "performance enhancements" before (autostarts, task killers etc etc) on the G1, and then later the Hero.
In the long term, I've found leaving the system alone to do its own thing improves the experience and I regularly get 30+ hours usage from a single charge (heavy user) and absolutely zero issues with lag - your mileage may vary of course!
Regards,
Dave
i get that, i also (as a bit of a e-control freak) can't stand things running when they have no need to. i have the paypal app, and even though it's something i would probably use every few weeks, runs all the time. it would be more efficient to have power user disallow these from running except when needed. it's annoying really since i want control of what happens on my phone
i did say i was a control freak
my concern is if the app is killing my battery ? I notice even with the task killer , I kill all apps (running ) but it appears again later on the list.
Will Autorun Killer stop the apps completely when not in use ?
Hi, I'm new here and new to the Android platform in general - just bought my Evo 4G last week.
I rooted the phone and have been using the Fresh ROM, but have noticed that it has some pretty severe battery-draining issues, unless I'm just using the wrong apps and settings.
Either way, I wanted to try out some other ROMs but I cannot find anything that works well so far. I tried out Cyanogen but of course it has no 4G access. Kind of a waste of that extra $10/month huh?
MIUI had some acclaim on the forums, but once again: no 4G according to the update log.
I had read on MakeUseOf or a similar site that the Baked Snack ROM is a good option for staying purely lightweight.
Before trying any other ROMs, I wanted to get some community feedback. I generally use these apps for my phone:
Browser
Google Voice
Gmail
DropBox
Endomondo
Pulse (RSS Feeds)
Which ROM would be most recommended to maximize performance and battery life with these apps, while still taking advantage of 4G capability?
Thank you for the help.
Every phone is different so someone's experience with a particular kernal/ROM will not necessarily be the same for you.
You mentioned bad battery life you also mentioned that you bought the phone last week. Since its a new toy, all you are thinking about is spending time on it. If you have 10 hours worth of battery on a full charge but 6 of those hours are awake then you are getting good battery life.
I recomend just breaking in your toy (not breaking it) and you'll notice much better battery life and time goes on since you'll be using it less.
In the meantime:
1. limit your 3g when you're not using data
2. limit your screen brightness
3. live wallpapers are nice, but they can use some battery
4. I sign out of gtalk and make sure to turn off automatic logging in
5. Sync as often as you need to but not more than that.
Good points, thank you. And yes I've been using it constantly.
Nevertheless, I downloaded Advanced Task Killer to monitor what's going on at different times. I notice certain native apps always kick themselves on, and I was hoping to disable those.
For instance, Voicemail is constantly turning itself on and I don't need it - I use Google Voice. Is there a way to disable or uninstall this altogether?
On reboot, I notice a whole list of about 10-15 apps that start themselves up too, which I usually proceed to shut down since I obviously don't need all those running in the background. Is this a good idea?
NoCatharsis said:
Good points, thank you. And yes I've been using it constantly.
Nevertheless, I downloaded Advanced Task Killer to monitor what's going on at different times. I notice certain native apps always kick themselves on, and I was hoping to disable those.
For instance, Voicemail is constantly turning itself on and I don't need it - I use Google Voice. Is there a way to disable or uninstall this altogether?
On reboot, I notice a whole list of about 10-15 apps that start themselves up too, which I usually proceed to shut down since I obviously don't need all those running in the background. Is this a good idea?
Click to expand...
Click to collapse
Get rid of your task killer immediately - it does more harm than good. Quit worrying about apps popping up when you don't use them.
If you want to uninstall apps you don't use that are "system" apps get Root Explorer.
Yeah - if you want a good app killer, get System Monitor from the Android Market...its only a few bucks and it gives you a lot more insight as to what is being used and what is not. I had Task Killer, but it stopped working when the OTA Froyo update was launched - which sent me searching a Froyo compatable Task Killer...
JayStation3 said:
Yeah - if you want a good app killer, get System Monitor from the Android Market...its only a few bucks and it gives you a lot more insight as to what is being used and what is not. I had Task Killer, but it stopped working when the OTA Froyo update was launched - which sent me searching a Froyo compatable Task Killer...
Click to expand...
Click to collapse
Task Killers are not needed on a andriod device it only restart the app thus causing problems and battery drainage in the long run...Most experienced users can tell you that they will do more harm to your system then good...system panel is a good app for figuring out if you have a rogue app taking up all your cpu and not letting your phone sleep...good luck happy flashing
Again, I appreciate all the advice here, but I don't believe anyone has addressed the issue at hand:
What are some good options for a light-weight ROM that allows usage of my 4G capability?
From my searching, even on other sites, supposedly this topic has been beaten to death, yet I can't seem to find much about it.
Basically, I would like to keep apps, like Facebook, Email, and Amazon Video, etc., from running until I start them up. Then I would like for them to close, and stay closed, when I'm not using them. In essence, act like a typical app.
All I have been able to find is that you can use a Task Killer to achieve this. But, the average opinion seems to be is that the TKs uses as much, if not more, resources repeatedly killing the constantly restarting apps as just letting the apps "run". Basically, I've yet to find out if it is or isn't possible to keep these apps from constantly restarting on their own.
The reason I want to make these changes is that when my memory gets full, my Fire will lock up, or slow down, for 30 seconds or so... sometimes longer. Supposedly, the O/S is designed to keep as much in memory as possible and it supposedly frees up memory quickly, from apps that you aren't using, when needed. In my experience this is definitely not the case... especially when I click the Task Killer button and my Fire instantly returns back to normal speed... and never did the CPU go above 600Mhz (which is the min I have it set to).... which means it wasn't an issue with the CPU being overloaded.
So does anyone know of a way to keep these persistent apps from being persistent?
BTW, I'm running a pretty standard rooted Fire that I just re-did using the KFU v9.6 and all the "goodies" with it, like the GoLauncher.
TIA
PBFred said:
Supposedly, the O/S is designed to keep as much in memory as possible and it supposedly frees up memory quickly, from apps that you aren't using, when needed. In my experience this is definitely not the case... especially when I click the Task Killer button and my Fire instantly returns back to normal speed...
Click to expand...
Click to collapse
It's true that, under normal circumstances, you shouldn't worry about it. It sounds like your system is simply lacking in memory because it has some high priority tasks eating it all away (Carousel + GO Launcher are probably hogging up a bunch already).
Seeing how you're running rooted Stock with Go Launcher and a bunch of other applications - have you considered switching to Modaco? It's based on Stock...
PBFred said:
So does anyone know of a way to keep these persistent apps from being persistent?
Click to expand...
Click to collapse
To answer this question, other than applying memory scripts, some task killers can be set to autoclose a pre-defined list of apps when you press a widget button - this may interest you. Look into the settings/options of the task killer you're using.
Maybe give this a shot?
https://play.google.com/store/apps/details?id=com.rs.autorun&hl=en
PBFred said:
From my searching, even on other sites, supposedly this topic has been beaten to death, yet I can't seem to find much about it.
Basically, I would like to keep apps, like Facebook, Email, and Amazon Video, etc., from running until I start them up. Then I would like for them to close, and stay closed, when I'm not using them. In essence, act like a typical app.
All I have been able to find is that you can use a Task Killer to achieve this. But, the average opinion seems to be is that the TKs uses as much, if not more, resources repeatedly killing the constantly restarting apps as just letting the apps "run". Basically, I've yet to find out if it is or isn't possible to keep these apps from constantly restarting on their own.
The reason I want to make these changes is that when my memory gets full, my Fire will lock up, or slow down, for 30 seconds or so... sometimes longer. Supposedly, the O/S is designed to keep as much in memory as possible and it supposedly frees up memory quickly, from apps that you aren't using, when needed. In my experience this is definitely not the case... especially when I click the Task Killer button and my Fire instantly returns back to normal speed... and never did the CPU go above 600Mhz (which is the min I have it set to).... which means it wasn't an issue with the CPU being overloaded.
So does anyone know of a way to keep these persistent apps from being persistent?
BTW, I'm running a pretty standard rooted Fire that I just re-did using the KFU v9.6 and all the "goodies" with it, like the GoLauncher.
TIA
Click to expand...
Click to collapse
Just let the OS do what it was designed to do, which is manage the apps and memory automatically. Any interference with that setup will only be a detriment to performance and battery life.
These are not full-featured Operating Systems like what is running on your desktop. Android (and iOS, and even Win8 Metro) automatically manages free memory, running processes, and stopping/starting of apps.
If you try to mess with this, it will cost you battery life and performance as the OS will continue to attempt to maintain it's designed status-quo by restarting apps that you've killed, and reassigning memory that you've freed up.
Task killers are only handy if you have an app that runs away and won't allow itself to be shut down (happens less often with every release/update), and even then, just cycling the device is more than enough to clean that up.
tl;dr Task Killers - Don't.
taskillers worked great in cupcake and donut... Using them In ics is just abusive.
PETA (peeps for ethical treatment of Android)
Sent from my HTC One S using xda premium
AlexDeGruven said:
tl;dr Task Killers - Don't.
Click to expand...
Click to collapse
This may be a dumb question, but I've read that kind of synopsis several times. With the release of ICS however, we have the option of killing previously running apps via the multitasking bar. What's the difference?
BleedsOrangeandBlue said:
This may be a dumb question, but I've read that kind of synopsis several times. With the release of ICS however, we have the option of killing previously running apps via the multitasking bar. What's the difference?
Click to expand...
Click to collapse
It's mostly in the way the OS talks to the task at hand. A Task Killer simply yanks the rug out from under the application in question, whether it's in a safe-to-stop state or not, and disregards any background services an app might be using. In many cases, the OS interprets this as a crash and attempts to get the app back into a 'normal' state.
ICS's task management politely asks (for lack of a better term) the app to stop and take any of its background processes with it. Sometimes, only the very foreground part of the app closes, sometimes the entire application and all services stop. But at the very least, you don't have the constant kill-recycle cycle that occurs with task killers.
ICS's method is much preferred, if not necessarily needed in most cases. I use it as a convenience to keep the list of recent apps clear.
androidcues said:
taskillers worked great in cupcake and donut... Using them In ics is just abusive.
PETA (peeps for ethical treatment of Android)
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
For memory management, yes. For killing wakelock abusers - they still have a reason for existing there.
Mainly Facebook. Facebook STILL holds excessive wakelocks on a regular basis (although it's not as bad as the perma-wakelock it held a year ago), and is the primary reason I keep Advanced Task Killer around.
Never use an autokiller though.
Only use a task killer for managing identified misbehaving apps that you just have to keep around for some reason (like Facebook). Never use a task killer for memory management reasons - only use it on apps that are using excessive background CPU or wakelocks. (usually, apps that are high on the ****list in Settings->Battery.)
There are programs like 'Gemini Task Manager" that will let you edit/modify the automatic startup settings for any particular app. At the very least it will let you see what apps may be causing problems on your device. As far as I know it only edits the startup to keep them from running in the first place rather than constantly killing them when they do like some task managers.
Thanks for all the info. It appears that just leaving it the way it is is what I should do... especially since 95% of what I use the Fire for is for reading books. But I am a Windows/Cisco Sys Eng, so I like to tinker with all my tech devices whenever I can.
That being said, it seems to me that if these "persistent apps" were on a Windows O/S, they would be running as a Service. And if you know Windows, you would know that Services can be set to restart if they are stopped by any means, except through the Service Manager Console itself (or the command line, if you really know Windows). But I have no clue if Linux/Android has the equivalent of Windows Services. I would have to believe that full-fledged versions of Linux/Unix does, but maybe not Android. Just a thought... and maybe it is something people have overlooked when trying to keep these "persistent apps" from being persistent.
Typically, in Windows, you would never ever think of running Facebook as a Service... but you easily could if you wanted to. And it appears that Amazon really wants Facebook, and several other apps, to be running at all times, for no apparent reason.
Oh well, if I had a 2nd Fire, I would "hack" the hell out of it. But since I don't, and I read a lot, I'll just be happy with what I got. And honestly, even after having the Fire since the first day it came out, I'm still loving it.
PBFred said:
Thanks for all the info. It appears that just leaving it the way it is is what I should do... especially since 95% of what I use the Fire for is for reading books. But I am a Windows/Cisco Sys Eng, so I like to tinker with all my tech devices whenever I can.
That being said, it seems to me that if these "persistent apps" were on a Windows O/S, they would be running as a Service. And if you know Windows, you would know that Services can be set to restart if they are stopped by any means, except through the Service Manager Console itself (or the command line, if you really know Windows). But I have no clue if Linux/Android has the equivalent of Windows Services. I would have to believe that full-fledged versions of Linux/Unix does, but maybe not Android. Just a thought... and maybe it is something people have overlooked when trying to keep these "persistent apps" from being persistent.
Typically, in Windows, you would never ever think of running Facebook as a Service... but you easily could if you wanted to. And it appears that Amazon really wants Facebook, and several other apps, to be running at all times, for no apparent reason.
Oh well, if I had a 2nd Fire, I would "hack" the hell out of it. But since I don't, and I read a lot, I'll just be happy with what I got. And honestly, even after having the Fire since the first day it came out, I'm still loving it.
Click to expand...
Click to collapse
It's still completely different system paradigms. In mobile OSes, background services are typically in a paused state when not actively in use, where in full-featured OSes, they can be in any one of several states.
As to the fb service running, that has nothing to do with Amazon. That's just the fb mobile developers not knowing what they're doing.
Sent from my Amazon Kindle Fire using Tapatalk 2
Hello everyone, im going to choose a phone for my cousin and i was looking to s20+ exynos. Its a great phone but when i bought it in 2020 summer, it was heating up a lot even when doing normal tasks like using chrome or watching youtube. For comparison, when using zoom s20+ got up to 42-43 Degree battery and was really hot, same conditions s10+ was something like 31battery. After 2 days i returned the phone. Now i suspect this was due to software problems and wanna know if phone still heats up like this during normal use.
My Note 10+ Snapdragon was a hot running battery hog when I first used it. Today it's a fast, stable, cool running platform. Same firmware but I optimized it over time.
If you expect an Android to run perfectly out of the box you're having Apple delusions
blackhawk said:
My Note 10+ Snapdragon was a hot running battery hog when I first used it. Today it's a fast, stable, cool running platform. Same firmware but I optimized it over time.
If you expect an Android to run perfectly out of the box you're having Apple delusions
Click to expand...
Click to collapse
I suppose its okay for it to not be perfect but it shouldnt be that bad either. I wouldnt return it otherwise. That was definitely not a case where it would fix itself with user optimizations and a week of 'phone getting used to your patterns' bs. You clearly had a different problem if you achieved it without updates.
theblitz707 said:
I suppose its okay for it to not be perfect but it shouldnt be that bad either. I wouldnt return it otherwise. That was definitely not a case where it would fix itself with user optimizations and a week of 'phone getting used to your patterns' bs. You clearly had a different problem if you achieved it without updates.
Click to expand...
Click to collapse
Doesn't matter what the problem is most times because with Android there's always a work around even on stock Androids.
Each device and user are different... we're not all the same lame Apple
It's time consuming... until you work it out.
If you're waiting an update solution you're going to wait... and maybe still not get what you want.
That's why Gookill can jam Q and especially 11 up someone else's auxiliary port.
No real improvements and lots of useless cpu cycle robbing big sister bs. 12 will likely be worse... so I'm not throwing my money or time at it. I have that luxury.
Dead cats, dead rats
Can't you see what they were at?
blackhawk said:
Doesn't matter what the problem is most times because with Android there's always a work around even on stock Androids.
Each device and user are different... we're not all the same lame Apple
It's time consuming... until you work it out.
If you're waiting an update solution you're going to wait... and maybe still not get what you want.
That's why Gookill can jam Q and especially 11 up someone else's auxiliary port.
No real improvements and lots of useless cpu cycle robbing big sister bs. 12 will likely be worse... so I'm not throwing my money or time at it. I have that luxury.
Dead cats, dead rats
Can't you see what they were at?
Click to expand...
Click to collapse
just out of curiosity, what did you do to stop your phone from overheating?
theblitz707 said:
just out of curiosity, what did you do to stop your phone from overheating?
Click to expand...
Click to collapse
A whole lot.
First step was to disable all power management.
Then go after each offender on a case by case basis. Rogue 3rd party apps either get firewall blocked or deleted especially if they're are startup apps that don't need that privilege.
I use Package Disabler and Karma Firewall a lot.
I clear the system cache and use as needed the old Device Care powered by 360° (firewall blocked) to clear system caches and logs.
Disable all cloud junk, and other Google trashware.
Simply disabling Google play Services and Playstore when not needed gives you another 1-2%@ hr of battery life. They are hogs that tend to run needlessly.
Disable all feedback... it's data mining at your expense.
Sometimes I turn off battery background usage to certain apks like Android Services.
It all adds up... play with it.
Each device, OS and user are different, so what works well for me might puke on you.
Don't make too many changes at once and be aware of possible dependencies for the apps you alter. It's a learning curve... and sort of fun.
&
It's almost impossible to crash and burn* a stock Android. So get after it!
*always be ready for a crash. Backup all critical data redundantly and be ready to reload at any time. While very rare Android crashes give little or no warning. Slight system instability and lag are many times the only warnings you will get on a fast platform... then bam, boot loop.
blackhawk said:
A whole lot.
First step was to disable all power management.
Then go after each offender on a case by case basis. Rogue 3rd party apps either get firewall blocked or deleted especially if they're are startup apps that don't need that privilege.
I use Package Disabler and Karma Firewall a lot.
I clear the system cache and use as needed the old Device Care powered by 360° (firewall blocked) to clear system caches and logs.
Disable all cloud junk, and other Google trashware.
Simply disabling Google play Services and Playstore when not needed gives you another 1-2%@ hr of battery life. They are hogs that tend to run needlessly.
Disable all feedback... it's data mining at your expense.
Sometimes I turn off battery background usage to certain apks like Android Services.
It all adds up... play with it.
Each device, OS and user are different, so what works well for me might puke on you.
Don't make too many changes at once and be aware of possible dependencies for the apps you alter. It's a learning curve... and sort of fun.
&
It's almost impossible to crash and burn* a stock Android. So get after it!
*always be ready for a crash. Backup all critical data redundantly and be ready to reload at any time. While very rare Android crashes give little or no warning. Slight system instability and lag are many times the only warnings you will get on a fast platform... then bam, boot loop.
Click to expand...
Click to collapse
Im pretty sure your note 10 would be completely fine without any of those. If you updated a few times. But if you have to stay at initial firmware for some specific reason then fair enough. (Btw, I also used to disable google play and google services but at the time my phone had 834MB ram so it was really important, i dont think saving %1 battery is worth it at all)
When i had my S20+, phone didnt heat at all when idling so some bloatware/feedback/google services/rogue app etc. wasnt the issue. I learned from someone else it was fixed after november update. Anyways have a good day
theblitz707 said:
Im pretty sure your note 10 would be completely fine without any of those. If you updated a few times. But if you have to stay at initial firmware for some specific reason then fair enough. (Btw, I also used to disable google play and google services but at the time my phone had 834MB ram so it was really important, i dont think saving %1 battery is worth it at all)
When i had my S20+, phone didnt heat at all when idling so some bloatware/feedback/google services/rogue app etc. wasnt the issue. I learned from someone else it was fixed after november update. Anyways have a good day
Click to expand...
Click to collapse
That's a minimum. When Gookill is misbehaving it's battery usage far exceeds that and extends into when the screen is off.
My battery usage when sleeping with AOD on touch demand is 2-3% for 6 hours.
That 1 or 2% is also after much of the Gookill junkware was disabled.
Google and Samsung apps are the prime suspects... as usual.
My stock 10+ is heavily reconfigured, I have no quick fixes for you because none of mine were quick
As for updates, they ain't got nothing for me. Last thing I want is Q loading on this device.
It would gut Karma Firewall's functionality and destroy trusted overlay apks... for what?
I've already archieved all my favorite apks so I'm not longer dependent on Playstore. Playstore will eventually alter or delete them.
Anyone know how I might go about diagnosing why my phone has been running much warmer than usual? Just browsing Facebook (posts, not video) for about 5 minutes with brightness around 25% the temp was up to 41 degrees. It happened earlier today when I was just using Chrome, and it happens most days now. The issue began when I updated to 11.2.8.8 (the very next day), and the phone overheated several times the first few days, evidenced by the system warning about temperature, then recovering several minutes later. I haven't seen the system warning since then, but it's frequently above 40 degrees just doing everyday tasks. Oddly, I haven't noticed it overheating when playing games.
I usually run Omega kernel, which has always run cooler than stock during both normal use and heavy gaming, but this issue has occurred with both stock and Omega, so it's not kernel-related. The only magisk modules I have installed are debloater (for YouTube only), font manager, and systemless hosts, so that's not it either.
Maybe some app going haywire (how to find it? Nothing in battery usage) or some system behavior that changed in 11.2.8.8? Anyone else have this issue or find what's causing it?
That's just how this phone is. It was worse when the phone released before all of the updates. They've been slowly trying to fix it with each update. The 888 is a hot *****.
TheKnux said:
That's just how this phone is. It was worse when the phone released before all of the updates. They've been slowly trying to fix it with each update. The 888 is a hot *****.
Click to expand...
Click to collapse
I remember having that complaint when I first got it, especially when gaming, but it's been fine for me since like April, until this last update. And with Omega several degrees cooler. So there has to be something new causing it....
terlynn4 said:
I remember having that complaint when I first got it, especially when gaming, but it's been fine for me since like April, until this last update. And with Omega several degrees cooler. So there has to be something new causing it....
Click to expand...
Click to collapse
What version of Omega are you on? What build of OOS? AA, BA, DA? Are there any unusual rogue apps that you've noticed running more than usual?
TheKnux said:
What version of Omega are you on? What build of OOS? AA, BA, DA? Are there any unusual rogue apps that you've noticed running more than usual?
Click to expand...
Click to collapse
Latest version of Omega (8/7) since yesterday, but was having the same issue on the previous build (7/30). I'm on OOS 11.2.8.8 BA.
I haven't noticed any apps using more battery than expected, but I guess that might be part of my question... If there are any, what's the best way to find them? I'm not seeing any useful info in BBS or anything in GSam I wouldn't expect, except overall battery drain is a bit higher when it's been running hot. I do have a lot of apps installed and should probably clean up what I don't use, so I guess that's a place to start.
Find which apks are using the battery.
Google system apks are prime suspects.
Trash apps like FB, WhatsApp, LinkedIn... none of that junkware runs on my device, ever.
Examine all startup apks closely, take out the trash.
Power management can end up causing excessive battery usage, try turning it off.
Track down each battery hog and deal with it on a case by case basis rather than the flip a switch shotgun approach.
I use Karma Firewall's logging feature to help track down offenders.
Dependencies... sometimes the source of the high usage is hidden. What apks and services are running? What apks are using what services and why? What's apks are getting cached first when you clear them all? Any memory leaks?
Play with it... Androids wuv attention
blackhawk said:
Find which apks are using the battery.
Google system apks are prime suspects.
Trash apps like FB, WhatsApp, LinkedIn... none of that junkware runs on my device, ever.
Examine all startup apks closely, take out the trash.
Power management can end up causing excessive battery usage, try turning it off.
Track down each battery hog and deal with it on a case by case basis rather than the flip a switch shotgun approach.
I use Karma Firewall's logging feature to help track down offenders.
Dependencies... sometimes the source of the high usage is hidden. What apks and services are running? What apks are using what services and why? What's apks are getting cached first when you clear them all? Any memory leaks?
Play with it... Androids wuv attention
Click to expand...
Click to collapse
Good ideas. I just installed Karma Firewall and will see if it turns up anything.
How do you manage startup apps and running services? I used to use Servicely, but with Android 11 I find that even when I disable apps at startup they still start on their own, and it seems to use more battery than it saves. I've since disabled all apps of that kind and just let Android manage things itself. The only thing I do is go to individual apps and turn on battery optimization and disable background data if not needed, and I keep apps I don't use often in Icebox, including Facebook, which is the only social media type app I have. (Uninstalling FB isn't an option unfortunately.)
What do you mean by "which apps are getting cached first when you clear them all?" and how might I find it there are memory leaks?
terlynn4 said:
Good ideas. I just installed Karma Firewall and will see if it turns up anything.
How do you manage startup apps and running services? I used to use Servicely, but with Android 11 I find that even when I disable apps at startup they still start on their own, and it seems to use more battery than it saves. I've since disabled all apps of that kind and just let Android manage things itself. The only thing I do is go to individual apps and turn on battery optimization and disable background data if not needed, and I keep apps I don't use often in Icebox, including Facebook, which is the only social media type app I have. (Uninstalling FB isn't an option unfortunately.)
What do you mean by "which apps are getting cached first when you clear them all?" and how might I find it there are memory leaks?
Click to expand...
Click to collapse
Karma's logging feature doesn't work in 10 and above I believe, I run Pie. See what you got though. It will still block apk internet access though and uses almost no battery.
The battery optimization option can cause erratic behavior and I never use it. Close apps when done with them. Brave browser for instance will run in the background until closed.
Developer options>running services memory leaks show up as an apk who's memory usage just keeps increasing with time. It can get quit large. These are rare and poorly coded programs. More common on Windows.
Keep an eye though for memory hungry apps as they may be using excessive power but not always. Small memory users can be worse. Dependencies, sometimes a apk or service keeps making repeated requests because of a disabled apk or service.
Killing Goggle play Services and Playstore when not needed will help battery life.
Google backup Transport, Framework and Firebase are always disabled on my device.
All carrier, manufacturer, and Google feedback are disabled.
I have a Samsung device and I use its Device Care app to clear the cached apks. Then watch as they repopulate. You'll need an app that does this. In running services you can disable a suspect apk and see how long it takes to come back. I find that Device Care is more effective though and that ability has let me track down some misbehaving system apks saving me a reload.
FB is weaponized and a proven liability. Known data miner. Purveyor of disinformation and dissent. It has ruined countless lives and careers. It deliberately makes you have load the app to be able to send messages. If this last year hasn't taught you what you need to know...
I used it for one month 15 years ago and knew what it was back then. It's far worse today.
Don't feed the beast.
blackhawk said:
Karma's logging feature doesn't work in 10 and above I believe, I run Pie. See what you got though. It will still block apk internet access though and uses almost no battery.
The battery optimization option can cause erratic behavior and I never use it. Close apps when done with them. Brave browser for instance will run in the background until closed.
Developer options>running services memory leaks show up as an apk who's memory usage just keeps increasing with time. It can get quit large. These are rare and poorly coded programs. More common on Windows.
Keep an eye though for memory hungry apps as they may be using excessive power but not always. Small memory users can be worse. Dependencies, sometimes a apk or service keeps making repeated requests because of a disabled apk or service.
Killing Goggle play Services and Playstore when not needed will help battery life.
Google backup Transport, Framework and Firebase are always disabled on my device.
All carrier, manufacturer, and Google feedback are disabled.
I have a Samsung device and I use its Device Care app to clear the cached apks. Then watch as they repopulate. You'll need an app that does this. In running services you can disable a suspect apk and see how long it takes to come back. I find that Device Care is more effective though and that ability has let me track down some misbehaving system apks saving me a reload.
FB is weaponized and a proven liability. Known data miner. Purveyor of disinformation and dissent. It has ruined countless lives and careers. It deliberately makes you have load the app to be able to send messages. If this last year hasn't taught you what you need to know...
I used it for one month 15 years ago and knew what it was back then. It's far worse today.
Don't feed the beast.
Click to expand...
Click to collapse
Thanks for the info, it's interesting. However, if you're running Pie & not even using a OnePlus device, none of this is going to be applicable to my issue which is specific to OOS 11.2.8.8 on this particular device, only present since last month's update.
Re: FB - I'm required to use it for my job (well, second job), and I need it on my mobile device in order to do that job, so it's not going away. Freezing it when not in use is the best I can do.
terlynn4 said:
Thanks for the info, it's interesting. However, if you're running Pie & not even using a OnePlus device, none of this is going to be applicable to my issue which is specific to OOS 11.2.8.8 on this particular device, only present since last month's update.
Re: FB - I'm required to use it for my job (well, second job), and I need it on my mobile device in order to do that job, so it's not going away. Freezing it when not in use is the best I can do.
Click to expand...
Click to collapse
You cross platform OS version and manufacturer to find solutions. I have a lot of posts here but few asking for help because I do the above or just keeps at it until I work it out as it's my issue.
*shakes head*
You've painted yourself into a corner.
@terlynn4 I use BatteryGuru because it uses root to find rogue apps that are draining battery unnecessarily. Give it a go and see if that helps pinpoint the problem at all.