Related
After about 6 months using my Incredible, today it's gotten severely slow! I noticed that it was taking 20-30 seconds to bring up my email, delete an email, etc. Then I noticed that the Google Maps update was still running from yesterday. Updates have always been reasonable fast.
I stopped the update and attempted to uninstall Google Maps thinking that I could reinstall it later. The uninstall ran on too and never completed so I stopped that as well. As a test I'm now running a Lookout "security scan" which normally runs about a minute or so. This time it's about 75% done and it's been running for 30 minutes.
What I've done so far is stop apps that I didn't need running and reboot. No change.
My QUESTION is, is there anyway that I can determine what's eating my processor cycles or any other way to determine what's going on? I'm assuming that's what's making it SO SLOW.
Have you just tried to reboot it? That can usually get the phone back to normal. If it keeps happening is when you want to look into other possible reasons it may be happening.
I have a rooted incredible and using Warm Z TwoPointTwo and I was using wave launcher and that caused my phone to become useless cuz it was too slow.. so check if there is an application like it... another is launch -X pro can cause that too..
i think that the gingerbread mods for Myns have slowed it down a hair too.. i just did it but i will keep an eye on it.
I really like the look though for sure!
SD card have ample free space?
Sent from my ADR6300 using XDA Premium App
jblackfish said:
After about 6 months using my Incredible, today it's gotten severely slow! I noticed that it was taking 20-30 seconds to bring up my email, delete an email, etc. Then I noticed that the Google Maps update was still running from yesterday. Updates have always been reasonable fast.
I stopped the update and attempted to uninstall Google Maps thinking that I could reinstall it later. The uninstall ran on too and never completed so I stopped that as well. As a test I'm now running a Lookout "security scan" which normally runs about a minute or so. This time it's about 75% done and it's been running for 30 minutes.
What I've done so far is stop apps that I didn't need running and reboot. No change.
My QUESTION is, is there anyway that I can determine what's eating my processor cycles or any other way to determine what's going on? I'm assuming that's what's making it SO SLOW.
Click to expand...
Click to collapse
Did you install anything before it seemed to get slow? Are you running a stock rom, rooted, etc.? Just would help to know the basics.
Sometimes random apps will do this to my phone. Usually when it does I haven't rebooted my phone in several weeks so I just reboot it to start it out clean and the lag goes away.
If you download watchdog you'll be able to see what's eating up your resources, but I wouldn't suggest you running it 24/7 because it eats up a decent amount of resources on its own.
Hi.!
I have a disturbing problem with my gnex.
Running Xylon 14 stable with franco kernel. I always use latest version of everything.
But my problem comes from past time and still continues.
When i install an app, from market, from blackmkrt or as an apk doesnt matter my phone frozes for 30 secs.
I cant do anything while doing that. Then it comes back to normal.
Its really annoying cuz sometimes play store crashes because of that, my navbar goes then comes back.
i have over 140 apps installed and i always flash roms wiping data and cache. always clean install.
but restoring apps from titanium backup.
When i do clean flash, if i install anything from anywhere, nothing happens, my phone acts normal.
Is this related to titanium backup? or Rom problem (Which i dont think so) or Related to so many apps installed.
Thank you..
Probably one of the apps u r restoring using Titanium Backup is giving u problem. I would do a clean install and download/install the apps one by one instead of restoring them with titanium backup. I know is painful doing this for 140+ apps but I don't think u use all of them.
Sent from my Galaxy Nexus using xda premium
jjjameson said:
Hi.!
I have a disturbing problem with my gnex.
Running Xylon 14 stable with franco kernel. I always use latest version of everything.
But my problem comes from past time and still continues.
When i install an app, from market, from blackmkrt or as an apk doesnt matter my phone frozes for 30 secs.
I cant do anything while doing that. Then it comes back to normal.
Its really annoying cuz sometimes play store crashes because of that, my navbar goes then comes back.
i have over 140 apps installed and i always flash roms wiping data and cache. always clean install.
but restoring apps from titanium backup.
When i do clean flash, if i install anything from anywhere, nothing happens, my phone acts normal.
Is this related to titanium backup? or Rom problem (Which i dont think so) or Related to so many apps installed.
Thank you..
Click to expand...
Click to collapse
I'm having the same issue, not quite as bad as 30 secs, but my phone will practically lock up when installing or uninstalling apps, or just any general file operation. I am also using xylon (16-1, also tried 19 and tried xenonhd latest). Tried multiple kernels doesn't seem to make any difference.
If you haven't already tried using Lagfix from the market, that might just fix your problem, I think it worked for me a couple times but I'm not 100%. Now it doesn't see to help at all.
Yesterday I decided to wipe everything and install from scratch, installing all apps from the market, and a few manually, it seemed better at first. Then I restored a few remaining apps with Titanium Backup (i needed to restore the data and app). Not sure if thats made it worse or not but it still hangs when installing/uninstalling apps. Very frustrating, after I spent probably over 4 hours (I have a lot of apps).
Seems like the CPU clock gets maxed out when this happens, but I can't see high usage from any apps in particular... I know this is not normal behavior because last week my phone was running perfectly with same rom and kernel, it would not lag/freeze when doing any file transfers or installs etc..
Wish I could pinpoint this issue its really driving me nuts. However I think you should definitely try Lagfix it might fix your issue.
i had the same thing happening on every rom/ kernel i tried .
and i also noticed that the cpu usage spikes to 100% for the time the device locks up.
i also noticed unusual high cpu usage whenever i/o was happening.
so i finally returned to stock and have not had any lock ups yet and the cpu never goes to 100% during i/o. its also high, but not maxed out.
i also noticed this on other devices with custom roms which makes me believe that it has to do with some stuff that was changed in the rom or kernel.
i will stay on stock for some time to see if the lockup will come back because everybody tells me it will... so i will report back in a couple of days and let you know if it started to lag.
oh and i restored all apps with titan backup like i had them in the custom rom so this can not be the issue.
Sent from my Galaxy Nexus using xda premium
grognaz said:
i had the same thing happening on every rom/ kernel i tried .
and i also noticed that the cpu usage spikes to 100% for the time the device locks up.
i also noticed unusual high cpu usage whenever i/o was happening.
so i finally returned to stock and have not had any lock ups yet and the cpu never goes to 100% during i/o. its also high, but not maxed out.
i also noticed this on other devices with custom roms which makes me believe that it has to do with some stuff that was changed in the rom or kernel.
i will stay on stock for some time to see if the lockup will come back because everybody tells me it will... so i will report back in a couple of days and let you know if it started to lag.
oh and i restored all apps with titan backup like i had them in the custom rom so this can not be the issue.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I can confirm the high CPU usage during the heavy i/o was happening. My phone would run cpu clock maxed, and then gets hot. One of the processes using a lot of CPU was System or System UI. I was also getting system ui crashes, without a error message though, it would just close and restart system UI by itself. When I checked battery stats showed Android_System which is System UI I believe.
I'm going to try again from scratch with a custom rom (one that was at one point not giving me problems xylon 16-1). This time i'm going to wipe everything including the internal SD.
AFAIK dalvik cache is generating right after installing app. Its like boot time increases after wiping dalvik cache.
And if so - its might be CPU greedy =.)
vvorth said:
AFAIK dalvik cache is generating right after installing app. Its like boot time increases after wiping dalvik cache.
And if so - its might be CPU greedy =.)
Click to expand...
Click to collapse
I see, maybe there is something gone wrong with the dalvik cache or something (I have no clue about dalvik cache) Is there perhaps an upper limit to the number of apps where the dalvik cache gets full or too large that would cause this issue? I've wiped cache and dalvik cache quite often (when trying other kernels recently) and it didn't seem to help the issue.
I went ahead and wiped everything went back to stock 4.2.1, installed 50+ apps via the market, phone barely got warm, and everything continued smoothly no freezing or high cpu usage during this (normally have 175+ apps installed).
I will test restoring app my other apps via Titanium Backup on the stock ROM and see what happens. Will report back...
I don't think I will stay on the stock rom for much longer, there are quite a few tweaks in these custom roms that I'm missing. But I will keep testing for now.
Thanks,
EDIT: Restored my missing apps with titanium (total 104 user apps) and everything is still smooth, including when installing and uninstalling apps from the play store etc... Will wait and see if that changes though.
quick_ said:
I see, maybe there is something gone wrong with the dalvik cache or something (I have no clue about dalvik cache) Is there perhaps an upper limit to the number of apps where the dalvik cache gets full or too large that would cause this issue? I've wiped cache and dalvik cache quite often (when trying other kernels recently) and it didn't seem to help the issue.
I went ahead and wiped everything went back to stock 4.2.1, installed 50+ apps via the market, phone barely got warm, and everything continued smoothly no freezing or high cpu usage during this (normally have 175+ apps installed).
I will test restoring app my other apps via Titanium Backup on the stock ROM and see what happens. Will report back...
I don't think I will stay on the stock rom for much longer, there are quite a few tweaks in these custom roms that I'm missing. But I will keep testing for now.
Thanks,
EDIT: Restored my missing apps with titanium (total 104 user apps) and everything is still smooth, including when installing and uninstalling apps from the play store etc... Will wait and see if that changes though.
Click to expand...
Click to collapse
Humm, I have the same terrible performance from Play Store. XENON HD Stable 4.0 and Franco kernel r364, although the problem goes back through many prior versions of this ROM and kernel.
I have almost 300 apps on the device, and Play Store seems to be the only one that kills the system. I'm also running the "seeder" app, which helped eliminate all other lag on the device FWIW.
A solution would be awesome, but for now, I just walk away from my comm dev and interact with the spousal unit. Strange, I know.
was1958 said:
Humm, I have the same terrible performance from Play Store. XENON HD Stable 4.0 and Franco kernel r364, although the problem goes back through many prior versions of this ROM and kernel.
I have almost 300 apps on the device, and Play Store seems to be the only one that kills the system. I'm also running the "seeder" app, which helped eliminate all other lag on the device FWIW.
A solution would be awesome, but for now, I just walk away from my comm dev and interact with the spousal unit. Strange, I know.
Click to expand...
Click to collapse
I should have updated earlier.
What I did was wipe everything including internal sd, then installed paranoid android rom, installed ak.Dummy kernel 673. Let the play store restore all my apps. Everything was smooth as hell almost 24hrs running so perfectly I was even running max cpu at 920mhz, everything was perfect until restoring some last remaining apps with titanium backup.
Soon as I did that lag and freezing has come back. Lag is so bad at times system ui force closes.
Edit: I just uninstalled all the apps that I had restored with titanium backup. So far the lag is still there somewhat.
This is really driving me fn nuts. If I wasn't so used to a lot of these custom rom features/tweaks, I would just stick with the stock 4.2.1 rom. That was the only rom that didn't eventually had even after restoring apps with titanium backup.
Anyway IMO there is something funky going on when restoring apps with titanium backup. That's when it all starts lagging again for me anyway. Device starts to get hot AGAIN (even though I have cpu still set to 920mhz max).
I've had this same issue with the following ROMs:
Xenon hd (latest)
Xylon (16-19 builds)
Paranoid android (latest)
So it doesn't seem to be rom specific...
I'm going to start over again for the millionth time (feels like) and wipe everything, and install paranoid android again but this time avoid titanium backup, but even going to install it.
I will report back.
Re: How do I fix this? Screen issue
quick_ said:
I should have updated earlier.
What I did was wipe everything including internal sd, then installed paranoid android rom, installed ak.Dummy kernel 673. Let the play store restore all my apps. Everything was smooth as hell almost 24hrs running so perfectly I was even running max cpu at 920mhz, everything was perfect until restoring some last remaining apps with titanium backup.
Soon as I did that lag and freezing has come back. Lag is so bad at times system ui force closes.
Edit: I just uninstalled all the apps that I had restored with titanium backup. So far the lag is still there somewhat.
This is really driving me fn nuts. If I wasn't so used to a lot of these custom rom features/tweaks, I would just stick with the stock 4.2.1 rom. That was the only rom that didn't eventually had even after restoring apps with titanium backup.
Anyway IMO there is something funky going on when restoring apps with titanium backup. That's when it all starts lagging again for me anyway. Device starts to get hot AGAIN (even though I have cpu still set to 920mhz max).
I've had this same issue with the following ROMs:
Xenon hd (latest)
Xylon (16-19 builds)
Paranoid android (latest)
So it doesn't seem to be rom specific...
I'm going to start over again for the millionth time (feels like) and wipe everything, and install paranoid android again but this time avoid titanium backup, but even going to install it.
I will report back.
Click to expand...
Click to collapse
Interesting. I use CWM for the ROM manager and Titanium to restore the apps. Haven't seen the lag problem, except after dirty flashes of XENON. After wiping, the lags went away, but only when using seeder (the free version from these forums).
For a while, I thought it was Facebook causing the lag. Every time I'd check OS Monitor, Facebook was running the CPU's at 40% or more. I backed off the refresh interval to one hour. Its now behaving normally but I'm not convinced that it caused the lags.
I concur: something is causing the lags. Maybe the community can piece together the common elements to isolate it. For now, my phone is running better than new and I'm really happy with the performance.
was1958 said:
Interesting. I use CWM for the ROM manager and Titanium to restore the apps. Haven't seen the lag problem, except after dirty flashes of XENON. After wiping, the lags went away, but only when using seeder (the free version from these forums).
For a while, I thought it was Facebook causing the lag. Every time I'd check OS Monitor, Facebook was running the CPU's at 40% or more. I backed off the refresh interval to one hour. Its now behaving normally but I'm not convinced that it caused the lags.
I concur: something is causing the lags. Maybe the community can piece together the common elements to isolate it. For now, my phone is running better than new and I'm really happy with the performance.
Click to expand...
Click to collapse
I will definitely give this "seeder" app a try this is the first I've heard about it. Thanks!
FWIW, I did have facebook installed but I had all refresh/notifications set to manual and/or off, never did see any high CPU usage with the facebook app in all the times I've been monitoring for this issue.
Thanks again,
You can get the entropy seeder app for free in the forum.
Galaxy Nexus (toro) XENON HD Stable-4.0 Franco kernel r364
was1958 said:
You can get the entropy seeder app for free in the forum.
Galaxy Nexus (toro) XENON HD Stable-4.0 Franco kernel r364
Click to expand...
Click to collapse
Thanks!
I've yet to try it thought, been trying to isolate the cause of this lag...which I might have found, sort of...
After wiping and installing everything from scratch 3 more times, it seems like if I go over 100 apps (number might be lower) that seems to the the trigger point. Once I hit this unknown number of apps installed its like a light switch gets flipped and everything goes to @#[email protected]#$, and lag starts.
This last time I only installed the most essential apps (which still was total of 60-70 lol) So far no lag at all, everything is running great, no lag when installing or uninstalling apps on the market etc..
Running as smooth as it does after a complete wipe and first install. So that's my thought for now, no idea what the actually issue is or how to fix it, other than staying below a certain number of apps. This seems to fix this issue for me at least for now anyway.
Few other things to note, I didn't let the market restore my apps automatically, I installed them one by one... Also did not install or use titanium backup, which I was suspecting as the cause initially, but it was just after restoring all my apps with TB, I went over this "X" number of apps installed that would cause the lag to begin.
Will update if anything changes.
i have exactly the same behavior...
UPDATE: Wanted to add from personal experience that these tricks all work on 4.4 KitKat ROMs. This information isn't stale
This guide should work for any Android phone running any ROM. (Though you do have to be rooted for most of these options. Nothing is THAT simple!)
The goal is to reduce your battery drain when your phone is idle. Nothing in this guide will improve your battery life when the phone is in use. But it will keep the battery from draining quickly (actually it will nearly keep it from draining at all) when the screen it off and the phone is not in use. And the battery savings can be extreme! As I write this guide my phone it has been 4 days, 15 hours, and 9 minutes since I last unplugged my Galaxy S4. I have 33% battery life remaining. You can have this too!
These fixes are not your typical "Lower screen brightness and delete carreir bloatware and disable auto syncing" tips. (Though all that stuff is still a good idea)
You can try all of these techniques or just some of them. Some of them will break features of your phone and might not be good options for you. Only you can decide if these fixes are right for you.
Special thanks for Mike216 and Penko956 for the endless research they did Greenifying, freezing, and disabling they did on just about every system and app on thier phone to see what all could be disabled. And to Torbitege who initially helped figure all this out with me for the HTC Sensation.
First off, what's using your battery?
If you're not already familiar with Better Battery Stats, fix that about yourself. Download it. Use it. Love it.
This app will run in the background constantly monitoring what's using your system resources 24 hours a day. It will tell you what apps are causing wakelocks, which are waking the device, etc etc etc.
The app won't do anything to help your battery life. But it will give you the information you need to adjust problematic apps.
Wakelocks and Battery Drain caused by Google Services
The battery saving impact is major.
This is my personal favorite battery saving technique. But it's not right for everyone, so read thoroughly.
Basically Google thinks your phone belongs to Google. Google Services runs A LOT even when you're not using the phone. This causes a ton of wakelocks and wake ups that use battery. I hate that. So I stopped it with a simple mod to the Google Services Framework.
Here's how....
This is a good old fashioned dirty fix, as it breaks some things. Most push notifications WILL NOT WORK AFTER DOING THIS!!!!! So this is not for everyone!!!! You've been warned. Please don't complain later in the thread that you aren't getting new mail or Twitter or whatever notifications after doing this. You're being told up front they will probably not work.
GTalk and GoogleNow (and maybe a few other things) will not work after doing this. Push notifications for any Google apps will also not work. They are casualties of the dirty fix. But if you're like me and never use GTalk or GNow this will help. Some other Google services might not work after this either. But if you're like me and the only Google service you use is the Play Store app, this will not affect you adversely. (Gmail and Google Maps run independantly of the Google Services framework and are not affected at all by this.)
Use this version of the fix for older Google Service Framework installs. You will know if you have a newer version if doing this install doesnt' prevent your wifi and data icons from turning blue (or whatever color your theme uses). If they turn blue, use the newer version below....
You need to download System Tuner from Google Play. The app will tell you to get Android Tuner instead. Don't do it. It doesn't have what you need. The icon is a blue suitcase with tools on it. Thats' the one you want.
First I froze GTalk and Gnow (Google Search). And no, you can't just freeze those two apps without touching the GSF. The GSF will still create wakelocks when trying to activate them even if they are not there. So you have to modify the GSF as well.
Go to System Tuner and select "Start Ups".
Then pick the Google Services Framework from the list and open it. You shoudl see a list of services.
Uncheck the things on the list below. (Basicall anything with GTalk or Checkin in the title)
gtalkservice.diagnostits.gtalkdiagnostics
gtalkservice.connection autherrordialog
talk.talkprovider
checkin.checinservices$reciever
checkin.checkinservices$triggerreciever
checkin.eventlogservices$receiver
gtalkservice.diagnostics.gtalkdiagnosticsbroadcast reciever
gtalkservice.serviceautostarter
gtalkservices.datamessagereciever
gtalkservice.sendxmppreciever
gtalkservices.packageinstalledreciever
gtalkservice.xmppendpointreciever
checkin.evenlogservice
gtalkservice.service.stalkservice
gtalkservice.pushmessagingregistar
You can freeze the GSF entirely with 1 easy step and that will also kill the wakelocks. But the Play Store becomes another casualty if you do that. Disabling the events above will stop the Google Services wakelocks dead in their tracks, and allow the Play Store to continue working. If you want to go that route you can do it but you'd have to unfreeze the GSF everytime you wanted to update an app.
Newer version if you have updated Google Service Framework.
Freeze the Google Services Framework entirely.
Profit.
Note: I haven't personally tried this and can't attest to it's viability to drawbacks. It was suggested by other members in this thread and confirmed to be working by several other people. Your miliage may vary.
One little quirk with both of the above versions is that when you turn on wifi or mobile data, the signal bars don't turn colors. They stay gray because you aren't connecting to the google servers anymore. (They normally change color to indicate that you are connected to the Google servers). After 1 day I stopped noticing they didn't change colors. Now it looks weird to me when I see them colored.
I highly recommend making a Nandroid backup before trying any of this. Once you go that, go nuts! You can't hurt too much when messing with the GSF because it will just shut down google elements. Worst case, you can always just reactivate everything, reboot, and it'll all work like it did before you messed with it. But if you accidentally disable Android System instead of Google Services, you will probably kill your ROM. So back a backup first.
And severely worst case, if you totally louse up your ROM, just restore the Nandroid and it'll all be back to normal in a flash. (Get it? In a 'flash'...haha I crack myself up)
The Greenify App Sollution
The battery saving impact is moderate.
This is one that you're just silly not to be doing.
Get the Greenify App from The Play Store
There is a free version. But its freakin' awesome so buy the donate version. It's $3 and the developer has more than earned it for the way he's making your phone awesome. (The donate version also includes some special experimental features. Read all about it. Do NOT just get the donate version. You need the free version too.)
This app basically lets your freeze any user app when you're not actively using it. And unfreeze it automatically when you want to open it again.
So if you have an app that likes to wake your device and run itself when you're not using the phone, you can just Greenify it and it will be prevented from using any system resources when you're not actively using the app.
You don't want to Greenify everything. Some apps need to run 24/7 like your messaing app, your phone app, etc. If you Greenify those you won't get messages or calls. The app is incredibly simple to us. You just select the app that's causing trouble and tell Greenify to 'go'. And it does the rest. It's just as easy to un-greenify an app if you greenify something you shouldn't have.
Not every app on your phone needs to be Greenified. Most apps behave themselves. Only do this to the ones that are showing as causing wakes or alarms or wakelocks in a battery monitor like Better Battery Stats.
Two that I will suggest for everyone to start with are Google Maps and T Mobile's My Account app. Both of these love to run when the phone is alseep.
If for whatever reason Greenify those apps hinders the way you use your phone, just ungreenify them! Simple as that.
Google Play Services and You
The battery saving impact is noticable.
Google Play Services wakes the phone a lot. It also does a lot. Read more about what all Google Play Services does here.
You have two options for this one. The first option is the nuclear option. Freeze Google Play Services outright. It will never bother you, but it might break some usefulness of other google apps.
The second option, thanks to XDA Member Karpfenhai , is to disable only certain aspects of the Google Play Services. This one uses the same technique mentioned above in the Google Services Framework Section, just different services to disable. (Thanks to Perseus71 for making me aware of this one and asking that it be included!) THIS HAS BEEN RECENTLY UPDATED
NEW PROBLEM AS OF MARCH 2015
The battery saving potential is ABSOLUTELY REQUIRED!
Since Google updated Play Services all hell has broken loose on custom roms. You get a persistent and unkillable wakelock for SystemUpdateManager.
The battery drain is horrendous. Your phone is awake and active 100% of the time.
This affects GPS version 7.0.97
I fixed this by going to the permissions manager (built into many aosp roms. If not available in your rom, consult yoir rom thread for ways to alter permissions) and disabling the permission in Google Play Services for "wake" and "keep awake".
Note: Some phones only show "keep awake". Just do that one if that is the case.
The problem is that on custom roms no ota is available. But Google tries to get it anyway. When it fails it doesn't shut down. It just keeps trying.
If the permissions method doesn't work, try this...
http://forum.xda-developers.com/general/general/fix-fix-systemupdateservice-wakelock-t3060548
I
Just so you don't think I'm kidding around when I say you can severely increase your battery drain when idle, take a look at tehse screen shots from my Galaxy S4.
My specific set up is running CyanogenMod 10.1 nightlies with ChronicKernal. I haven't been using my phone much over the past 4 days. I have a total of 2 hours and 34 minutes screen on time and 40 minutes of phone calls during that period. So this is admittedly very light usage. But that's perfect to show you that these techniques really work to minimize battery drain when the phone is idle. And I promise you that your results will vary based on your ROM and Kernel.
This won't make the battery last longer during use. The screen will still burn a lot of battery and the cell radio does too. But if you want to make sure your phone will be charged when you need it without you having to carry a charger with you everywhere you go, these are the mods for you.
As you can see from these screen shots I am at 4 days, 16 hours, 50 minutes since unplugging. I have 31% battery left. (That's what the 31 in the upper left corner is. Thats' from an app called Big Battery Notifier. Its free on Play.)
The other screenshot is from Better Battery Stats showing my Alarms screen. Alarms are loosely the same as wakes. Everytime an app wakes the device (not neccessarily turning the screen on) it will record an alarm. If you look at your BBS alarms screen without these modifications I bet you see a lot more alarms than you see here, and keep in mind that mine screen show is showing 4 and a half days worth. Each one of those represents an app or service waking the device and using battery.
If the written instructions somehow baffle you, here's a video of the whole thing!
http://www.youtube.com/watch?v=cUBpOl77Tm4
This will show you step by step how to do all of this.
Thanks to XDA Member Chaitanyapatel8880 for his work in putting this video together
Just a note. If you convert Google Play Services to a User App (TB), you can then Greenify (free ver.) it. This works very well and does not affect other functions that may rely on that app.
I also Greenify Maps and Google Search. Two more heavy drainers. Convert to User App first.
*Note: You must use Greenify v1.82 to Hibernate Google Play Services! Search this thread for links to it.
Fwiw, my sleep drainage is 0.3 - 0.4%hr, with wifi on 24/7.
I get either 7-8 days standby, or so far, 5.5 days with 3.5 hours screen time, or likely 6-7hrs screen time single day. Screen shots are in my posts.
I would argue too that these settings/tweaks do indeed increase your battery time, since while sleeping, the battery is draining at a much lower rate, therefore keeping more juice for live time use.
Although you and I don't use all of the same "tweaking" programs, we do seem to be on the same mission. Better battery life! :good:
Pinan said:
Just a note. If you convert Google Play Services to a User App (TB), you can then Greenify (free ver.) it. This works very well and does not affect other functions that may rely on that app.
I also Greenify Maps and Google Search. Two more heavy drainers. Convert to User App first.
Fwiw, my sleep drainage is 0.3 - 0.4%hr, with wifi on 24/7.
I get either 7-8 days standby, or so far, 5.5 days with 3.5 hours screen time, or likely 6-7hrs screen time single day. Screen shots are in my posts.
I would argue too that these settings/tweaks do indeed increase your battery time, since while sleeping, the battery is draining at a much lower rate, therefore keeping more juice for live time use.
Although you and I don't use all of the same "tweaking" programs, we do seem to be on the same mission. Better battery life! :good:
Click to expand...
Click to collapse
I like your way of dealing with Google play services. I'll change the op later.
That doesn't break function of the play services to run as a user app?
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
I like your way of dealing with Google play services. I'll change the op later.
That doesn't break function of the play services to run as a user app?
Click to expand...
Click to collapse
I have not noticed any dysfunction, though there are likely some things I don't use. But for me it's been completely functional.
Besides, if I froze it, I'd have none of it's functions at all.
Pinan said:
Just a note. If you convert Google Play Services to a User App (TB), you can then Greenify (free ver.) it. This works very well and does not affect other functions that may rely on that app.
I also Greenify Maps and Google Search. Two more heavy drainers. Convert to User App first.
Fwiw, my sleep drainage is 0.3 - 0.4%hr, with wifi on 24/7.
I get either 7-8 days standby, or so far, 5.5 days with 3.5 hours screen time, or likely 6-7hrs screen time single day. Screen shots are in my posts.
I would argue too that these settings/tweaks do indeed increase your battery time, since while sleeping, the battery is draining at a much lower rate, therefore keeping more juice for live time use.
Although you and I don't use all of the same "tweaking" programs, we do seem to be on the same mission. Better battery life! :good:
Click to expand...
Click to collapse
How do I convert those services to user apps?
Sent from my SGH-M919 using xda app-developers app
rodny23 said:
How do I convert those services to user apps?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Titanium Backup will do it, I think you need the paid version though.
/System/App Mover is also good app for doing it. It's free on Google Play.
Dang right now Google services is at 41%
Sent from my SGH-M919 using xda app-developers app
Skipjacks said:
Titanium Backup will do it, I think you need the paid version though.
Click to expand...
Click to collapse
Yup. I think you're right.
Something disabled notifications for instagram, etc.
Sent from my SGH-M919 using xda app-developers app
kevinrubio1 said:
Something disabled notifications for instagram, etc.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Did you Greenify Instragram? If yes, that explains why you aren't getting notifications.
lordcheeto03 said:
Did you Greenify Instragram? If yes, that explains why you aren't getting notifications.
Click to expand...
Click to collapse
Nope, it's something in system tuner, I unchecked all the "checking" things so it's one of the "gtalk" options. I'm narrowing it down
Sent from my SGH-M919 using xda app-developers app
This has saved a bunch of us from odd battery drain. Skipjacks has been there and done that. Amazing informative thread! Going on two weeks without having to worry about bringing my charger to work thanks to skip
SGH-M919_Omega, the end result
kevinrubio1 said:
Nope, it's something in system tuner, I unchecked all the "checking" things so it's one of the "gtalk" options. I'm narrowing it down
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I don't believe it. Instagram is its own thing. It shouldn't be reliant on the google services framework at all.
Sent from my SGH-M919 using xda app-developers app
Pinan said:
Just a note. If you convert Google Play Services to a User App (TB), you can then Greenify (free ver.) it. This works very well and does not affect other functions that may rely on that app.
I also Greenify Maps and Google Search. Two more heavy drainers. Convert to User App first.
Fwiw, my sleep drainage is 0.3 - 0.4%hr, with wifi on 24/7.
I get either 7-8 days standby, or so far, 5.5 days with 3.5 hours screen time, or likely 6-7hrs screen time single day. Screen shots are in my posts.
I would argue too that these settings/tweaks do indeed increase your battery time, since while sleeping, the battery is draining at a much lower rate, therefore keeping more juice for live time use.
Although you and I don't use all of the same "tweaking" programs, we do seem to be on the same mission. Better battery life! :good:
Click to expand...
Click to collapse
I'm not sure whether Greenifying Google Search would save as much battery as freezing it would, but I'm going to try it out and see how it works for me. I'll report back some results in case anyone is curious
funkl3 said:
I'm not sure whether Greenifying Google Search would save as much battery as freezing it would, . .
Click to expand...
Click to collapse
It does. It also allows other functions to still work such as TTS. I had the issue a while back. Something to do with shared voice.
I also freeze Contacts and Calendar syncs as well. If I want them to sync I simply thaw them for a few seconds.
Skipjacks said:
I don't believe it. Instagram is its own thing. It shouldn't be reliant on the google services framework at all.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Maybe one of the "gtalk" options has something to do with notifications because last night I rebooted my phone a lot checking/unchecking options, none of the "checking" did anything! So that's good, and I unchecked some gtalk but not all and it worked!
Sent from my SGH-M919 using xda app-developers app
Great guide! A little bitter I had to read all of the pages in the original topic :laugh:
Skipjacks said:
I like your way of dealing with Google play services.
Click to expand...
Click to collapse
Btw. I forgot to mention that after I reboot the first thing I do is turn off Google Play in Running Programs. Persistent bugger. And of course I turn off notifications and auto update in GP as well with each new ROM install.
My tweak list is extensive. Someday I'll right it all down as you have. Save me some thinking, LOL.
Hello
I have had a massive battery drain problem on my Note 2, a couple of days after the 4.3 update. While being idle during the night it loses 25% to 30% of its battery and while using it I can literally see the percentage drop. I have tried everything that I could find on the net. EVERYTHING! Nothing worked. These included: Factory reset (twice), letting the battery frain completely and then recharging it while the phone was switched off, switching off all sync,disabling bloatware including KNOX components (the actual KNOX app is not installed), installing only a few apps after factory reset, using Gsam, Wakelock detector, Deep sleep battery saver (which could not make my phone sleep), no GPS, no 3G, wifi on only when needed and more besides.
The phone is only one year old and unrooted. On 4.1.2 it had a beastly battery performance of almost 1.5 days of normal to heavy use, with 300 apps on it. Now it cannot go for more than a few hours with the same use.
I cannot say for sure but it seems to me that the drain is the same when it is sleeping and when I am using it. Wakelock has given me a 75% awake time even though I only use it for 15-20% of the day at most nowadays. Battery settings show everything normal, or at least I think so, eg Screen 35%, Android OS 15-28%, Voice calls 10%, Android system 5-15%, Cell standby 7%, Device idle 4%, Media server 4%. The batttery chart shows a constant steep drop all the time.
The problem started one day when the Media server went mad consuming 50% of the battery. After I did the factory reset it has never again been a problem but the drain still persists.
I have also read that it's a mess up between syncing of Samsung apps and Google services, but I have no way of verifying that.
Can anyone help?
Thanks
I had the very same problem until yesterday myself but think I found a solution on the web.. Uninstall Google Search and Google Play Services and the goto the Play Store and wait for them to reinstall and that's it....! As I found that there is a bug in Google Services (Nlpwakelock and Location service)
Hope this helps...?
Sent from my GT-N7100 using xda app-developers app
terzisc said:
Hello
I have had a massive battery drain problem on my Note 2, a couple of days after the 4.3 update. While being idle during the night it loses 25% to 30% of its battery and while using it I can literally see the percentage drop. I have tried everything that I could find on the net. EVERYTHING! Nothing worked. These included: Factory reset (twice), letting the battery frain completely and then recharging it while the phone was switched off, switching off all sync,disabling bloatware including KNOX components (the actual KNOX app is not installed), installing only a few apps after factory reset, using Gsam, Wakelock defender, Deep sleep battery saver (which could not make my phone sleep), no GPS, no 3G, wifi on only when needed and more besides.
The phone is only one year old and unrooted. On 4.1.2 it had a beastly battery performance of almost 1.5 days of normal to heavy use, with 300 apps on it. Now it cannot go for more than a few hours with the same use.
I cannot say for sure but it seems to me that the drain is the same when it is sleeping and when I am using it. Wakelock has given me a 75% awake time even though I only use it for 15-20% of the day at most nowadays. Battery settings show everything normal, or at least I think so, eg Screen 35%, Android OS 15-28%, Voice calls 10%, Android system 5-15%, Cell standby 7%, Device idle 4%, Media server 4%. The batttery chart shows a constant steep drop all the time.
The problem started one day when the Media server went mad consuming 50% of the battery. After I did the factory reset it has never again been a problem but the drain still persists.
I have also read that it's a mess up between syncing of Samsung apps and Google services, but I have no way of verifying that.
Can anyone help?
Thanks
Click to expand...
Click to collapse
Download wakelock detector from the play store. It detect which app is waking your device (both screen and cpu) by list.. Then download greenify from the play store and herbinate (greenify) upper most apps from wakelock detector. Hope you can solve your problem
Sent from my GT-N7100 using XDA Premium 4 mobile app
yeminswe said:
Download wakelock detector from the play store. It detect which app is waking your device (both screen and cpu) by list.. Then download greenify from the play store and herbinate (greenify) upper most apps from wakelock detector. Hope you can solve your problem
Sent from my GT-N7100 using XDA Premium 4 mobile app[/
Thanks. I already have Wakelock Detector on. I mistakenly wrote "defender" instead of detector on the original post. It gives me Viber and Messenger as the most active wakelock apps. But they both were not installed when the problem started. Besides, on the 4.1.2 they created no problems. In essence I believe that Wakelock Detector cannot help much. Whatever this problem is , it is well hidden. Thanks for your interest and help anyway. Much appreciated.
Click to expand...
Click to collapse
In wifi settings, goto advanced and untick scanning always available.
Sent from my GT-N7100 using Tapatalk
Manjunath324 said:
In wifi settings, goto advanced and untick scanning always available.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Thanks, but I have checked and it was not ticked in the first place...unfortunately...
terzisc said:
Thanks, but I have checked and it was not ticked in the first place...unfortunately...
Click to expand...
Click to collapse
Which kernel you are using? And also i recommend using Greenify. Widgets usually eat a lot of battery, I went from battery lasting only 8 hours to get my battery use only 30% in 8 hours.
What i did: installed wakelock detector, gsam battery monitor and better battery stats.
Monitorized the wakelocks.
Applied greenify to the apps which were waking most
Removed widgets which were waking alot
Installed Toggle 2G.
Kernel settings: 200-1600mhz | zzmoove | AFTR+LPA | Multicore power saving (SCHED_MC) = 0 | GPU = stock settings
Works like a charm for me. Hope it helps! Any question, ask!
I've read all sorts of things about this problem since I updated and got hit. I have too much app data to lose by trying the factory restore (which by all accounts shouldn't change anything anyway since you'd still be stuck with 4.3)
I finally decided to try the age old blackberry cure-all: "if in doubt, pull it out" (the battery). Since the entire issue seemed to be related to battery caused problems (ie slow charging, fast drain, etc) it made a lot of sense.
And it worked.
I think the main reason this isn't more commonly tried to fix issues on Android is the same reason I didn't try it earlier. My case is pretty serious and isn't easy to remove. I'm glad I did take the time to take the case off though or I could have ended up wiping my phone.
Nukkels said:
I've read all sorts of things about this problem since I updated and got hit. I have too much app data to lose by trying the factory restore (which by all accounts shouldn't change anything anyway since you'd still be stuck with 4.3)
I finally decided to try the age old blackberry cure-all: "if in doubt, pull it out" (the battery). Since the entire issue seemed to be related to battery caused problems (ie slow charging, fast drain, etc) it made a lot of sense.
And it worked.
I think the main reason this isn't more commonly tried to fix issues on Android is the same reason I didn't try it earlier. My case is pretty serious and isn't easy to remove. I'm glad I did take the time to take the case off though or I could have ended up wiping my phone.
Click to expand...
Click to collapse
Thank you for the suggestion. I have already taken the battery on and off several times. It had no improvement. The phone is only a year old, that is why I don't believe the battery is the culprit. Besides, problems started only after the 4.3 update. Before that it was working perfect. Too much of a coincidence.
Sorry to hear that it didn't work for you
I'm not saying the battery is faulty in any way - however removing the battery and letting the phone power drain completely seems to stop whatever process is running under the buggy 4.3 long enough for it to work again as intended. It's basically just a more thorough way to reboot.
As I said, I've read all sorts of suggestions, many of which don't work for everyone (such as the factory reset) - this is hopefully just one more thing for people to try before they end up wiping their phone in desperation. I mainly posted here in the hopes that others with this issue that may not be forum members can get some more suggestions.
At least for me, wakelock and all the other diagnostic tools at my disposal showed nothing different to before the update. Many other people have found that the Android System is using a lot more of their battery than normal or some other apps are involved - if this is the case, it's likely to be a combination of things causing the issue (the firmware, the drivers, apps, hidden Samsung processes, etc).
Also, for what it's worth, I found that Knox supposedly wasn't installed (when I find it in the apps list, the button to install it is showing...). But it's showing in the list of apps so it must already be installed. I dug through the list of running processes (had to show the system processes too) and I discovered that several Knox and some other new Samsung processes were indeed running.
One other quick tip - If you wanted to check/tweak the 'developer options' and can't seem to find it any more, that's because it's now hidden since 4.2 - go to 'About Device' and tap 7 times on the Build Number. I tried disabling all background processes however it seems this only disables application level processes, not system level processes but if you've tried everything else, it can't hurt to try playing around with some of the options in there.
Nukkels said:
Sorry to hear that it didn't work for you
I'm not saying the battery is faulty in any way - however removing the battery and letting the phone power drain completely seems to stop whatever process is running under the buggy 4.3 long enough for it to work again as intended. It's basically just a more thorough way to reboot.
As I said, I've read all sorts of suggestions, many of which don't work for everyone (such as the factory reset) - this is hopefully just one more thing for people to try before they end up wiping their phone in desperation. I mainly posted here in the hopes that others with this issue that may not be forum members can get some more suggestions.
At least for me, wakelock and all the other diagnostic tools at my disposal showed nothing different to before the update. Many other people have found that the Android System is using a lot more of their battery than normal or some other apps are involved - if this is the case, it's likely to be a combination of things causing the issue (the firmware, the drivers, apps, hidden Samsung processes, etc).
Also, for what it's worth, I found that Knox supposedly wasn't installed (when I find it in the apps list, the button to install it is showing...). But it's showing in the list of apps so it must already be installed. I dug through the list of running processes (had to show the system processes too) and I discovered that several Knox and some other new Samsung processes were indeed running.
One other quick tip - If you wanted to check/tweak the 'developer options' and can't seem to find it any more, that's because it's now hidden since 4.2 - go to 'About Device' and tap 7 times on the Build Number. I tried disabling all background processes however it seems this only disables application level processes, not system level processes but if you've tried everything else, it can't hurt to try playing around with some of the options in there.[/Q
Thanks mate
I think you are right. It is probably a combination of many things. I have opened the Developer options some time back. The one thing that I do for sure in there is limit background processes to 4. Besides that I don't experiment much, exept maybe to change transition animation scale. I am actually thinking of rooting the phone and downgrading to 4.1.2. It was just fine before. I can live without the 4.3 add ons.
Click to expand...
Click to collapse
Problem still persists, even with Google+ and most other Google applications disabled
Sent from my GT-N7100 using xda app-developers app Some screenshots taken from 3 different apps. Wakelock detector, Better battery stats and Gsam battery monitor
Sent from my GT-N7100 using xda app-developers app
The only battery apps on my phone are the 3 mentioned above, so I don't know what the battery monitor that keeps my phone awake is. The drain existed before I installed these apps. I have read that Chrome could prevent the phone from going to sleep but it is disabled on my phone.
Sent from my GT-N7100 using xda app-developers app
http://www.youtube.com/watch?v=ak1sYWRaEKg
I faced same battery drainage issue, after installing wanam kernel and freezing all bloatwares through Titanium Backup. I'm satisfied with my battery now.
You can try.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Here is detail-
Disable sync always, enable when needed.
Disable wifi always scan from settings
Display set to auto
Uninstall apps of playstore you rarely use
Use widgets on lock and homescreen as less as you can (I don't use any)
Disable motion on settings
Freeze all bloatwares by TB except allshare and samsung content agent
Install Agni kernel, from agni control app-
profile: normal
Governor: pegasusq
Scheduler: cfq
Don't touch other tweaks, hardly you can tweak sound boost.
THIS GIVES ME A SATISFIED BATTERY STATUS.
regards.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Wew 4.3 does have may bugs
Anyone know how I might go about diagnosing why my phone has been running much warmer than usual? Just browsing Facebook (posts, not video) for about 5 minutes with brightness around 25% the temp was up to 41 degrees. It happened earlier today when I was just using Chrome, and it happens most days now. The issue began when I updated to 11.2.8.8 (the very next day), and the phone overheated several times the first few days, evidenced by the system warning about temperature, then recovering several minutes later. I haven't seen the system warning since then, but it's frequently above 40 degrees just doing everyday tasks. Oddly, I haven't noticed it overheating when playing games.
I usually run Omega kernel, which has always run cooler than stock during both normal use and heavy gaming, but this issue has occurred with both stock and Omega, so it's not kernel-related. The only magisk modules I have installed are debloater (for YouTube only), font manager, and systemless hosts, so that's not it either.
Maybe some app going haywire (how to find it? Nothing in battery usage) or some system behavior that changed in 11.2.8.8? Anyone else have this issue or find what's causing it?
That's just how this phone is. It was worse when the phone released before all of the updates. They've been slowly trying to fix it with each update. The 888 is a hot *****.
TheKnux said:
That's just how this phone is. It was worse when the phone released before all of the updates. They've been slowly trying to fix it with each update. The 888 is a hot *****.
Click to expand...
Click to collapse
I remember having that complaint when I first got it, especially when gaming, but it's been fine for me since like April, until this last update. And with Omega several degrees cooler. So there has to be something new causing it....
terlynn4 said:
I remember having that complaint when I first got it, especially when gaming, but it's been fine for me since like April, until this last update. And with Omega several degrees cooler. So there has to be something new causing it....
Click to expand...
Click to collapse
What version of Omega are you on? What build of OOS? AA, BA, DA? Are there any unusual rogue apps that you've noticed running more than usual?
TheKnux said:
What version of Omega are you on? What build of OOS? AA, BA, DA? Are there any unusual rogue apps that you've noticed running more than usual?
Click to expand...
Click to collapse
Latest version of Omega (8/7) since yesterday, but was having the same issue on the previous build (7/30). I'm on OOS 11.2.8.8 BA.
I haven't noticed any apps using more battery than expected, but I guess that might be part of my question... If there are any, what's the best way to find them? I'm not seeing any useful info in BBS or anything in GSam I wouldn't expect, except overall battery drain is a bit higher when it's been running hot. I do have a lot of apps installed and should probably clean up what I don't use, so I guess that's a place to start.
Find which apks are using the battery.
Google system apks are prime suspects.
Trash apps like FB, WhatsApp, LinkedIn... none of that junkware runs on my device, ever.
Examine all startup apks closely, take out the trash.
Power management can end up causing excessive battery usage, try turning it off.
Track down each battery hog and deal with it on a case by case basis rather than the flip a switch shotgun approach.
I use Karma Firewall's logging feature to help track down offenders.
Dependencies... sometimes the source of the high usage is hidden. What apks and services are running? What apks are using what services and why? What's apks are getting cached first when you clear them all? Any memory leaks?
Play with it... Androids wuv attention
blackhawk said:
Find which apks are using the battery.
Google system apks are prime suspects.
Trash apps like FB, WhatsApp, LinkedIn... none of that junkware runs on my device, ever.
Examine all startup apks closely, take out the trash.
Power management can end up causing excessive battery usage, try turning it off.
Track down each battery hog and deal with it on a case by case basis rather than the flip a switch shotgun approach.
I use Karma Firewall's logging feature to help track down offenders.
Dependencies... sometimes the source of the high usage is hidden. What apks and services are running? What apks are using what services and why? What's apks are getting cached first when you clear them all? Any memory leaks?
Play with it... Androids wuv attention
Click to expand...
Click to collapse
Good ideas. I just installed Karma Firewall and will see if it turns up anything.
How do you manage startup apps and running services? I used to use Servicely, but with Android 11 I find that even when I disable apps at startup they still start on their own, and it seems to use more battery than it saves. I've since disabled all apps of that kind and just let Android manage things itself. The only thing I do is go to individual apps and turn on battery optimization and disable background data if not needed, and I keep apps I don't use often in Icebox, including Facebook, which is the only social media type app I have. (Uninstalling FB isn't an option unfortunately.)
What do you mean by "which apps are getting cached first when you clear them all?" and how might I find it there are memory leaks?
terlynn4 said:
Good ideas. I just installed Karma Firewall and will see if it turns up anything.
How do you manage startup apps and running services? I used to use Servicely, but with Android 11 I find that even when I disable apps at startup they still start on their own, and it seems to use more battery than it saves. I've since disabled all apps of that kind and just let Android manage things itself. The only thing I do is go to individual apps and turn on battery optimization and disable background data if not needed, and I keep apps I don't use often in Icebox, including Facebook, which is the only social media type app I have. (Uninstalling FB isn't an option unfortunately.)
What do you mean by "which apps are getting cached first when you clear them all?" and how might I find it there are memory leaks?
Click to expand...
Click to collapse
Karma's logging feature doesn't work in 10 and above I believe, I run Pie. See what you got though. It will still block apk internet access though and uses almost no battery.
The battery optimization option can cause erratic behavior and I never use it. Close apps when done with them. Brave browser for instance will run in the background until closed.
Developer options>running services memory leaks show up as an apk who's memory usage just keeps increasing with time. It can get quit large. These are rare and poorly coded programs. More common on Windows.
Keep an eye though for memory hungry apps as they may be using excessive power but not always. Small memory users can be worse. Dependencies, sometimes a apk or service keeps making repeated requests because of a disabled apk or service.
Killing Goggle play Services and Playstore when not needed will help battery life.
Google backup Transport, Framework and Firebase are always disabled on my device.
All carrier, manufacturer, and Google feedback are disabled.
I have a Samsung device and I use its Device Care app to clear the cached apks. Then watch as they repopulate. You'll need an app that does this. In running services you can disable a suspect apk and see how long it takes to come back. I find that Device Care is more effective though and that ability has let me track down some misbehaving system apks saving me a reload.
FB is weaponized and a proven liability. Known data miner. Purveyor of disinformation and dissent. It has ruined countless lives and careers. It deliberately makes you have load the app to be able to send messages. If this last year hasn't taught you what you need to know...
I used it for one month 15 years ago and knew what it was back then. It's far worse today.
Don't feed the beast.
blackhawk said:
Karma's logging feature doesn't work in 10 and above I believe, I run Pie. See what you got though. It will still block apk internet access though and uses almost no battery.
The battery optimization option can cause erratic behavior and I never use it. Close apps when done with them. Brave browser for instance will run in the background until closed.
Developer options>running services memory leaks show up as an apk who's memory usage just keeps increasing with time. It can get quit large. These are rare and poorly coded programs. More common on Windows.
Keep an eye though for memory hungry apps as they may be using excessive power but not always. Small memory users can be worse. Dependencies, sometimes a apk or service keeps making repeated requests because of a disabled apk or service.
Killing Goggle play Services and Playstore when not needed will help battery life.
Google backup Transport, Framework and Firebase are always disabled on my device.
All carrier, manufacturer, and Google feedback are disabled.
I have a Samsung device and I use its Device Care app to clear the cached apks. Then watch as they repopulate. You'll need an app that does this. In running services you can disable a suspect apk and see how long it takes to come back. I find that Device Care is more effective though and that ability has let me track down some misbehaving system apks saving me a reload.
FB is weaponized and a proven liability. Known data miner. Purveyor of disinformation and dissent. It has ruined countless lives and careers. It deliberately makes you have load the app to be able to send messages. If this last year hasn't taught you what you need to know...
I used it for one month 15 years ago and knew what it was back then. It's far worse today.
Don't feed the beast.
Click to expand...
Click to collapse
Thanks for the info, it's interesting. However, if you're running Pie & not even using a OnePlus device, none of this is going to be applicable to my issue which is specific to OOS 11.2.8.8 on this particular device, only present since last month's update.
Re: FB - I'm required to use it for my job (well, second job), and I need it on my mobile device in order to do that job, so it's not going away. Freezing it when not in use is the best I can do.
terlynn4 said:
Thanks for the info, it's interesting. However, if you're running Pie & not even using a OnePlus device, none of this is going to be applicable to my issue which is specific to OOS 11.2.8.8 on this particular device, only present since last month's update.
Re: FB - I'm required to use it for my job (well, second job), and I need it on my mobile device in order to do that job, so it's not going away. Freezing it when not in use is the best I can do.
Click to expand...
Click to collapse
You cross platform OS version and manufacturer to find solutions. I have a lot of posts here but few asking for help because I do the above or just keeps at it until I work it out as it's my issue.
*shakes head*
You've painted yourself into a corner.
@terlynn4 I use BatteryGuru because it uses root to find rogue apps that are draining battery unnecessarily. Give it a go and see if that helps pinpoint the problem at all.