Related
Hi Guys!
Amazingly, I found out yesterday that Google stores our historic location. I'm thinking of disabling it, but afraid to worsen research services and access speed of Google Maps. Let me know if anyone knows this history consists of access to the GPS of the device or the networks? Consumes more battery when enabled?
https://maps.google.com/locationhistory/b/0
You leave enabled or not?
BR4DOKYBrazil said:
Hi Guys!
Amazingly, I found out yesterday that Google stores our historic location. I'm thinking of disabling it, but afraid to worsen research services and access speed of Google Maps. Let me know if anyone knows this history consists of access to the GPS device or the networks? Consumes more battery when enabled?
https://maps.google.com/locationhistory/b/0
You leave enabled or not?
Click to expand...
Click to collapse
Have to check mine....
But I have it ALWAYS off unless I use Maps...
Going to check mine but i dont see it as a draining problem.
BR4DOKYBrazil said:
Hi Guys!
Amazingly, I found out yesterday that Google stores our historic location. I'm thinking of disabling it, but afraid to worsen research services and access speed of Google Maps. Let me know if anyone knows this history consists of access to the GPS of the device or the networks? Consumes more battery when enabled?
https://maps.google.com/locationhistory/b/0
You leave enabled or not?
Click to expand...
Click to collapse
I won't cause you battery consumption too much ( it used to be ) but with the new Google Play Service, it consume battery very low and it's really good if you leave it on.
1. It help you if you get picture and have G+ to make a Story for you.
2. It help you for your favorite location and trip time and traffic time to there.
And lots of other thing that I don't remember now.
Nobleman1 said:
Going to check mine but i dont see it as a draining problem.
Click to expand...
Click to collapse
It's strange to think how he draws our daily route without consuming battery! So I think he does this with the help of cellular networks! If the device used the GPS, we would have a huge battery drain!
dany20mh said:
I won't cause you battery consumption too much ( it used to be ) but with the new Google Play Service, it consume battery very low and it's really good if you leave it on.
1. It help you if you get picture and have G+ to make a Story for you.
2. It help you for your favorite location and trip time and traffic time to there.
And lots of other thing that I don't remember now.
Click to expand...
Click to collapse
Particularly I not use Google Now, much less G +, believe not be advantageous to have this option enabled! I mean, it would not matter to me!
I saw on Google's help page that it uses a considerable amount of data, which can be harmful to the battery!
I disabled both functions and deletes my history. My big fear was disable this function and impair functioning of any device, such as speed of access Maps, which tested it and did not notice any difference!
I believe that this function would be for Google to know what my daily route and enter it into the database of Google Now.
BR4DOKYBrazil said:
It's strange to think how he draws our daily route without consuming battery! So I think he does this with the help of cellular networks! If the device used the GPS, we would have a huge battery drain!
Particularly I not use Google Now, much less G +, believe not be advantageous to have this option enabled! I mean, it would not matter to me!
I saw on Google's help page that it uses a considerable amount of data, which can be harmful to the battery!
I disabled both functions and deletes my history. My big fear was disable this function and impair functioning of any device, such as speed of access Maps, which tested it and did not notice any difference!
I believe that this function would be for Google to know what my daily route and enter it into the database of Google Now.
Click to expand...
Click to collapse
Google Now is very limited in our country, Brazil.
higgs_ said:
Google Now is very limited in our country, Brazil.
Click to expand...
Click to collapse
Exactly! Higgs, you leave these options enabled or disabled?
I leave this option always on! It's helps several services and apps.
Experience tells me that when this location is ON together with Google Now then it is a battery killer!!! Google now is always looking for information to show on the cards in the background and uses fairly more battery.
But of course it can be cool when Google Now tells you witch buses you can catch and how long can you be at home...
SWEagle said:
I leave this option always on! It's helps several services and apps.
Experience tells me that when this location is ON together with Google Now then it is a battery killer!!! Google now is always looking for information to show on the cards in the background and uses fairly more battery.
But of course it can be cool when Google Now tells you witch buses you can catch and how long can you be at home...
Click to expand...
Click to collapse
Exactly!
I disabled these options, given that I do not use Google Now for now! Here in Brazil is very limited!
BR4DOKYBrazil said:
Exactly! Higgs, you leave these options enabled or disabled?
Click to expand...
Click to collapse
Disabled
Hi
First of all thank you Oasis for creating a tool to fix things that shouldn't be broken to begin with! You are an example for a lot of developers :good:
I've read the first couple of posts on the original thread but I still have a few things that are not clear..
The advice of Oasis himself is too hibernate only those apps that misbehave. He states that hibernating apps will also remove them from the memory, which will come with a performance/cpu usage penalty when you want to use them again.
In the video tutorial however Josh greenifies almost every application that doesn't need push notifications.
So this would mean that when I use an application that doesn't have notifications but I open frequently, for example Nu.nl, a dutch newsapp, it will always have to reload the app from scratch instead of loading it from memory?
So baically the best way to use Greenify would be to NOT just greenify most apps, but to use the analyzer frequently and see what's running in the background and greenify those that don't depend on notifications?
Then newsapps that don't push news, image viewers, file managers, system tools like SD Maid and simple games that don't use internet should be ok not being greenified?
Is there no big list available of apps that misbehave or are safe to keep de-greenified?
Thanks in advance for any help on this.
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
marchrius said:
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
Click to expand...
Click to collapse
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
latino147 said:
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
Click to expand...
Click to collapse
"Disable Service" (and "Autostarts") from play store.
marchrius said:
"Disable Service" (and "Autostarts") from play store.
Click to expand...
Click to collapse
Ah, I believed those were two functions withing Greenify I couldn't find
wtf, FB has 62! services! None of them where active though, until you open the app, then it was 3.
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
The only issue with this second method being that you don't always really know what these services do.
latino147 said:
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
Click to expand...
Click to collapse
Exactly. Take google play services for example. If you greenify it, you'll lose gcm and other functions and that's not advisable at all (in fact greenify hides it). But with disable service (and autostarts/system tuner)you can choose what to disable while still mantaining gcm, location services (when needed), sync etc. I can' remember what I did in system tuner regarding gplay services (I followed some tutorial), but with disable service I disabled analyticsservice (this one will reactivate itself unless you do some tweak with system tuner), refreshenabledstateservice, playlogreportingservice, googlehttpservice, playlogbrokerservice, adrequestbrokerservice, gcmschedulerwakeupservice, advertisingidservice, adsmeasurementservice, locationwearablelistenerservice, nlplocationreceiverservice, geocodeservice, dispatchingservice and playlogservice. A reboot is needed. Haven't lost a single function since weeks (gcm, location, autosync and every google app in general are working 100% fine).
Same story with play store. Apps wake it very often, so greenify it does more harm than good. Instead, you can disable pendingnotificationsservice, contentsyncservice and dailyhygiene (and will still be fully functional).
Of course these are little tips to increase performance and battery life even more. I use greenify for 90% and more of apps that "misbehave" and disable service/autostarts/system tuner for the remaining 10% "misbehaving" apps. However, an app "fixed" with such methods will stay cached while with greenify is completely closed (resulting in more cpu/time/battery consumption when loaded again).
The only issue with this second method being that you don't always really know what these services do.
Click to expand...
Click to collapse
Like I already said, for general purposes you'd better simply greenify the "misbehaving" apps. If you use it/it is woken very often, you can consider these methods.
Yes, it's a "trial and error" thing. Unless you're disabling services with self-explainatory names such as "pushservice".
Never installed Facebook official app but I heard many times that is a notorious hogger and takes many personal datas too, for which you can look for xprivacy xposed module as well.
I'll start experimenting with it today :good:
On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
mermaidkiller said:
On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
Click to expand...
Click to collapse
Of course it does. The size/activity in this forum plus frequent mentions in respected publications over many years should offer some clues to its integrity. Whether it is working on your device is a different matter.
Greenify does best on rooted devices as unharnessed ROMs can both undo actions and/or misrepresent status. It's quite possible an app placed in hibernation was later woken via internal trigger that Greenify can not suppress on an unrooted device. In the case of Opera (my preferred browser) there is regular syncing of tabs and downloading of *cough* 'news' if you have those features enabled.
I also question info coming out of the "Android Assistant" app. On my device it claimed all apps had zero CPU...including itself. Also did not display system partitions correctly nor properly detect the sensor suite. Granted I only spent a few minutes poking around. Maybe some switches needed to be thrown.
Finally, you probably don't need Greenify on Oreo as Doze does a find job with power management.
planetera said:
Don't I really need Greenify on oreo? Is Doze on Oreo really that good? Can you confirm please? I've been always using Greenify but if I don't need it on Oreo, I'll remove it
Click to expand...
Click to collapse
Well don't take my word for it. Simply remove all apps from Greenify's hibernation list (hopefully there are not many there), observe device behavior over the next few days then make your own decision.
planetera said:
Well, thanks for information. Just made a quick research and everyone says Greenify is trash on Oreo. So I just uninstalled it. Thanks for heads up. Glad I've seen your comment
Click to expand...
Click to collapse
Trash? Err-no. I have it installed on every one of my devices for valid reasons. Needed for generic power management on Doze capable ROMs? Probably not (and as such serving no purpose). Enjoy your device.
planetera said:
ok, but, when Greenify hibernates an app, you don't get notificaton froms this app, but when Android itself hibernates the app, you still get notifications, how does these two compare?
Click to expand...
Click to collapse
It varies by app, developer approach and user settings. Many apps will experience delayed notifications with Doze while other punch right through. Greenify can be configured to permit notifications but only if the app utilizes GCM (Firebase). Aggressive doze, light hibernation, Xposed framework availability and several other variables contribute to notification behavior. If your head is spinning it should! End users should not need to know the contents of the underwear drawer. Best practice is to simply let Android do its thing without 3rd party tools unless one understands their behavior and application. At one time such tools were needed to achieve acceptable app/device performance and battery life. Not so today. Is such a simplistic solution 'optimal' form an enthusiasts point-of-view? Probably not. It is acceptable/reasonable from an end-user perspective? In most cases 'yes' yielding a good balance of performance and battery life with minimal interaction for those who simply want to enjoy their device vs. manage it. Good luck with whatever direction you choose.
Agree one hundred percent!
Greenify on Oreo is an appendage that is best left out in my opinion, since for most, Oreo itself manages the drain admirably. Though I have it installed, it is more by way of habit than necessity. I have experienced Oreo without Greenify and have no complaints.
Greenify is STILL works.
But its benefit on recent Android versions is not as prominent as on earlier versions.
Coz we already have Doze starting from Marshmallow.
It works for me. I have a samsung tab a 9.7 sm-t550 with an aicp 8.1 rom (lineageos based). Therefore it doesn't have the built-in samsung app device maintenance. I've also discovered a little trick to using greenify that I want to share. I use greenify with another app called shutapp. Shutapp is an app that helps you force stop apps running in the background. Except I don't do that. I use it solely for the purpose of having an accurate number of apps running in the background. Then I open the app to see which ones are running. Next I open greenify and hibernate them. I use this method, because I found that when you force stop the apps they will open back up again. Also, I use the widget from shutapp and not the floating bubble which requires extra permissions granted. The widget does the same thing without the extra permissions. This method I discovered has improved my ram and battery life drastically. I can tell because I use status bar mini pro to monitor my ram speed constantly. And finally I do have Xposed with the donation package of greenify, didn't want to leave that out. Not sure if it makes a difference or not, but wanted to be accurate. That's it, hope that works for somebody else, take care.
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
tnsmani said:
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
Click to expand...
Click to collapse
Greenify works just fine on recent Android builds. It is a tool that can be very beneficial when properly used to produce a specific outcome. That said, it is rarely needed on Android 6+ as doze handles most of the heavy lifting. Enjoy using your device vs trying to fix problems you haven't identified.
My android device is rooted with xposed framework installed and greenify xposed module enabled. What Greenify settings i can enable to make it perform at its best?
Peter770 said:
My android device is rooted with xposed framework installed and greenify xposed module enabled. What Greenify settings i can enable to make it perform at its best?
Click to expand...
Click to collapse
There is no right answer as every device and work flow is unique. That said, Aggressive Doze, Doze on the Go and Wakeup Timer Coalescing are popular choices with limited side effects. If you miss notifications or find your device lagging for a few seconds after wake disable Aggressive Doze. Resist the temptation to add every app/service to Greenify's action list; only target apps that demonstrate bad behaviors. If running Android 6+ doze will take care of most background activity w/o help from Greenify. It's a tool to address specific problems.
What is the difference between the three hibernation modes: default, normal hibernation, deep hibernation (by island)?
Peter770 said:
What is the difference between the three hibernation modes: default, normal hibernation, deep hibernation (by island)?
Click to expand...
Click to collapse
Default is whatever you set as the default in Greenify settings. Normal is what Android uses by default and is adequate for the vast majority of work flows. Deep requires an add on product (Island) and seems to be a solution looking for a problem. You could have discovered all this by searching the thread or reading documentation.
Peter770 said:
What is the difference between the three hibernation modes: default, normal hibernation, deep hibernation (by island)?
Click to expand...
Click to collapse
I absolutely concur to @Davey126's correct statement and recommendation, and I'm unable to add anything substantial. However, I like to share my settings (please refer to attached screenshots), and if interested and required I'll provide information, which of my applications are not greenified.
Regarding your question, at least from my point of view all settings are pretty well explained within Greenify but it's also worth to study the threads by @oasisfeng that are pinned to this Greenify forum.
Thanks, for the screenshots. It was helpful.
I have problem with some apps, like Nine email client, which won't hibernate. Why is that?
Peter770 said:
I have problem with some apps, like Nine email client, which won't hibernate. Why is that?
Click to expand...
Click to collapse
They might be woken up by other apps. If so, you can cut off the links using wakeup tracker option in Greenify's settings.
'Wake-up tracking and cut-off' option is enabled.
Peter770 said:
'Wake-up tracking and cut-off' option is enabled.
Click to expand...
Click to collapse
Merely enabling the option is not enough. You have to manually cut off the trigger. When an app which you greenified wakes up automatically and is shown in Greenify as pending hibernation, if you long press the app, it will show some info like which app or process triggered it and whether it is critical etc. Then you can click the three dot menu button at top right and choose to cut off the trigger using the scissor icon or to ignore its running state. Then it will remain hibernated. Be careful while choosing the options since it may have unwanted side effects. Unless you are sure that you don't absolutely want that app to run in the background and be woken only upon your choosing to open it, don't meddle with the options.
EDIT: I am rusty with Greenify since I haven't installed it for my daily driver and hence the instructions are from memory. There may be some slight differences with what I stated and the actual behaviour.
I don't see these Greenify options but my device is running android 4.4.2 and that might be the reason.
Peter770 said:
I don't see these Greenify options but my device is running android 4.4.2 and that might be the reason.
Click to expand...
Click to collapse
Sorry, I have no idea since I never ran Greenify before MM and that was looong ago.
DB126 said:
Default is whatever you set as the default in Greenify settings. Normal is what Android uses by default and is adequate for the vast majority of work flows. Deep requires an add on product (Island) and seems to be a solution looking for a problem. You could have discovered all this by searching the thread or reading documentation.
Click to expand...
Click to collapse
True man, but i am looking for that documentation for a few days (cause i like to read...); so i ended up here... still... no documentation...
So please, if you are kind, give me a link to Greenify documentation.!
Thanks.!
Robotu said:
True man, but i am looking for that documentation for a few days (cause i like to read...); so i ended up here... still... no documentation...
So please, if you are kind, give me a link to Greenify documentation.!
Thanks.!
Click to expand...
Click to collapse
Greenify is obsolete; power management approaches of the past are no longer relevant. Looking forward is a better time investment. Greenify documentation exists somewhere but I'm not going hunting. Good luck, mate.
DB126 said:
Greenify is obsolete; power management approaches of the past are no longer relevant. Looking forward is a better time investment. Greenify documentation exists somewhere but I'm not going hunting. Good luck, mate.
Click to expand...
Click to collapse
Very true, though it took me a few days to convince myself..., just to remember why i freezed it few years ago...
Thanks...!
I've been removing bloatware that I see using `adb shell pm uninstall -k --user 0 com.the.app`. I think I may have removed "the wrong thing" because now I don't see the Battery setting in the settings list. I also don't see battery saver in the notification menu. There was a useful battery statistics page that showed what apps are using what percentage of the battery. I'd like to get that back.
Can anyone confirm what the package is that provides this functionality? I'll look at how to restore it (since I used the -k option I should be able to get it back).
Thank you.
There are dependencies. Can't recall all for that.
Maybe:
com.sec.android.sdhms
com.google.android.apps.turbo
You really need to know what you're uninstalling before you do it.
It's easier to use a Package Disabler if you want to experiment. It's possible to boot loop the device though if you go too nuts. Some of the "bloatware" just sits there using no resources until you need it and is in fact operationally useful.
blackhawk said:
There are dependencies. Can't recall all for that.
Maybe:
com.sec.android.sdhms
com.google.android.apps.turbo
You really need to know what you're uninstalling before you do it.
It's easier to use a Package Disabler if you want to experiment. It's possible to boot loop the device though if you go too nuts. Some of the "bloatware" just sits there using no resources until you need it and is in fact operationally useful.
Click to expand...
Click to collapse
It's been difficult to find a guide that specifically lists the operationally useful ones to keep. I can only judge them by name and remove based on that. I try to be conservative. But lack of reliable guidance is frustrating.
Googling leads to a ton of different lists of "bloatware", all of them completely wrong. So there's no way for me to know what to trust. I think it would be fantastic if you could provide a list.
I did `cmd package install-existing PACKAGE_NAME` for each of the 2 packages you listed, and it didn't install anything, I think. `pm list` doesn't show them after I run the commands.
Here is something that should be a little more helpful. I generated two lists:
pm list packages -u
pm list packages
I diffed the two and here are the packages that were in the first list but not the second (should represent packages I uninstalled via `adb shell pm uninstall`:
Code:
package:com.samsung.android.fmm
package:com.samsung.android.service.livedrawing
package:com.samsung.android.visionintelligence
package:com.samsung.android.app.clockpack
package:com.samsung.android.app.reminder
package:com.samsung.android.bixbyvision.framework
package:com.samsung.android.app.galaxyfinder
package:com.sec.android.app.samsungapps
package:com.samsung.android.app.notes.addons
package:com.samsung.android.forest
package:com.samsung.android.lool
package:com.samsung.android.app.contacts
package:com.samsung.android.game.gametools
package:com.sec.android.app.myfiles
package:com.samsung.android.bixby.agent.dummy
package:com.samsung.android.app.watchmanagerstub
package:com.sec.android.gallery3d
package:com.sec.android.app.clockpackage
package:com.samsung.android.messaging
package:com.samsung.systemui.bixby2
package:com.samsung.android.authfw
package:com.sec.android.daemonapp
package:com.samsung.android.scloud
package:com.samsung.android.app.dressroom
package:com.samsung.android.beaconmanager
package:com.samsung.android.aremoji
package:com.samsung.android.app.routines
package:com.samsung.storyservice
package:com.samsung.android.bixby.service
package:com.sec.android.mimage.avatarstickers
package:com.samsung.android.arzone
package:com.samsung.android.allshare.service.mediashare
package:com.samsung.android.samsungpassautofill
package:com.samsung.android.ardrawing
package:com.samsung.android.allshare.service.fileshare
package:com.samsung.android.bixby.wakeup
package:com.samsung.android.game.gamehome
package:com.samsung.android.samsungpass
package:com.samsung.android.bixby.agent
package:com.samsung.safetyinformation
package:com.samsung.android.video
package:com.samsung.android.sdk.handwriting
package:com.samsung.android.app.spage
package:com.samsung.android.svoiceime
package:com.samsung.android.calendar
package:com.samsung.app.highlightplayer
package:com.samsung.android.homemode
package:com.samsung.android.app.settings.bixby
package:com.sec.android.easyMover.Agent
If there's anything in here that should be restored (especially if they are related to this battery app issue), please let me know. Thanks again.
Nothing that stands out.
The names can be quit different from their actual function. Worse there can be seemingly unrelated dependencies that will fail if it's needed associated apk is disabled.
Many times the trail/error method is needed to figure out what all a apk or service does.
It takes some time. Each device and user needs are different so each device needs to be customized by the user to work right. One list does not fit all.
I have about 86 packages disabled, about 6 are available immediately by using a PD's interactive widget on/off toggle.
Google play Services and Playstore are normally disabled except when because they're such troublemakers.
Google backup Transport, Framework, Firebase are always disabled.
I also use Karma Firewall to lock down a bunch of apks/services.
My stock N10+/Pie gets 7-11%@hr SOT now. At night using tap on AOD with phone, texting and internet enabled it uses >.5% battery per hour.
Current OS load is over a year old, still fast and very stable with little maintenance needed.
Took over a year for me to fully optimize it.
It's a learning process, but well worth it.
Could you provide some information on how you disable the items in your list? For example I google for disabling Firebase but nothing comes up.
I'm looking at adb logcat to see if something jumps out at me but so far most of it seems useless.
Google Firebase is under Settings, Google account. It collects all kinds of your usage data ie music, playlists, vids etc on your dime, allegedly for faster indexing.
This Disabler works:
Home - Package Disabler
The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.
www.packagedisabler.com
blackhawk said:
Google Firebase is under Settings, Google account. It collects all kinds of your usage data ie music, playlists, vids etc on your dime, allegedly for faster indexing.
This Disabler works:
Home - Package Disabler
The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.
www.packagedisabler.com
Click to expand...
Click to collapse
Thank you! How reliable is the disable bloat feature in the dashboard for Package Disabler?
Android.Addiction said:
Thank you! How reliable is the disable bloat feature in the dashboard for Package Disabler?
Click to expand...
Click to collapse
What do you mean exactly?
It disables most.
I tried generating a current list but I'm having problems similar to yours
I need to play with it a bit.
Ok I made some progress on this issue. The app that I removed that caused this is:
Code:
com.samsung.android.lool
This is listed in this repo: https://github.com/khlam/debloat-samsung-android
The repository has this to say about the "Device Care" app:
The Device Care app will be disabled and will not appear in settings. This includes Samsung's app sleeper and battery monitor. There is evidence the Device Care app created by the Chinese company Qihoo 360 sends data to China domains over HTTP.
Click to expand...
Click to collapse
Is there any other app I can use to analyze battery usage of applications on my tablet?
Android.Addiction said:
Ok I made some progress on this issue. The app that I removed that caused this is:
Code:
com.samsung.android.lool
This is listed in this repo: https://github.com/khlam/debloat-samsung-android
The repository has this to say about the "Device Care" app:
Is there any other app I can use to analyze battery usage of applications on my tablet?
Click to expand...
Click to collapse
Device Care is a useful app. I use the original factory load version that came with my 10+.
It uses the suspected CCP spyware 360° cleaning app, which actually does a very good job. I simply firewall block it's untrustworthy a$$
Latter Device Care versions aren't as useful but still have needed settings toggles. After you set them you can disable it. I recommend you not use battery optimization or and of those toggles, only toggle on fast charging. This app doesn't use a lot of power as best I can tell as long as the battery optimizing toggles aren't enabled.
blackhawk said:
Device Care is a useful app. I use the original factory load version that came with my 10+.
It uses the suspected CCP spyware 360° cleaning app, which actually does a very good job. I simply firewall block it's untrustworthy a$$
Latter Device Care versions aren't as useful but still have needed settings toggles. After you set them you can disable it. I recommend you not use battery optimization or and of those toggles, only toggle on fast charging. This app doesn't use a lot of power as best I can tell as long as the battery optimizing toggles aren't enabled.
Click to expand...
Click to collapse
I instead went with a separate app, AccuBattery, to monitor app battery usage. That way I'm not relying on potential malware from Samsung
Android.Addiction said:
I instead went with a separate app, AccuBattery, to monitor app battery usage. That way I'm not relying on potential malware from Samsung
Click to expand...
Click to collapse
Accubattery can't do what Device Care does.
I use Accubattery too.
The newer versions dropped 360° so it's gone.
360° deep cleaning actually works very well and is probably no threat when firewall blocked. Which is why I still run the factory load version.
blackhawk said:
Accubattery can't do what Device Care does.
I use Accubattery too.
The newer versions dropped 360° so it's gone.
360° deep cleaning actually works very well and is probably no threat when firewall blocked. Which is why I still run the factory load version.
Click to expand...
Click to collapse
What is 360?
Android.Addiction said:
What is 360?
Click to expand...
Click to collapse
I still don't know what it actually is.
Android.Addiction said:
I still don't know what it actually is.
Click to expand...
Click to collapse
It's a cleaning app Samsung use to license to use in Device Care. Unfortunately the Chinese company that owned it was data mining user data so Samsung ditched them.
So I just firewall block it... it works well otherwise.
blackhawk said:
Accubattery can't do what Device Care does.
Click to expand...
Click to collapse
What exactly does Device Care (or 360) do that Accubattery doesn't? I'm trying to decide if I want to re-enable it, and any details you provide here will help me understand a bit better to make that decision. Thanks for everything so far.
Android.Addiction said:
What exactly does Device Care (or 360) do that Accubattery doesn't? I'm trying to decide if I want to re-enable it, and any details you provide here will help me understand a bit better to make that decision. Thanks for everything so far.
Click to expand...
Click to collapse
The old Device Care with 360° effectively cleans system logs files and other hidden caches.
Cleans some things SD Maid doesn't seem to touch. If you load the old version simply block it with Karma Firewall which uses almost no battery, ad free.
Battery stats are much more detailed in Device Care. It also has easy power mode settings... play with it. No harm, no foul.