Question Thermal causes screen dimming . - Samsung Galaxy S22 Ultra

Is there any solution to prevent the screen from dimming after a while when using the phone ? I know that is from thermal protection but is very annoying . Its the first phone to own that has this problem . Good guardians settings dont work on this. I find an activity that is probably rensposible for this but i cannot deactivate it .
Samsung Device Health Manager Service
com.sec.android.sdhms.debugger.ui.ThermalLimitSet
tingActivity
Is there a way through adb to disable this ? I know it is dangerous but i will take the responsibility.

Figure out why it's using so much power and correct those issues. Even with the thermal protection you can cause damage like this. Eventually you will...

I know what is using so much power, its the.. Exynos chip..! And the only way to correct this issue is to buy s23u. Unfortunately if I do that i will lose a lot of money, that's why I am trying to make this phone to work as it should be..

andreasarxon said:
I know what is using so much power, its the.. Exynos chip..! And the only way to correct this issue is to buy s23u. Unfortunately if I do that i will lose a lot of money, that's why I am trying to make this phone to work as it should be..
Click to expand...
Click to collapse
The Exynos may not be as good as the Snapdragon but the excessive power consumption is likely more settings, usage and/or app related. The S22 and 23's seem to be power hogs with both chipsets.
Regardless all Samsung's should be optimized for best performance.
Start by using manual brightness control, avoid going over 50% or using in direct sunlight for more than a few seconds. Cloud apps and Google backup Transport are known habitual offenders. Try temporarily disabling Google play Services and see how much this helps; Playstore and backup Transport are dependencies.
Keep all social media, news and sales apps off the phone. Disable Google, Samsung, app and carrier feedback.
Package Disabler is helpful or you can use LADB edits, just don't go too nuts. Target power hogs and complete crapware like Digital Wellbeing.
Redundant Google apps where there's a better Samsung app can be disabled or package blocked. Deal with each power hog on a case by case basis; Do Not use global power management as it never worked right. Leave the dozens of smaller Samsung system apps alone unless they are using excessive power; most just sit there using little resources until needed.
Play with it... this will take some time and effort.

Related

End tasks when closing apps

I've noticed that when I close an app (exit it) it usually stays open in the background. An example for this would be Facebook or Google Goggles.
I don't want to have those apps drain my battery when I don't use them and I don't want to have to close them manually every time I exit them. What can I do?
Please help
Im doing the same thing too i would like to know if possible. I tried a taskmanager program but that just halts an app from coming back up again.
Sent from my Arc using XDA premium App
When any Activity is no longer the frontmost Activity (on screen), it's shut down by the OS. Any "background" Activities are simply stored in memory in case you want to go back to them. What you're seeing is essentially the history of the app; when you "open" it again it'll just reload the last saved state. At that point, the application is allowed to execute again.
The only applications that should continue running in the background are services.
The only drain you'll see are, as above, services running and the power necessary to keep the background Activities in memory; they're not actually executing.
Of course, there are ways to get around that, but most good citizens will respect Android's wishes when it comes to saving state and exiting when they're no longer frontmost.
NickWarner said:
When any Activity is no longer the frontmost Activity (on screen), it's shut down by the OS. Any "background" Activities are simply stored in memory in case you want to go back to them. What you're seeing is essentially the history of the app; when you "open" it again it'll just reload the last saved state. At that point, the application is allowed to execute again.
The only applications that should continue running in the background are services.
The only drain you'll see are, as above, services running and the power necessary to keep the background Activities in memory; they're not actually executing.
Of course, there are ways to get around that, but most good citizens will respect Android's wishes when it comes to saving state and exiting when they're no longer frontmost.
Click to expand...
Click to collapse
So when I click the "Force Stop" in the task manager on one of those applications that I've closed, what does it do? I don't think it erases them from the memory.
For instance, Facebook, when I click "Force Close" I'll still get notifications.
I'm seeing some of these applications in the Battery Usage.
Furthermore, Android will completely shut down apps in the background in order to recover the memory they're using, if it's needed elsewhere. That's really the only time that app management is necessary.
If you're simply seeing a lot of "background apps", rest assured they're not draining your battery.
If you are seeing an inordinate battery drain while you're on the home screen, you might have a service running behind the scenes that's consuming your CPU cycles.
Look for System Panel Lite in the Market; it will let you see the amount of CPU being devoted to each process. I'd bet that most of your background stuff is only eating RAM and not CPU. If there is something eating up a lot of CPU, you can investigate that particular app instead of simply force-killing everything in the background.
matanc1 said:
So when I click the "Force Stop" in the task manager on one of those applications that I've closed, what does it do? I don't think it erases them from the memory.
For instance, Facebook, when I click "Force Close" I'll still get notifications.
I'm seeing some of these applications in the Battery Usage.
Click to expand...
Click to collapse
There are two components to the Facebook app: the application itself and a service. When you "Force Close" the application, you're just stopping what you see onscreen. The service is still running, and a totally different animal than the application stuff we were discussing.
Edit: To clarify: You're seeing the package under Battery Usage, which combines the application ("Activity") and service usage to form an aggregate for "Facebook", not just one component.
Edit: (again) You're right above when you say that it removes them from memory. That, in fact, is ALL it's doing. It's removing the history/background Activities from memory. Unless that Activity is actually the frontmost Activity at that time you click "Force Close", it's not saving you any CPU time/battery usage.
Okay.
So you're saying there is no reason for me to "Force Close" every app after I've closed it?
And btw, when you say that they are in the background what does that mean?
I mean, the Active Applications widget is supposed to show me those that are running in the background right? So how come when I go to the home screen (using the back button) from an app like Facebook it won't show in the Active Applications widget but it will show Google Goggles?
matanc1 said:
Okay.
So you're saying there is no reason for me to "Force Close" every app after I've closed it?
And btw, when you say that they are in the background what does that mean?
I mean, the Active Applications widget is supposed to show me those that are running in the background right? So how come when I go to the home screen (using the back button) from an app like Facebook it won't show in the Active Applications widget but it will show Google Goggles?
Click to expand...
Click to collapse
To your first point, yes, that's exactly it. Android does this for you if it needs the memory. Otherwise, it leaves the history hanging around to make it appear the app is loading quickly the next time you open it (and it puts you right back where you left off). Note that we're ONLY talking about the user interface you see onscreen here, not any services.
Your second point requires a bit more explanation. My apologies if this gets either too basic or too in-depth; I'm not sure what your skill level is with Android. Each "window" or "screen" you see is actually a separate Activity, and is essentially self-contained. As you navigate through screens, the previous one saves what you were doing in memory and then exits. When you hit the Back button, Android simply grabs the last screen in memory and loads it back up. At that point, the application is running again. My references to "background" applications above is exactly this: screens you've left behind that are waiting for you to hit Back.
It's ultimately more complicated than that, but I think this will work for our needs.
matanc1 said:
Okay.
So you're saying there is no reason for me to "Force Close" every app after I've closed it?
And btw, when you say that they are in the background what does that mean?
I mean, the Active Applications widget is supposed to show me those that are running in the background right? So how come when I go to the home screen (using the back button) from an app like Facebook it won't show in the Active Applications widget but it will show Google Goggles?
Click to expand...
Click to collapse
To continue: Services are the real sticking point here. A service is an application that doesn't have a user interface (or screen). It's running all the time and not subject to the history/back button behavior we've been discussing. These guys are the ones you really need to be worried about, if anything. These are the ones that will run behind the scenes, consuming CPU and data (and, by extension, battery). Facebook is an excellent example: It's always checking to see if you have new messages, posts, etc. so that it can pop them up on the screen. GMail and SMS (and phone calls, even) all do the same thing using services. If the service is badly-written, it can be a real drain even when you're not using it.
You mentioned Google Goggles specifically above, and unfortunately, I'm not very familiar with how that particular app works. I suspect it's not subscribing to the good citizen philosophy and shutting down when you're done with it. It imagine it has to do with needing to perform searches or image comparisons in the background while you're off doing something else. This is technically allowed by Android, but it's frowned upon and suggested that you only do it when absolutely necessary.
Whew. All of that to say this:
Apps, as a general rule, don't consume resources when they're not on screen. They'll consume RAM, which does consume battery power, but it's really insignificant in the grand scheme of things.
Some apps will continue running after you "exit" to the home screen, but they should only do that as long as they have actual work to do. Once they're done, they should also shut down as above.
Services will consume resources all the time; they're constantly used for things like checking Facebook, Twitter, email, voicemail, etc.
okay, so again, just to summarize:
Force Closing an app just removes it from the System Memory (which makes them load faster when I open them). These apps use no additional battery life?
So I can feel free to not Force Close apps such as Camera (which I can do that to for some reason which I can't think of)?
Edit: And thank you very much Nick for the help and great responses.
matanc1 said:
okay, so again, just to summarize:
Force Closing an app just removes it from the System Memory (which makes them load faster when I open them). These apps use no additional battery life?
So I can feel free to not Force Close apps such as Camera (which I can do that to for some reason which I can't think of)?
Click to expand...
Click to collapse
You're correct. As a general rule, you don't have to force close any applications in Android. They will use some RAM and zero CPU and data, which equates to effectively zero battery.
Leaving the app in the background (in memory) loads the app faster the next time you open it, assuming Android hasn't closed it to reclaim that memory on its own. I've found that within a few minutes of heavy use (browsing the Internet, etc.), Android has shut down several of the apps in the background for me; it needed that memory to let me continue doing what I was doing.
You don't need to force close apps in the normal course of business. The only time you should force close an application is if it's behaving badly while on the screen (it's not responding to button presses or it's stuck in a tight loop or somesuch). Force closing it while it's in the background doesn't really gain you anything.
Okay, so just one last thing:
Do you have any suggestion to try and improve the battery life?
matanc1 said:
Okay, so just one last thing:
Do you have any suggestion to try and improve the battery life?
Click to expand...
Click to collapse
I have some general suggestions:
Don't sync accounts that you don't use. For example, if you don't use Facebook very often, don't have it set to sync up every hour.
Turn off WiFi, Bluetooth, and GPS unless you're actively using them. (A caveat: Google Maps uses WiFi in conjunction with GPS, so turn them both on while using Maps, even if you're not connected to WiFi.) Personally, I don't do this. I leave WiFi, Bluetooth, and GPS on all the time, but I know people who swear by this.
Keep your screen brightness as low as you can stand it. Again, I don't do this. I generally leave it on Auto-brightness.
Ultimately, though, you need to find that balance between usability and battery life. If you're always on Facebook and Twitter, sending SMS and surfing, well, there's not much you can do but keep an extra battery or charger nearby. If you're an office-worker that only uses their phone on break and at night, some of the above will probably help.
If you can give me an idea of a normal day's usage of your phone (and make/model/ROM version), I might be able to be a little more specific, or at least point you in the direction of your device's Q&A forum.
Well, I'm new to android and I've got a Samsung Galaxy S 2.
I don't really use the data connection (which is why it's always disabled unless I decide otherwise) and I turn on the Wifi only when I need it (which is often relative to 3G).
Normally I just use my phone for calls, SMSing and a bit of surfing.
About the google maps, I've noticed that it uses A LOT of battery and that it starts itself after I force close it, so I've closed the Maps service which seemed to fix the problem.
That's more or less it.
Not much syncing as well, I usually sync only when I need it.
Edit: I must say that I don't really understand what Backround Data is.
Is it that the Background Data lets the apps use data (like use facebook via wifi?) while the Auto Sync syncs automatically when I get a new email / notification? Does the background data have to do only with the my monthly data package and not with wifi ( i think that is the case ).
First off, you'll probably be better served to ask the guys in the Samsung Galaxy S2 Q&A Forum. They'll have a better idea of what the device's baseline is and what specific features you can turn off. Sometimes, as with the Samsung Fascinate, there are specific features that cause problems on the stock ROM, like Maps issuing bad WakeLocks. I know on my Fascinate before the first update, I had to toggle airplane mode every time I booted or Maps would eat the battery up in hours. Those guys in the device-specific forums will have a better handle on it, if there's anything of concern.
In general, though, it sounds like you're doing a pretty good job of keeping the device doing just what you want it to do. Android's sync framework is going to try to sync up all of your accounts essentially simultaneously whenever you turn on data, since it's probably been turned off for longer than their individual refresh intervals. You might want to turn off automatic sync on the service that you do use, so you can control those a little better when you turn on data to do something else.
Maps is a heavy data user and it makes use of GPS, which is going to consume quite a bit of power. The startup cost you're noticing is it trying to get a fix via the cell tower, GPS, and WiFi all at the same time, since the services have been off. If you use Maps often, you might be better served to leave data on (but, say, Edge only if you're GSM or 3G only if you're LTE/WiMax). This way, Maps can get a rough fix on your location at all times and not have to beat up the hardware to get a fix from scratch when you turn all the services on.
The Maps service is probably, to be anthropomorphic, freaking out all the time because it's trying to get some sort of fix while all the data services are off. Truth be told, I don't believe it was designed for that. Shutting down the service is a good way to go if you don't use it often.
You could try an application like Autorun Manager to control which services start up on boot. To make the most use of it, you need to be rooted, but in non-rooted form it will give you more control over what starts up automatically.
matanc1 said:
I must say that I don't really understand what Backround Data is.
Is it that the Background Data lets the apps use data (like use facebook via wifi?) while the Auto Sync syncs automatically when I get a new email / notification? Does the background data have to do only with the my monthly data package and not with wifi ( i think that is the case ).
Click to expand...
Click to collapse
Background Data is what services use behind the scenes (like syncing and such), but I believe it's an aggregate of all data, not just data on the cellular network. I'm looking through the docs right now to see if I can find a definite answer.
Edit: According to the docs, Background Data is data that is sent or retrieved when the application is not onscreen. This can be either in a service (as is usually the case) or when the app has to do some cleanup after you've moved to a different screen.
Thank you very much
I've noticed that I've got a few widgets that are using memory etc, ones that I don't use and never intend to.
They were preinstalled with the phone and I can't seem to uninstall them. Is there a way that I could without rooting my phone?
And on another subject, if I root my phone, is there a way to "unroot" it in case I'll need to send it to Samsung if there is a problem with it (since i've got a warranty and rooting voids it?)
matanc1 said:
Thank you very much
I've noticed that I've got a few widgets that are using memory etc, ones that I don't use and never intend to.
They were preinstalled with the phone and I can't seem to uninstall them. Is there a way that I could without rooting my phone?
And on another subject, if I root my phone, is there a way to "unroot" it in case I'll need to send it to Samsung if there is a problem with it (since i've got a warranty and rooting voids it?)
Click to expand...
Click to collapse
In theory, widgets don't consume resources unless they're on your home page. If they have services that collect their data, that's a different story. If you don't want them, you can just long-press on them and drag them to the trash can.
In conjunction with Autorun Manager above, you can remove the widget from your home page and stop the service from starting at boot. For example, I don't use Facebook (I know, lame), so I removed the widget and stopped the service. True, it's burning up a couple of megabytes of disk space, but that's insignificant next to the power of the Force, as it were.
Regarding uinstalling them, generally the answer is no. If you root your phone, you can manually remove them from the device, but that's sometimes overkill. Generally, they take up little enough room on disk that you won't be hurting for space.
In most cases, "unrooting" is as simple as flashing the stock ROM (usually available at the top of your device's development forum). Rooting your device generally doesn't make any changes to the device itself that can't be undone by flashing a stock ROM.
I've heard that rooting still leaves traces on the device though and that if they catch that it's been rooted I'm screwed. So you're saying that's not true?

Battery

I know I've made a few posts about this in the past, but now I've learned a few things since then.
I know the battery isn't the greatest on the infuse (no rom that I'm using atm..) but would like to get the most juice out of my device that I can. I have root access and currently use the apps "battery calibration" and "no-frills CPU control" which I set my cpu at a relatively low frequency to help keep juice.
My phone is drained throughout my day, even without use. I believe it primarily happens because my data (mobile network) consumes it. I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery. However, I have used this application in the past and after a few days of use, it shuts off my mobile connection altogether.
My question is, if I were to use this application again and my mobile network were to malfunction, would I be able to change my apn to regain my network connection? In the past I had to reset my phone to regain connection, which isn't really worth using if that's the only solution.
Or are there any other battery saver apps worth using??
Thanks
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Dr_Nacho said:
I know I've made a few posts about this in the past, but now I've learned a few things since then.
I know the battery isn't the greatest on the infuse (no rom that I'm using atm..) but would like to get the most juice out of my device that I can. I have root access and currently use the apps "battery calibration" and "no-frills CPU control" which I set my cpu at a relatively low frequency to help keep juice.
My phone is drained throughout my day, even without use. I believe it primarily happens because my data (mobile network) consumes it. I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery. However, I have used this application in the past and after a few days of use, it shuts off my mobile connection altogether.
My question is, if I were to use this application again and my mobile network were to malfunction, would I be able to change my apn to regain my network connection? In the past I had to reset my phone to regain connection, which isn't really worth using if that's the only solution.
Or are there any other battery saver apps worth using??
Thanks
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
A bit more information is needed before a specific course of action can be recommended. How much battery life are you using in an average 24 hour period? Also, what version of Juice Defender(beta, free, plus, ultimate) are you using, and what specific settings are you utilizing. It is a very customizable program after all. You might look into Battery Indicator Pro, which estimates your total remaining battery life based on your level of usage. I would also recommend CPU spy, which, if your device is rooted, will show the percentages that your device is running at various CPU levels.
If you turn off all the locational stuff, turn off 'update my current location' in Navigator, and set your CPU gov to conservative, you might get better battery life. I've not had any lasting luck with any of the battery saving apps. In the end, I decided to buy a couple of Anker batteries from Amazon just in case I have a bad battery day... Also some of the battery saving mods work, but I'm not sure about applying them to ICS and JB ROMS. I haven't tried!
Battery life is what you make of it..
Anything running in the background will drain the battery.. email constantly checking for new messages, twitter, Facebook, GPS, WiFi if no connection is found, etc..
Anything that makes the phone process even while the screen is off is going to kill a battery..
What ROM are you using? Some ROMs have better life than others..
How much are you actually using the phone?
What's the brightness set at?
Have you tried changing the processor and slowed it down?
Lots of information that is missing is helpful..
Its powered by Jellybeaned AOKP!
I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery
Click to expand...
Click to collapse
Some have good luck with these, others don’t. I prefer to try to adjust settings myself.
I believe it primarily happens because my data (mobile network) consumes it.
Click to expand...
Click to collapse
How about putting a widget on your homescreen to toggle data on/off. Keep it on only when you need it. I go a step further, I use Tasker to automatically turn my data off every time my screen times out (because that means I’m not using it... I can restart my data later with my widget when I need it). Maybe that’s extreme, but I’m not just watching my battery.. I’m managing my limited data plan.
My phone is drained throughout my day, even without use.
Click to expand...
Click to collapse
It may be that you have wakelocks keeping your phone awake when it’s supposed to sleep. One way to see this is (in GB or above) Settings / About-Phone / Battery Use...then click on the small graph at the top... should expand it to a large graph with traces along the bottom including Awake and Screen On. If you have long periods of time where phone is awake while screen is off, that’s a wakelock problem. A good program to troubleshoot that is Better Battery Stats. If nothing else, follow the instructions in the first post in the BBS thread linked below, and then post a dump to the end of that BBS thread (the developer and a lot of other knowledgeable people follow that thread and will help you interpret results):
http://forum.xda-developers.com/showthread.php?t=1179809
Thru use of BBS, I found that Google Maps is one that was keeping mine awake and I think someone else on the forum reported the same. If that program (Maps) is causing problems, you can disable it from auto-starting on boot using Gemini Manager. It will still be available when you need it, just take a few seconds longer to load the first time after boot. Then need to reboot to stop it from causing wakelocks after use (there may be other easier ways, but this works for me).
Another program (Power Tutor) was helpful to me to see programs that were consuming unusual amount of battery although not necessarily thru wakelocks. In my case Dolphin Browser HD was occasionally drawing very high power even when that program was not actively in use.
electricpete1 said:
I found that Google Maps is one that was keeping mine awake and I think someone else on the forum reported the same. If that program (Maps) is causing problems, you can disable it from auto-starting on boot using Gemini Manager. It will still be available when you need it, just take a few seconds longer to load the first time after boot. Then need to reboot to stop it from causing wakelocks after use (there may be other easier ways, but this works for me).
Another program (Power Tutor) was helpful to me to see programs that were consuming unusual amount of battery although not necessarily thru wakelocks. In my case Dolphin Browser HD was occasionally drawing very high power even when that program was not actively in use.
Click to expand...
Click to collapse
So how can I stop maps to running in background? only rebooting the device is the only option?or is there any other option?
TIA
atrix4nag said:
So how can I stop maps to running in background? only rebooting the device is the only option?or is there any other option?
TIA
Click to expand...
Click to collapse
Just to provide more details on my previous post (not sure if it's answering your question):
I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
In particular, I installed the free program "Gemini Apps Manager". That allows you to stop programs from auto-loading at boot.
So I used the program to stopp Google Maps from auto-loading at boot.
That stopped a large chunk of my wakelocks, as long as I don't manually launch Google Maps.
If I do manually Google Maps, then those wakelocks come back, and to get rid of them I have to reboot.
I don't use Maps that often (only when I go on trips), so it's not a big problem for me to reboot when I'm finished with my trip to help keep my battery use low.
It may also be possible to kill it from the list of applications at Settings/Applications/ManageApplications and killing botht the application and the process...but I'm not sure if it will stay killed that way... haven't tried. I know some applications have hooks that make it hard to get rid of them once they're launched.
But (if you haven't already), I think it's a good idea to use BBS to find out what programs are causing problems on your phone. You may have other apps causing lot bigger problems than Maps. And it certainly may be the case that a program that acts up on one phone can be fine on another phone due to differences in the way the user configures the application settings and the phone settings (along with other possible differences in application version, ROM used, etc etc).
electricpete1 said:
Just to provide more details on my previous post (not sure if it's answering your question):
I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
In particular, I installed the free program "Gemini Apps Manager". That allows you to stop programs from auto-loading at boot.
So I used the program to stopp Google Maps from auto-loading at boot.
That stopped a large chunk of my wakelocks, as long as I don't manually launch Google Maps.
If I do manually Google Maps, then those wakelocks come back, and to get rid of them I have to reboot.
I don't use Maps that often (only when I go on trips), so it's not a big problem for me to reboot when I'm finished with my trip to help keep my battery use low.
It may also be possible to kill it from the list of applications at Settings/Applications/ManageApplications and killing botht the application and the process...but I'm not sure if it will stay killed that way... haven't tried. I know some applications have hooks that make it hard to get rid of them once they're launched.
But (if you haven't already), I think it's a good idea to use BBS to find out what programs are causing problems on your phone. You may have other apps causing lot bigger problems than Maps. And it certainly may be the case that a program that acts up on one phone can be fine on another phone due to differences in the way the user configures the application settings and the phone settings (along with other possible differences in application version, ROM used, etc etc).
Click to expand...
Click to collapse
Thanks for your detail explanation. My main question was how can close the app without restarting? i feel my major battery drain is from dolphin browser, befor dolphin i used opera, even that has the same problem. Most of the time, if I dont open dolphin, my phone battery is good, but once I open it, it drains battery. So i am looking for soemthing simple which does, without rebooting the device.
Any way thanks for your help.

Craig's Root Batter Saver - Lollipop Supported!

So i got installing all the battery saver apps, greenify etc... they all close apps and not much else, my version comes from the mind of an electronics engineer view point...
hardware drains power NOT some little app running in the background! (Purely software programmer logic... )
So my app grabs what states wifi/gps/bt/modem at the time the screen goes off...
When the screen comes on, it re enables them! Eg go bed with 95% wake up with 94% put in your pocket it just does it...
The 2nd feature is the lost/stolen phone feature while the app itself can not get your gps data (no permissions for it) it can switch gps on/off...
So you send "on" without the surrounding quotes, the app will then switch on gps/wifi/modem/bt... it then disables itself
Now you can use wheres my droid or any other location finding app to easily pinpoint your lost or stolen phone (try getting a location with gps/agps/data disabled which people often do to save power!)
(Includes option to keep wifi/gps untouched from the app)
as for ads!... the ui has 1 ad, no popups or notifications ... and when activated the activity with the ad on is destroyed and can't touch battery life ... at all
Craig's Root Battery Saver!
https://play.google.com/store/apps/details?id=saver.battery.craigs.craigsbatterysaver
Well done
Holy crap! Someone replied (first for me here lol)
Thanks!
To be honest, your app is great when it comes to save battery, but in my opinion your approach is plain wrong in terms of the main purpose of a smartphone - receiving notifications in a timely manner, not when you turn on the screen manually. The same purpose can be achieved by using DS Battery Saver, which will in addition turn on mobile data once per specific time interval to receive push notifications.
And you should reconsider your opinion about "software does not drain battery but hardware does". Check this great thread for example. I am using a combination of different apps (Greenify, Amplify, Power Nap) to tame aggressive services/alarms/wakelocks and I am able to achieve a battery drain close to 0.0% per hour while screen is turned off with WiFi, mobile data and location turned on the whole time without losing instant notifications.
The app supports wake up notifications (well, will... the app's not quite finished yet, been too busy to get everything finished)
If you had gone to the playstore you'd have seen
Also you might want to reconsider what i said..... hardware drains it not software!
You refer to wake locks ... well believe it or not, wake locks turn on hardware which drains the battery, i program microcontrollers with the esp8266 / bluetooth / compass / etc ...
Software can only drain the battery if it's purposely trying to max out the cpu, and if it did you'd know it's malware... there are wakelock detectors too
Craig Capel said:
The app supports wake up notifications (well, will... the app's not quite finished yet, been too busy to get everything finished)
If you had gone to the playstore you'd have seen
Click to expand...
Click to collapse
I came across this, therefore my reference to DS Battery Saver, that already is capable of exact those things. Nevertheless, your app is doing what it was designed for - saving battery (and this is pretty good, indeed).
Craig Capel said:
Also you might want to reconsider what i said..... hardware drains it not software!
You refer to wake locks ... well believe it or not, wake locks turn on hardware which drains the battery, i program microcontrollers with the esp8266 / bluetooth / compass / etc ...
Software can only drain the battery if it's purposely trying to max out the cpu, and if it did you'd know it's malware... there are wakelock detectors too
Click to expand...
Click to collapse
Well, I am familiar with what wakelocks are. But without software, that produces a wakelock, there would be no noticable drain, right? Thus we can go round and round here, I guess. From my point of view the most battery drain on an Android device is the result of poorly programmed software (which results in an unneccessary wakelock) and alarms waking up your device, not from ****ty hardware. You can hunt down those wakelocks/alarms by using apps like Better Battery Stats or Wakelock Detector and reduce them to a minimum without losing functionality. Therefore I consider this as a better approach.
But without software, that produces a wakelock, there would be no noticable drain, right? Thus we can go round and round here, I guess. From my point of view the most battery drain on an Android device is the result of poorly programmed software
Click to expand...
Click to collapse
Unless the software drains it by intensive cpu work, anything else has to be hardware, if i power a gps module, talk to it via uart to enable/disable it... then it's hardware doing it not software..
Take Qualcomm, the newer cpus support an embedded DSP
https://gigaom.com/2014/12/12/5-things-to-expect-from-qualcomms-flagship-mobile-chip-in-2015/
Qualcomm*made that feature possible*in the Snapdragon 800*with its DSP, and they’re pushing hot words even farther. New devices will have the ability to passively listen, using only a small amount of power, for more than just the word “OK.” Qualcomm calls this feature Snapdragon Sense.
The first feature it will enable is a much faster Shazam search. So if you find yourself too slow on the draw when trying to identify unfamiliar music, you’ll love this: When you boot up Shazam, it’ll already have been listening just a little bit, so it can identify the song in a few seconds.
Click to expand...
Click to collapse
As hardware gets smaller and uses less power, then things like the embedded dsp chip will allow you to use wakelocks without little drainage, but were no where near that yet...
think of it like this... software simply carries instructions which can turn on hardware via a field effect transistor, that binary 1 value shows up as 3v logic and the fet begins to conduct between the drain and source, this sets a flip flop and the hardware starts wasting power...
Or to put it another way after the software enables the hardware via a gpio the software stops, or better still, show me software draining the battery with all hardware services disabled... it can't
Good
Does it really work ..
Don't you believe the title? (Really works!)
Craig Capel said:
As hardware gets smaller and uses less power, then things like the embedded dsp chip will allow you to use wakelocks without little drainage, but were no where near that yet...
Click to expand...
Click to collapse
True words. I can also see your other points and do agree with them. But as you said, we are not even close to a system where wakelocks do not drain as much as they currently do. Would we have such a system, your app wouldn't be required, I guess. Therefore taming the unneccessary wakelocks is a good way to achieve a great battery life without losing functionality for the moment.
Awesome
Awesome!!!
Can't open the settings and this sound makes me rly angry lol. Why it makes this sound? (even my phone is silence)
Gesendet von meinem ONE A2001 mit Tapatalk
There are no settings... work in progress (says so in the play store readme)
I've had the flu for the past week so i've not been developing much... expect updates shortly to remove the "settings" option which annoyingly is placed there by default... i never put it there
The sound is cool no? ... it plays a low volume sound to indicate the app is working!
Alright, update includes support for android 4.1 for gps now... i'm slowly working my way through android oddities and different techniques to switch hardware / on and off and with 5 phones to use 4 of them use kitkat!
Had to stop for a break i've had the flu all week, throwing up constantly, later on i'll add the finishing touches to wake up notifications as right now it's extreme power saving mode...
Stay tuned.... oh and i found a bug supporting lollipop, fixed that too, so if you have lollipop and it never worked, it should now ...
Antibiotics did the trick! It was sadly not the flu but some rare bug...
I've almost finished the autowakeup every x minutes 5, 10, 20 min intervals..
Unless someone here can think up a value or maybe add it as an option.
.
I removed the blocking side of things prior i used a thread/sleep now i use a timer event this stops the lag when unlocking the device on older models...
nive work :good:
I dumped the smart check (as far as i can tell anroid never fails, so i removed it)
It should now be seamless between lock screen and the main screen without any more lock up due to the threading...
Enjoy!
great!! will try it. thanks!

Battery Drain: MDE Service Framework

Battery has been bad since I switch to note 20 ultra from note 10+.
Trying to find the root cause.
Anyone knows what mde service framework is? Can't find much info on it..
aarick said:
Battery has been bad since I switch to note 20 ultra from note 10+.
Trying to find the root cause.
Anyone knows what mde service framework is? Can't find much info on it..
Click to expand...
Click to collapse
Could it be this .....quote from G search >
What is MDE Service Framework?
The Android media router framework allows manufacturers to enable playback on their devices through a standardized interface called a MediaRouteProvider . ... This guide discusses how to create a media route provider for a receiver device and make it available to other media playback applications that run on Android.Dec 27, 2019
link to my G search
https://www.google.com/search?safe=...hUKEwiJ6LLOo43sAhVtx4UKHQs9A-gQ1QIoAHoECAsQAQ
Maybe try a Factory Reset .
Could it be ,that when switching from /old backups from N10 + /re installing apps /setting /Smart switch ...etc something got corrupted ...?
I know it's a hassle, to factory reset , but as i see it
You can "stress " and look for the "culprit " , that causes the battery drain or
maybe try a factory reset ...it might help ??
Good luck
•Try to find the issues of this load otherwise doing a hard reset may only land you in the same situation.
Lot of junk running... do you need it?
A package blocker like PD MDM can be used to turn off bloatware.
Cloud services and Goggle backup tend to be habitual offenders.
Turn off Google, Samsung and carrier feedback.
I had a lot of trouble with ARcore, disable it if you aren't using augmented reality applications.
Clear data on Goggle Backup Transport, Goggle Framework and google.android.gms.policy.
Clear system cache and log files with a cleaner.
SD Maid does a good job.
I use the old version of Device Care to clean the cache when it used 360° however I block internet access when it runs then package block it because of the Chinese junk in it. It's a good cache cleaner
•Turn off 3rd party power management apks and like Adroid manage its self. Don't set apps to sleep.
•Clear system cache on the boot menu.
In Developer options in Running Services, see what's running. In Stand By Apps all buckets should show as active, if not power management is being used. Android will power them down when not in use even if shown as active.
•Monitor your battery milliamp draw in realtime; at idle it should go down as low as 60 ma at times and average about 180-300 ma at idle. Frequent or sustained spikes in the 400-1000+ range indicate excessive cpu activity; find what's doing it. Examine what was recently opened or cache when the drain starts in Running Services in Developer Options.
•Before doing a hard reset try resetting Settings; it's less drastic and time consuming.
•If you do a hard reset be more careful during setup.
Avoid loading a bunch of junk 3rd party apps... keep it clean. Test new 3rd party apps before the reload if you can.
Play with it... observe and play some more... you will find it.
Go through all the settings, poke around, see what's there and learn what it does. Unlike playing in the Windows Registry it's relatively safe to do and fun
blackhawk said:
•Try to find the issues of this load otherwise doing a hard reset may only land you in the same situation.
Lot of junk running... do you need it?
A package blocker like PD MDM can be used to turn off bloatware.
Cloud services and Goggle backup tend to be habitual offenders.
Turn off Google, Samsung and carrier feedback.
I had a lot of trouble with ARcore, disable it if you aren't using augmented reality applications.
Clear data on Goggle Backup Transport, Goggle Framework and google.android.gms.policy.
Clear system cache and log files with a cleaner.
SD Maid does a good job.
I use the old version of Device Care to clean the cache when it used 360° however I block internet access when it runs then package block it because of the Chinese junk in it. It's a good cache cleaner
•Turn off 3rd party power management apks and like Adroid manage its self. Don't set apps to sleep.
•Clear system cache on the boot menu.
In Developer options in Running Services, see what's running. In Stand By Apps all buckets should show as active, if not power management is being used. Android will power them down when not in use even if shown as active.
•Monitor your battery milliamp draw in realtime; at idle it should go down as low as 60 ma at times and average about 180-300 ma at idle. Frequent or sustained spikes in the 400-1000+ range indicate excessive cpu activity; find what's doing it. Examine what was recently opened or cache when the drain starts in Running Services in Developer Options.
•Before doing a hard reset try resetting Settings; it's less drastic and time consuming.
•If you do a hard reset be more careful during setup.
Avoid loading a bunch of junk 3rd party apps... keep it clean. Test new 3rd party apps before the reload if you can.
Play with it... observe and play some more... you will find it.
Go through all the settings, poke around, see what's there and learn what it does. Unlike playing in the Windows Registry it's relatively safe to do and fun
Click to expand...
Click to collapse
appreciate the suggestion. Considering I had all the same apps on my note 10 and didn't have similar issue. Am incline to believe issue is related to restoring with smart switch. So will consider doing a reset when I have the time to set everything up manually.
aarick said:
appreciate the suggestion. Considering I had all the same apps on my note 10 and didn't have similar issue. Am incline to believe issue is related to restoring with smart switch. So will consider doing a reset when I have the time to set everything up manually.
Click to expand...
Click to collapse
I don't like smart switch or trust it. This type of Samsung apk has failed me miserably before... bugware.
The 10+ between Goggle, Samsung and carrier apks can be witchy. Lots of junk that does nothing for you and creates conflicts that suck resources/power/internet bandwidth are all too common.
Since each configuration is different you need to play with it.
Without root you lack advanced diagnostic tools which makes it more difficult as if Google wants it that way... effective real time monitors I can use in Windows are completely missing in Android.
Note 20 ultra user here myself, by chance have you got mobile hotspot active? Or the auto hotspot running? Just done a Google search for the service and found this thread. For me turning off the hotspot and auto hotspot stopped the battery drain for this service in its tracks. I have also noticed the phone getting alarmingly hot 50c to 55c when it is switched on and in use, though saying that I'm finding general use makes the phone uncomfortably hot to hold
Im using N20 ultra exynos version and only in the beginning the phone would get hot and battery life is very poor. After about 3-4 weeks im seeing a massive improvement in device performance and battery life. Using ccswe to disable packages. Naptime helping stand by battery drain as well.
blackhawk said:
•Try to find the issues of this load otherwise doing a hard reset may only land you in the same situation.
Lot of junk running... do you need it?
A package blocker like PD MDM can be used to turn off bloatware.
Cloud services and Goggle backup tend to be habitual offenders.
Turn off Google, Samsung and carrier feedback.
I had a lot of trouble with ARcore, disable it if you aren't using augmented reality applications.
Clear data on Goggle Backup Transport, Goggle Framework and google.android.gms.policy.
Clear system cache and log files with a cleaner.
SD Maid does a good job.
I use the old version of Device Care to clean the cache when it used 360° however I block internet access when it runs then package block it because of the Chinese junk in it. It's a good cache cleaner
•Turn off 3rd party power management apks and like Adroid manage its self. Don't set apps to sleep.
•Clear system cache on the boot menu.
In Developer options in Running Services, see what's running. In Stand By Apps all buckets should show as active, if not power management is being used. Android will power them down when not in use even if shown as active.
•Monitor your battery milliamp draw in realtime; at idle it should go down as low as 60 ma at times and average about 180-300 ma at idle. Frequent or sustained spikes in the 400-1000+ range indicate excessive cpu activity; find what's doing it. Examine what was recently opened or cache when the drain starts in Running Services in Developer Options.
•Before doing a hard reset try resetting Settings; it's less drastic and time consuming.
•If you do a hard reset be more careful during setup.
Avoid loading a bunch of junk 3rd party apps... keep it clean. Test new 3rd party apps before the reload if you can.
Play with it... observe and play some more... you will find it.
Go through all the settings, poke around, see what's there and learn what it does. Unlike playing in the Windows Registry it's relatively safe to do and fun
Click to expand...
Click to collapse
Hey! Thank you so much for your tips. Can you please point out a good app for measuring standby power usage? I used to use Gsam Battery Monitor Pro, but that no longer seems to be compatible with my Snapdragon Note 20 Ultra. I don't get accurate reading and it seems the dev has abandoned the app (last update Jan 2020)
xenofont said:
Hey! Thank you so much for your tips. Can you please point out a good app for measuring standby power usage? I used to use Gsam Battery Monitor Pro, but that no longer seems to be compatible with my Snapdragon Note 20 Ultra. I don't get accurate reading and it seems the dev has abandoned the app (last update Jan 2020)
Click to expand...
Click to collapse
Not sure what works with Q; I'm running Pie.
Galaxy's Battery Tracker is useful.
I use the Accubattery overlay sometimes to measure ma but again Q.
DecChek is a useful tool.
Duplicate entry removed.
blackhawk said:
Not sure what works with Q; I'm running Pie.
Galaxy's Battery Tracker is useful.
I use the Accubattery overlay sometimes to measure ma but again Q.
DecChek is a useful tool.
Click to expand...
Click to collapse
have DevCheck installed. Does the Pro version allow to keep it running in the background collecting data for analysis later? I specifically want to understand how much is the drain in standby mode and whether T-mobile 5G could also be the culprit here?
Looks like DevCheck won't collect data silently in the background. So any recommendations for a reliable app to measure standby drain would be very welcome.
xenofont said:
have DevCheck installed. Does the Pro version allow to keep it running in the background collecting data for analysis later? I specifically want to understand how much is the drain in standby mode and whether T-mobile 5G could also be the culprit here?
Click to expand...
Click to collapse
Don't know.
Goggle system apks are more likely to blame.
Try blocking suspects with Karma Firewall and see what it does.
Turn off auto sync for Gmail and look hard at 3rd party apps including Samsung.
xenofont said:
Looks like DevCheck won't collect data silently in the background. So any recommendations for a reliable app to measure standby drain would be very welcome.
Click to expand...
Click to collapse
Use GSAM after enabling permissions via adb. Make sure the app is also not set to be optimized or restricted in background usage .
Limeybastard said:
Use GSAM after enabling permissions via adb. Make sure the app is also not set to be optimized or restricted in background usage .
Click to expand...
Click to collapse
Tried all of that already. Did you get accurate readings?
xenofont said:
Tried all of that already. Did you get accurate readings?
Click to expand...
Click to collapse
Accurate enough for me to determine what is using my battery and make necessary adjustments, yes.
So when you tried that already, what did you come up with? You see MDE Framework in there?
The mde service framework is a system service that enables media playback on Android devices. It provides APIs to support the following media playback operations:
- playing audio and video files
- streaming audio and video content
- recording audio and video
- managing playback queue
- managing media player settings
The mde service framework is implemented in the media server process and uses the MediaDrm API to support DRM-protected content. See also https://grouphowto.com/mde-service-framework/

Question GOS disabled = phone on fire?

I'm on unlocked U1 firmware AVC8 Snapdragon and I've had Game Optimizing Service manually disabled for a while now using Alliance Shield X.
COD Mobile has been running great since there's no throttling and I never get any frame drops, which was not the case when GOS was enabled, even with the alternative performance management on or off, or any type of configuration from Game Booster Plus, so I got rid of it all.
However, with the newest COD update, it feels like my phone is getting dangerously hot when only playing for about 10 minutes.
Are there any tricks or tips to reduce this? I don't want to damage my battery or phone from overheating.
I currently use Thermal Guardian but I don't notice a difference with the temperature, still gets super hot no matter what.
What settings are you guys using to run highly demanding games?
Do you have better luck with GOS enabled or disabled?
I will say the game was running just as smooth and temperatures were actually normal when I was on AVA6 before the March update, with GOS disabled.
I'm considering flashing back to AVA6 so my phone doesn't turn into Portgas D. Ace.
Any thoughts would be great, thanks.
Running like that is extremely hard on the battery, it could significantly decrease it's lifespan. The possibility of thermal damage to the mobo is also increased. Remember flash memory doesn't like high temperatures as far as memory retention goes.
Find the apps responsible and tone them down. It likely could be junk running in the background.
Clear system cache.
Disable global power management.
Disable cloud junk... yeah Google backup and Google Firebase too.
Try temporarily disabling Google play Services.
Rule #1 - if the firmware is running fast, stable (and cool)... let it be. Updates can and do break things. Once I have a phone optimized I don't update it. Security is not an issue, but chasing your own tail after an update/upgrade is an issue and it can be quit time consuming.
blackhawk said:
Running like that is extremely hard on the battery, it could significantly decrease it's lifespan. The possibility of thermal damage to the mobo is also increased. Remember flash memory doesn't like high temperatures as far as memory retention goes.
Find the apps responsible and tone them down. It likely could be junk running in the background.
Clear system cache.
Disable global power management.
Disable cloud junk... yeah Google backup and Google Firebase too.
Try temporarily disabling Google play Services.
Rule #1 - if the firmware is running fast, stable (and cool)... let it be. Updates can and do break things. Once I have a phone optimized I don't update it. Security is not an issue, but chasing your own tail after an update/upgrade is an issue and it can be quit time consuming.
Click to expand...
Click to collapse
Yeah that's what I'm worried about, it definitely doesn't feel safe to continue playing when it gets that hot. I track my apps battery drainage pretty good with Accubattery and everything is normal, I get great battery life no complaint there, it's just the overheat. I set background process limit to 0 from developer setting before I start playing.
How do I disable global power management?
I disable useless stuff and don't let much run in the background so I doubt it's anything like that. I also clear cache partition regularly.
My RAM Plus is set to 1GB and my Processing speed is set Optimized for less heat. I'm not sure what other settings I could tinker with to reduce heat.
If it's running hot it's using battery, lots of it.
I'm running on Pie so no idea about Ram plus, but with 12gb of ram I don't even think about it other than curiosity. Try disabling it.
The power management is found in Device Care.
Lol, it never worked right, why should it now?
Rather handle power hogs on a case by case basis. Trial and error. Don't go too nuts disabling apks. Many apks just sit there and do nothing unless needed. Dozen of small Samsung system apps, be careful with them; dependencies. That may be part of what's going on.
To verify power management's status...
Developer options>standby apps If all buckets are active then global power management is not running. If you can reset the bucket state it's enable. It will cause erratic behaviors. Power management and the bucket crap is a Google brain child. Maybe it's junk, maybe Samsung didn't integrat it right, whatever... it's trouble. Androids will run fine without it.
Only fast charging should be toggle on if you want it. Changing limit background usage in individual app doesn't effect the bucket state and is ok to do if needed.
{
"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"
}
blackhawk said:
Running like that is extremely hard on the battery, it could significantly decrease it's lifespan. The possibility of thermal damage to the mobo is also increased. Remember flash memory doesn't like high temperatures as far as memory retention goes.
Find the apps responsible and tone them down. It likely could be junk running in the background.
Clear system cache.
Disable global power management.
Disable cloud junk... yeah Google backup and Google Firebase too.
Try temporarily disabling Google play Services.
Rule #1 - if the firmware is running fast, stable (and cool)... let it be. Updates can and do break things. Once I have a phone optimized I don't update it. Security is not an issue, but chasing your own tail after an update/upgrade is an issue and it can be quit time consuming.
Click to expand...
Click to collapse
how do one disable google firebase?
thanks
blackhawk said:
If it's running hot it's using battery, lots of it.
I'm running on Pie so no idea about Ram plus, but with 12gb of ram I don't even think about it other than curiosity. Try disabling it.
The power management is found in Device Care.
Lol, it never worked right, why should it now?
Rather handle power hogs on a case by case basis. Trial and error. Don't go too nuts disabling apks. Many apks just sit there and do nothing unless needed. Dozen of small Samsung system apps, be careful with them; dependencies. That may be part of what's going on.
To verify power management's status...
Developer options>standby apps If all buckets are active then global power management is not running. If you can reset the bucket state it's enable. It will cause erratic behaviors. Power management and the bucket crap is a Google brain child. Maybe it's junk, maybe Samsung didn't integrat it right, whatever... it's trouble. Androids will run fine without it.
Only fast charging should be toggle on if you want it. Changing limit background usage in individual app doesn't effect the bucket state and is ok to do if needed.
View attachment 5575279
Click to expand...
Click to collapse
This is really helpful, thank you.
xjust said:
how do one disable google firebase?
thanks
Click to expand...
Click to collapse
In the Google account settings in Android Settings, near or at the bottom. Go through all the Google settings.
Also disable carrier, Samsung, Google and 3rd party app feedfack.
those are already disabled for me, yet firebase still kicks in.
i see it clearly in google play services beta dev options , time and info of what is shared. scary stuff
i thought there is some setting inside myaccount on google that needs attention
btw. whatsapp and telegram works without playservices?
xjust said:
those are already disabled for me, yet firebase still kicks in.
i see it clearly in google play services beta dev options , time and info of what is shared. scary stuff
i thought there is some setting inside myaccount on google that needs attention
btw. whatsapp and telegram works without playservices?
Click to expand...
Click to collapse
Not sure why Firebase is running if disabled. Gookill is a mess... may have something to do with another running Google app like Backup Transport which I also disable.
Get the social media apps off the device. Security risks and really nothing but trouble.
If the site isn't fully functional through the browser only, ditch it.
To get that device to tone down is going to take some effort... and maybe some sacrifices.
it might have something to do with the fact that i logged other android devices on this account or buggy firmware
took out backup transport as well
galaxy s22 is quite a mess so far no deep sleep on wifi, 2-3%/h gms
got better standby on 5 years phones with exactly the same apps/account , without even trying
or maybe nearby device wifi/bt scanning, findmyphone and firebase settings might reset on clearing data/cache for google play services ?
xjust said:
it might have something to do with the fact that i logged other android devices on this account or buggy firmware
took out backup transport as well
galaxy s22 is quite a mess so far no deep sleep on wifi, 2-3%/h gms
got better standby on 5 years phones with exactly the same apps/account , without even trying
Click to expand...
Click to collapse
I always keep wifi disabled. For me it's a huge security risk and I have an unlimited data plan.
Unless I need to get Gmail, Google Play Services is always off. Playstore runs in the background too more so if Google play Services is running.
It took me a while to tone down my N10+, it was a hot running hog. Hard to believe it's the same device/firmware. Setting up my new one was a snap... lessons learned.
i will wait for 1-2 updates from this thing, if nothing works i guess its time to root the main phone again after more than 5 years
xjust said:
i will wait for 1-2 updates from this thing, if nothing works i guess its time to root the main phone again after more than 5 years
Click to expand...
Click to collapse
You're going to have to optimize it. Updates may just make it more complicated to optimize... hard to say. I don't update my N10+'s.
A lot of downsides to rooting Samsung's especially if under warranty. The risk of an expensive brick is not appealing to me and Snapdragon's are notoriously hard to root.
They run very well once optimized but it can be challenging and time consuming.
A package disabler is a good tool for this but not sure if it works on Android 12. It makes it a lot easier, faster and is more flexible than adb edits.
It's very useful for troubleshooting on the fly.
you think there is a way to optimize this to perform similar to my pixel 2 xl ?
smaller and older battery , bigger display resolution, 6 days standby with the same google account, sim card, and software on it.
no matter how many bloat I remove from it. its just not there
I will try disabling gms to see how it performs, but i kind of need it for some of the apps.
xjust said:
you think there is a way to optimize this to perform similar to my pixel 2 xl ?
smaller and older battery , bigger display resolution, 6 days standby with the same google account, sim card, and software on it.
no matter how many bloat I remove from it. its just not there
I will try disabling gms to see how it performs, but i kind of need it for some of the apps.
Click to expand...
Click to collapse
I have about 75 apks blocked and 5 more I toggle on/off if needed.
Disable only apps that need to be disabled especially any Samsung system apps. Many only run when needed and otherwise just sit there doing nothing. Which brings me to dependencies; disabling an app or service can have unintended consequences and be hard to track down. Samsung's have many features and are very customizable, most of those apks reflect and help do that. Lol, don't turn it into a Pixel.
Play Services is a true pain. PD stopped listing it so can't use the widget now to toggle it on/off.
I open settings>apps and punch "play" the search bar to take me to it to turn it off. Note: if Find my Device is set as system Administrator it needs to be deactivated otherwise the Google play Services disable is greyed out.
If you can find a firewall that logs with Android 11/12 it be a useful tool. I use Karma Firewall but it's logging feature only works with Pie. It will still block internet access by apps but you can easily see what's accessing the internet and when. Many don't need access all the time and shouldn't have it. Blocking also prevents forced updates and once a paid app like Accubattery is activated you can hide it from their server. Otherwise if Playstore is disabled it will lose its pro version status. The Google family of apps are wretched power hungry big sisters... they need serious toning down.
Lol, my work arounds are rather extensive and evolved over time. Some require manual input from me and although I don't really think about it much now... it wasn't always this way
However a side benefit is it helps you to develop your troubleshooting skills and tools for doing it. This is also why I don't update... more trouble than it's worth.
looks like a lot of work for the results samsung should've put on from the start
it would've been a lot more sales for them if every process ran was optional for each user to decide what he wants from their 'features'
all of them combined -> dead phone
ps. google play services needs any reboot if i disable/enable it ?
xjust said:
looks like a lot of work for the results samsung should've put on from the start
it would've been a lot more sales for them if every process ran was optional for each user to decide what he wants from their 'features'
all of them combined -> dead phone
ps. google play services needs any reboot if i disable/enable it ?
Click to expand...
Click to collapse
Each user and configuration is different. It's not a boring Apple. That said Samsung's been dropping the ball since the Note 10+, that's been their zenith to date.
Google Android dived down the Apple rabbit hole starting with Android 10, its a mess that gets worse the higher the version. So secure that you can't use it effectively.
Playstore and apps dependent on an active handshake from Playwhore will need a reboot, otherwise no. I reboot every couple days, but rarely use Playstore
Once I initialize the Playstore dependent apps, I firewall block them to keep them locked to their pro versions. Bite me Playstore...
Gmail doesn't care. Of course it's won't autosync but I really don't care about that. I don't want Gookill holding my hand, screw them and their hype.
Funny you mentioned apple.
I moved to android after my iphone 6 couldn't last half a day. had most iphones since the first one
maybe its time to move back
xjust said:
Funny you mentioned apple.
I moved to android after my iphone 6 couldn't last half a day. had most iphones since the first one
maybe its time to move back
Click to expand...
Click to collapse
Android's scoped storage remains a never ending tale of disaster. Google's long standing nose up attitude of expandable storage in favor of their cloud crap only makes matters worse.
Samsung and Google are inept malakas. You don't compete with Apple by mirroring Apple's mistakes...

Categories

Resources