[Q] Huge Lag on my Samsung Galaxy Tab Pro 10.1 - Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble

So out of no where my Galaxy Tab Pro 10.1 began lagging pretty bad. I closed all of my open apps and the lag persisted. My ram was at about 86-90% being used at one point, but even when I got it to drop the Lag continued.
Does anyone know why this was happening?? and how to fix it next time it happens?

Install a task manager to see which app or process is using CPU when lagging. Don't pay attention to high RAM usage, that's how Android works,

Reboot the device in Safe Mode and see if it persists.
If you don't know how, hold the power button and long press "Power Offf" and a prompt will appear asking if you want to reboot to Safe Mode.
All 3rd party apps will be disabled (including system app updates I think?)

You can also use WakeLock detector (https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector&hl=cs, http://www.xda-developers.com/andro...one-awake-wakelock-detector-xda-developer-tv/), which monitors the processors and screens wakes by the apps, so you can analyze, if there are any apps, that can potentially cause the problem.

Related

[Q] Process lifetime

I was wondering if there's any way to prevent android from killing programs immediately after i press the home button or switch to other programs.
For example, I'm browsing the Web when an sms comes in. Using home button (long pressing) I switch the task to answer and when I come back, the browser is gone and i have to load the page again (although it reloads in the same state).
It's really annoying. Reloading a webpage is not a problem but what about playing games?
I'm running InsertCoin 1.5, have about 80- 90MB RAM unused. And I doubt that I had RAM shortage
Thanks for reply
Your brought up that old horse (debate) on why the android OS does or does not need task managers. Yes, the wonderful engineers at android, developed a platform unlike windows, manages processes (by some opinions) way better than Windows. When you switch screens, it freezes the process, and holds it until you come back. When the phone starts to run out of allocated memory, it starts to kill the (less used) processes.
Now, I've heard of allocation of process levels to cause some apps to continuous run, which would be an interesting development for some dev to take on. You can select what apps you'll like to constantly run even if you switch screens. This would help those who would want to quickly drain their battery for OS calibration purposes.
If I find such a solution, ill report back.
Sent from my HTC Vision using XDA Premium App
Android should never kill the 2nd process in line (aka the Browser when switching to SMS), unless you're extremely short on RAM. In low RAM conditions, it will kill the farthest from recently used app in order to free up RAM.
How often do you notice this? is it always killing the app you switch from? Because this isn't correct (unless you're literally out of RAM as I said).
martonikaj said:
Android should never kill the 2nd process in line (aka the Browser when switching to SMS), unless you're extremely short on RAM. In low RAM conditions, it will kill the farthest from recently used app in order to free up RAM.
How often do you notice this? is it always killing the app you switch from? Because this isn't correct (unless you're literally out of RAM as I said).
Click to expand...
Click to collapse
Like i said. I had plenty of free RAM. So it's unlikely that I have RAM shortage.
I spent the morning examined things. Just figured I it out:
Flash this over and I have 3 apps in line.
Combine with Perfect task switcher, I got what i wanted.
Also, I noticed that switching by long pressing HOME button and choosing apps cause the app to restart while using BACK button won't
I don't know if this is Android behavior or my device's issue
But anyway, I got it sorted out
Thanks you u guys
I'm running CM7. Long pressing home and switching between numerous apps I've never had an app close on me. Must be a ROM/device combination situation for you...

Lag after 5.1.1 update

Hi, i dont remember there being much lag before updating yet now, opening apps or even trying to swipe between the pull down menu pages (battery, cinema mode & settings) for example sometimes takes a couple of seconds.
I've reset the watch to factory settings and uninstalled the app on my phone and reinstalled.
It feels like i need to reduce the animation times like i would in the phones developer settings.
Any suggestions?
I haven't seen anyone else on XDA or reddit with lag issues. If you can sideload a CPU profiler or otherwise monitor processor load, I would recommend making sure an app or system process isn't hogging all the CPU cycles. If there is no issue and the lag is still there, the only option might be to contact Sony support.
I could not use the watch lagged too much, restarted the watch and it seems better.

Note 4 Sprint 6.0.1 Baseband PC1 lags

I bought a used Note 4 Sprint and since I flashed marshmallow using odin on it it gets laggy or reboots from time to time.
Is it something with my Baseband? Like should I install a different Frimware or it's a marshmallow issue?
The battery is okay and the screen is all good as well.
And finally do you recommend me any stable ROM or stock ROM ? Thank you I'm advance
You could likely do better with later Marshmallow releases and possibly custom ROMs if that's your thing. I'm on the PJ1 update running UN7 (Note7) port.
Between, Samsung, Google and Sprint, there's enough bloat on a stock Sprint Note 4 to sink a ship. And Samsung can't optimize the RAM caches well enough to suit individual preferences because it favors its native apps that are baked in as well as other system apps from Google.
This optimization may not favor the apps you prefer to run at will so you need to understand how to deal with it. There's Samsung's version of Doze and there's Android's version of Doze on your Marshmallow Touchwiz firmware. Samsung's version will routinely shut your apps down and doesn't do a good job of real time RAM management while sleeping. It's based on a 3 day run theory but it doesn't my user apps use at all; it shuts apps down that haven't been used in three days. This favors apps that it runs in the backgrounds continually.
So turn that of and focus on Android Doze is my advice. You can find both methods in battery management. Smart Manager may a shortcut to battery management but you can use Settings to find it too. You may see App power monitor on first battery screen; I advise turning that one off. Android doze can be found by tapping Battery usage then tapping 3 dot menu button in top right to goto Optimize battery usage. Once there, the dropdown menu will allow you optimize doze by showing all apps. I disable ones I don't want running continually but enable those that may be impacted by doze with screen off only. If you ever wonder why your music or downloads stop with screen off, here's a place to start. Push notifications should happen anyway with doze active so those may not need enabling to run continually.
You may consider freezing apps that show as running when you don't prefer them to even you're checking running apps. You can use Smart Manager often to optimize RAM or get an app that allows you white list some apps and dump cache for non white listed apps on a scheduled basis.
Personally I find Marshmallow Touchwiz poor for RAM management. The UN5 Lollipop ports managed RAM better without having doze. Somehow I think even the Note 5 may not have good RAM management on Marshmallow. Maybe Nougat is a different story? But I do know that Marshmallow proved to be a bigger challenge than Lollipop did, especially the ports. Why would I run Marshmallow? I guess its inherently faster than Lollipop. But only when optimized, IMO.
I also use Boost+ by HTC found in Google Play Store to free up RAM. Samsung thinks many apps I use regularly aren't being used. HTC Boost+ can discern app use better and logs freed RAM so you know it's working.
As a user, you can discern if these suggestions help or not. Just lag, preferred running apps and battery management advice. They may not be every user and YMMV.
Edit: pay close attention to battery capacity at reboots; bad batteries do have a tendency to shutdown, possibly reboot as well. Last time I had a bad battery, it was on a lollipop ROM; phone shutdown at 30% and plugging in charger showed 0%. Marshmallow may be different; battery is suspect for reboots in Marshmallow. I haven't experienced reboot issues with Marshmallow or have a bad battery to add to this suspicion though.
Sent from my SM-N920P using Tapatalk
You couldn't have got a better answer very concise and thought out. I can only add that a bad battery will have the same results as far as shutdowns in marshmallow. Never had a reboot issue. However many have with the earlier builds.
Sent from my SM-N910P using Tapatalk

P6 battery usage

Hi, I need a bit of help please with my P6 still on 4.2.2 my issue is a massive drain on battery life apparently being caused by Android OS using up around 70%. I have only wifi and mobile internet running with location etc turned off. One thing that I'm unable to control the background apps manager setting properly in that the only app I want to keep running is WhatsApp so I set the All button to off. However in next to no time I find it has switched itself back to on.
I've been through manage apps and turned off or disabled pretty well all that I dare.
Many thanks in advance.
Oh, just to add a little more information if I try to access Start up manager I get a "Power manager has stopped working" message.
Is there some way I could reinstall or repair the Power manager?
Unfortunately WhatsApp seems to override sleep on a lot of systems so you may be in a situation where it is constantly waking itself up.
Try just letting it run i.e don't try to stop it in start manager.
Thanks for that, the problem doesn't appear to be with WhatsApp because when I look at the battery consumption tab the biggest user by far, and mean at up to 70% is the android OS.
I only mention start up manager as it's one of the items controlled through power manager. My real issue is the background apps manager self enabling all background apps.
I'm really trying to avoid doing a factory reset if possible.

How to prevent apps from getting killed

Hi all,
I'm running several apps that should run all the time (AdGuard, Network Speed Meter) or for a long time (speed trap warner,...) but OxygenOS kills them after a certain period. Some of them restart automatically, some don't. Of course all of these apps are 'not battery optimized'. Is there any chance to prevent OxygenOS from killing them?
Are there custom ROMs that can overcome this problen?
I'm on the latest OxygenOS Pie Beta, but the behavior was similar on Android O...
Thanks a lot,
W
Did you try locking the app via recents menu?
Thank for the info, didn't know that.
Unfortunately it doesn't help, Adguard and the network monitor don't appear in recents. The speed trap warner automatically starts and stops when I'm in the car, i don't want to open recents manually every time.
Battery - Battery optimisation - Don't optimise
safwankatharudheen said:
Battery - Battery optimisation - Don't optimise
Click to expand...
Click to collapse
This is not changing anything,e ven with disable battery disabled, even with adaptative battery disabled.
I have the same problem. I have not found any solution whatsoever. This is really frustrating. I've made sure apps aren't optimized. Advanced optimization is disabled. Developer options background limit is at standard. I've pinned the apps in recent apps and it still happens. Apps get killed all the time.
For example,
1. I use Google Fit to start tracking a run. Within 10 minutes of tracking, the app is closed and workout not tracked. Its not even like i touched the phone and opened other apps during this.
2. I have VoIP account setup in the default dialer. Calls come through only 50% of the time cause the dialer is closed.
3. YouTube Music, constantly gets closed if i simply pause the music. Within 2 minutes, the app is closed.
4. Trying to transfer 15GB of files through Explorer app from phone to file server, never succeeds if i don't watch the app and keep the screen on.
5. Plex gets closed and therefore my photos don't auto backup with the phone is plugged in.
This is absolutely ridiculous! Why the hell a phone with 8GB of RAM is killing apps is beyond me!
Custom ROM on the same phone, like Lineage OS, no issues. Can have optimization on, battery manager on and all. In fact, battery life is better on custom when its not killing the apps! Seems to be the only solution until OOS can stop killing apps so aggressively.
M3drvr said:
I have the same problem. I have not found any solution whatsoever. This is really frustrating. I've made sure apps aren't optimized. Advanced optimization is disabled. Developer options background limit is at standard. I've pinned the apps in recent apps and it still happens. Apps get killed all the time.
For example,
1. I use Google Fit to start tracking a run. Within 10 minutes of tracking, the app is closed and workout not tracked. Its not even like i touched the phone and opened other apps during this.
2. I have VoIP account setup in the default dialer. Calls come through only 50% of the time cause the dialer is closed.
3. YouTube Music, constantly gets closed if i simply pause the music. Within 2 minutes, the app is closed.
4. Trying to transfer 15GB of files through Explorer app from phone to file server, never succeeds if i don't watch the app and keep the screen on.
5. Plex gets closed and therefore my photos don't auto backup with the phone is plugged in.
This is absolutely ridiculous! Why the hell a phone with 8GB of RAM is killing apps is beyond me!
Custom ROM on the same phone, like Lineage OS, no issues. Can have optimization on, battery manager on and all. In fact, battery life is better on custom when its not killing the apps! Seems to be the only solution until OOS can stop killing apps so aggressively.
Click to expand...
Click to collapse
My app is not killed when i lock it in the switch app menu
There's a whole website regarding that issue on several devices, maybe it helps: dontkillmyapp(dot)com/general#user-solution

Categories

Resources