Database Users

Slow Down on Hero

Hi all,
Had a quick search round these parts to see if anyone has ask about it, and apparently now
I've noticed that the touch flo interface has become really slow again, most notably when bringing down the notification area; it's a good 5 - 8 seconds before it comes down to where my finger is! Another way I can judge it is by playing ThrottleCopter, any lag makes the game unplayable...
The first time, the culprit was Last.fm's offcial app, and gettign rid of it made it all spring-chicken again, but I haven't downloaded any new apps of late...
*Please* don't tell me I need to reboot my phone every week or so to stop it being laggy; That's why I ditch my Tytn II !!!
Many thanks for any help provided, and if you require more info (I'm guessing an app list, or ROM version [Stock from T-mobile]), ask please!

...Does no one else have this problem? It's really bugging me, insofar as that it's becoming unusable without rebooting it again, and not placing calls when tapping a contact in the call history list.

Do you use Peep ?
If you are, log out of Twitter via the social networks section in Settings and try another client like Twidroid (which uses its own independent login)
Made a huge performance difference to me on the initial stock Orange firmware.
Else wait for the T-Mobile v2 firmware or go MoDaCo.

@Joemax:
I don't use Peep or Twitter, and have made sure it's "logged out" in the settings menu, but can't access the Peep settings menu as I haven't (ever) logged on.
Thanks for the reply, as I quite keen to find the source of the problem. The only other thing I've heard thus far is that rooting the phone _can_ give a speed boost, but it's not been confirmed?

Rooting on its own won't speed up your Hero or any handset as far as I know.
But if you root and then replace the firmware with MoDoCo's you will see a speed boost. His ROM is based on the latest HTC firmware release.
The other thing would be to turn off all the background notifications that apps you have put on the Hero are setup to do... not the stock ones, but apps from the Market you have loaded.
Some of these put persistent information in the Notifications panel and these may be slowing down the handset before showing you the panel.
Then enable them one by one gradually until to find the likely culprit.
Some battery monitoring apps and task manager / switching apps, do use too much of the CPU from what I've read.
Worth a try.

Thanks for the help Joemax.
AFAIK, I don't have any non-stock apps that have any b/g notifications, as there aren't a whole lot of apps on my phone (a couple of games, boring utilities like the compass), but I have got the battery status widget, which may be the culrpit... Fingers crossed

Whenever I have used skype my hero lags. I always have to kill skype even when I exited the app correctly. Maybe this applies for you as well? Did you try to kill some apps (check after each kill if performance is better)? this is how I found out the skype issue.

I have TasKiller Full, and I do kill off apps periodically, and haven't noticed skype in the background, although the Last.fm one kept on coming back even after a force kill .
It's a useful app for me (as I use Skype as my main IM), so I'll onyl get rid of it should it be the fault.
Just checked now, as it goes, and there are no non-stock apps running, as it's still slow - taking about 3 seconds for the notification bar to catch up. As for notifications, the only ones I've noticed since the joemax asked the question is Gtalk, Gmail, and the phone ones (sms, missed calls), and the USB one once plugged in.
Oh dear... it's not looking good to find the source, is it? I mean, short of deleting all non-stock apps and putting them back on one by one...

Lollipop Findings

Installed Lollipop last night and a few things that I found are working/not working. Let's get a list going here.
1. H+ icon no longer shows up. (ATT)
2. Feels like a new phone performance wise.
3. Home Launcher App no longer seems to work. (https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en)

Cast screen option is now available in the notification pull down, but it still doesn't recognize the Chromecast.
ART uses a lot more space for apps, so a microSD card is now a must. Probably why Moto added it.
Camera doesn't seem to have any improvements. Not worse, but I'm not seeing anything better either.
Sometimes specific apps (like Skype for example) don't seem to use both speakers leaving the sound very quiet.

Screen pining option in security is awesome
Sent from my Galaxy Nexus using xda premium

Hey, I'll paste the questions I leaved in a thread I created but doesn't seem so popular:
First and foremost, I'm curious about the new memory management in this Release. As you can see in this threads 1 XDA Thread 2 (Official Motorola Forums one) the problems with RAM management in KitKat were MASSIVE.
- How do you feel it is as of right now? It's still there? It's a little better?
- How does the CPU respond? Could you run an Antutu Benchmark to compare with KitKat?
- I know it's a little early to ask, but I'm curious about Project Volta. Do you notice more battery life?
Click to expand...
Click to collapse
THANKS !!!

jarbro said:
Installed Lollipop last night and a few things that I found are working/not working. Let's get a list going here.
1. H+ icon no longer shows up. (ATT)
2. Feels like a new phone performance wise.
3. Home Launcher App no longer seems to work. (https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en)
Click to expand...
Click to collapse
Have noticed performance improvements? Such as better memory management, improved responsiveness, faster app loadings etc. ?
On 4.4.4, I can't run Facebook and Chrome simultaneously without one getting kicked out of memory

jarbro said:
Installed Lollipop last night and a few things that I found are working/not working. Let's get a list going here.
1. H+ icon no longer shows up. (ATT)
2. Feels like a new phone performance wise.
3. Home Launcher App no longer seems to work. (https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en)
Click to expand...
Click to collapse
What about battery usage? Does the application optimizing occur at every boot?

ksuuk said:
What about battery usage? Does the application optimizing occur at every boot?
Click to expand...
Click to collapse
100% at 8am. Was down to 10% around 2:30PM after heavy usage. Definitely not real world use. Mostly playing around with Lollipop.
Application optimization does not happen at boot like it did w/ ART on 4.4.4.
I'd like to note, it took my phone nearly 45 minutes to upgrade from 4.4.4 > Lollipop.

jarbro said:
100% at 8am. Was down to 10% around 2:30PM after heavy usage. Definitely not real world use. Mostly playing around with Lollipop.
Application optimization does not happen at boot like it did w/ ART on 4.4.4.
I'd like to note, it took my phone nearly 45 minutes to upgrade from 4.4.4 > Lollipop.
Click to expand...
Click to collapse
It would appear your lolly got well and truly licked...
L LLIP P

Can you test some more things, like a benchmark or something just to see, and more impressions about the lag of open the menu?

I waded through all the spam and robotically dubbed crap on YouTube, and FINALLY found someone who's actually bothered to make a brief video... so here it is:

Has anyone else noticed not being able to access the camera from the lockscreen on Lollipop?

My thoughts on Lollipop 5.0:
-Booting the phone takes about 30 seconds. I have a lot of apps on the SD card, and they take a while to become available. Perhaps 2 minutes. I had to move a lot of apps to the SD card to get room for the update, so I can't compare before and after times for finding apps on the SD.
-When the phone was updating to Lollipop it said it optimized 105 apps. It does not optimize on every boot. I'm pretty sure apps on the SD card were not optimized based on number of apps.
-Music (Pandora and Play Music) still stops playing in the background when I launch some apps. The suspected 'memory leak', memory management problem, or whatever the cause, has not been fixed. So no apparent change there.
-If I create an app folder with apps on the removable SD, those apps still do not reappear in the folders when I restart the phone. No change.
-App-specific notifications are awesome. I have 'Subway Surfers' on my phone because my kids like the game. I hate getting notifications every day for an app I don't even play. I have disabled notifications for that app. Definate positive change.
-I use an app called 'Notification Toggle' to add toggles for skipping tracks, camera, battery life with numbered %, turning on wifi and cell data, etc. The Cell Data toggle doesn't work any more, it takes me to a screen that can be used to turn on/off data roaming but not data all together. Hopefully that will be fixed. The notification screen update already gives me another option (see my next comment).
-The pull-down notification menu can be pulled down again to show some settings that partly replace the 'Notification Toggle' app I just mentioned, including turning cell data on/off. It's a nice feature. I wish it were customizable. Definate positive change; it doesn't quite replace 3rd party apps for me, but that's part of the Android customizable experience.
-It takes longer to unlock. The unlock pattern/code input has been replaced by notifications, you need to swipe up before unlocking. Minor change but definitely not an improvement for me.
-Stability and responsiveness are good. I haven't noticed any lag but I don't remember noticing lage on 4.4.
-Battery life? I'm a compulsive phone charger, so I don't know yet. I like the new battery life screen. It shows charge over time like it used to, and it also shows projected battery life. It says I have 10 hours left, after using the phone for about an hour looking at settings, locking/unlocking the phone while on WiFi streaming Pandora.
-Lockscreen notifications have the following settings:
Show all notification content will show content in new text messages and what is playing on Pandora or Play music; in Play Music it lets me skip to the next song without unlocking; I can't change tracks in Pandora from the unlock screen. Annoying change for me.
Hide Sensitive content in Notifications lets me know I got a text but doesn't show the message; I can see what is playing and skip tracks in Play Music but not Pandora
Show Nothing shows... nothing.
I wish I could select which apps would show their content on the lock screen; in my mind what I am playing in Pandora is not nearly as sensitive as what texts I receive.
If I get a text and there are multiple notifications on the lock screen, or if I get more than one text,it won't show the content of the texts. No scrolling to fit more notifications (like the notifications shade). So if you have a lot going on, lock screen notifications become sort of useless, and that's when they might be the most useful.
I used to be able to press the power button and skip to the next pandora track from the unlock screen. Two actions. Now: (1) I press the power button, (2) swipe up, (3) enter the unlock pattern, (4) open Pandora, and (5) skip to the next track. Convenience has suffered.
People will have different opinions, but for me personally the whole lock screen experience is a step backwards. I think there are some simple fixes that could make it very good, and I hope this is a bad start to a good feature (i.e. waiting for 5.0.1).

Memory leak/bug is still there Oh god why
@mike_ekim
can you check if the usb otg bug is still there?

mike_ekim said:
-It takes longer to unlock. The unlock pattern/code input has been replaced by notifications, you need to swipe up before unlocking. Minor change but definitely not an improvement for me.
Click to expand...
Click to collapse
Thanks, I asked if this was the case in another thread, nice to have it confirmed but wasn't the answer I wanted.
From my impression the KitKat lockscreen is perhaps better for people like us (it is for me), you can easily see your notifications but not see any content just the icons at the top, music playback controls are easily accessible and the pattern/PIN is displayed without a swipe.

thisisjason said:
Has anyone else noticed not being able to access the camera from the lockscreen on Lollipop?
Click to expand...
Click to collapse
I can get to the camera app from the lock screen without unlocking, take pics from front and rear camera, shoot video, and view the gallery pics/videos I took from THAT LOCKED SESSION ONLY. I can't see all the other pics/videos on the phone.
A minute later I accessed camera without unlocking the phone again. I could NOT see the pics that I took a minute ago with a locked phone. In other words, if I take pics with a locked phone those new pics are still private, as long as I turn off the screen again. Maybe that's the default Lollipop behavior, but I'm glad it works that way.
Edit: the phone wants to back up the photos that i took with the screen locked. I need to look into this. I deleted those pics i.e. I selected 'delete everywhere'. If someone takes pics with my phone, will they be backed up to online folders/tools that I share? I'm just a simple caveman lawyer, your new technology frightens me. I just copy/save my pics manually, so I don't even understand how backup works. I'm pretty sure backup was turned backup off in Jelly Bean.
Another edit: The Photos app says that backup is for 'my eyes only'. As long as no one can take a pervy pic with my locked phone and share it with the world, I'm ok. Because we all know how safe pics on our phones are.
bhavin192 said:
Memory leak/bug is still there Oh god why
@mike_ekim
can you check if the usb otg bug is still there?
Click to expand...
Click to collapse
Sorry, I don't have a thumb drive or otg cable handy. I never heard of the problem till you mentioned it, I guess I don't use thumb drives with my phone.
Different subject:
I connected the phone to my computer with USB debugging turned on, and I got this driver error:
Device driver software was not successfully installed
Motorola ADB Interface X No driver found
It's an old problem and looks like getting the error is expected, but I'm busy at work and can't be bothered to look into it for now. File explorer from the PC works fine. I have other android toys, I don't like messing with my main phone so I don't need ADB anyways. I honestly think I've never even put this phone into USB Debug before today.

mike_ekim said:
I can get to the camera app from the lock screen without unlocking, take pics from front and rear camera, shoot video, and view the gallery pics/videos I took from THAT LOCKED SESSION ONLY. I can't see all the other pics/videos on the phone.
A minute later I accessed camera without unlocking the phone again. I could NOT see the pics that I took a minute ago with a locked phone. In other words, if I take pics with a locked phone those new pics are still private, as long as I turn off the screen again. Maybe that's the default Lollipop behavior, but I'm glad it works that way.
Edit: the phone wants to back up the photos that i took with the screen locked. I need to look into this. I deleted those pics i.e. I selected 'delete everywhere'. If someone takes pics with my phone, will they be backed up to online folders/tools that I share? I'm just a simple caveman lawyer, your new technology frightens me. I just copy/save my pics manually, so I don't even understand how backup works. I'm pretty sure backup was turned backup off in Jelly Bean.
Another edit: The Photos app says that backup is for 'my eyes only'. As long as no one can take a pervy pic with my locked phone and share it with the world, I'm ok. Because we all know how safe pics on our phones are.
Click to expand...
Click to collapse
Thanks, weird that it's not working for me. If I restart the phone, it will work the very first time I'm on the lockscreen and swipe into the camera, but on subsequent attempt I get a black screen with the icons for switching between front and back cameras and for shooting video, but none of the controls work.

thisisjason said:
Thanks, weird that it's not working for me. If I restart the phone, it will work the very first time I'm on the lockscreen and swipe into the camera, but on subsequent attempt I get a black screen with the icons for switching between front and back cameras and for shooting video, but none of the controls work.
Click to expand...
Click to collapse
Interesting, that's an inconsistency between out phones. I can enter, exit, and re-enter the camera app repeatedly without unlocking the phone, turn the screen off and on again, and use the camera again without unlocking.
---------- Post added at 12:36 PM ---------- Previous post was at 12:23 PM ----------
One more thing: the home screen redraw issue still happens, but less often. For example I just used chrome browser briefly, went home and the screen didn't redraw. Same with Play Music.
I loaded Clash of Clans, collected some gold/elixir, donated some troops, went to home screen and the screen had to redraw. Exiting a lightweight game like 2048 does not cause the home screen to redraw (so far). Overall the home screen seems to redraw less often.
---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------
One more thing: the home screen redraw issue still happens, but less often. For example I just used chrome browser briefly, went home and the screen didn't redraw. Same with Play Music.
I loaded Clash of Clans, collected some gold/elixir, donated some troops, went to home screen and the screen had to redraw. Exiting a lightweight game like 2048 does not cause the home screen to redraw (so far). Overall the home screen seems to redraw less often.
Actually, another one more thing:
In settings-->developer options-->Process stats: I got the message "device memory is currently critical" I killed a few apps (including Play store, play music, all the Motorola apps) and got 403 MB ram available. Settings is using 70MB, Notification Toggle is using 3MB, Swipe is using 26MB. I went back to Process Stats and it now says 'Device memory is currently normal". Sorry, I didn't take not of how much memory was available before killing apps.
---------- Post added at 12:56 PM ---------- Previous post was at 12:45 PM ----------
Reboot:
Unlock screen 50 seconds after pressing power
Widgets active 1 min 15 seconds after pressing power
Apps on SD available in app drawer 2 minutes 30 seconds after pressing power. I have 36 apps on my SD card, it's a 16GB card with 5.4GB available (lots of media) and I believe it's a class 4 or class 6).
On boot I had 408MB ram free. After killing some apps I have 453 MB free; settings using 70MB, Swype 24MB, and Google Search 15MB. MotoCare using 15MB and if I kill it it just restarts. I don't know if Settings always uses RAM or if I get that RAM back when I exit Settings.

How much more space does ART take?

You can try ART on KK... but on my XT1068 Dalvik 2.6Gb free space / ART 2.0Gb free space.

I updated my phone yesterday.
It's now faster. The lollipop is so beautiful.
The only problem is that yes I can't see
H+ icon anymore. Does anyone know what ?
Sent from my XT1064 using XDA Free mobile app

[Q] How to schedule a switch from priority interruptions to all notifications?

Hi all,
I don't know what Google and especially Samsung were smoking when releasing Android Lollipop, but the new "interruptions" were really a bad idea IMHO.
If Samsung had just copied what Google did there, it would be still ok, but Samsung removed the schedule option in the interruptions menu! Why Samsung, why? I just want to disable all notification between 10pm and 7am, but still be able to receive calls and let my alarm get off at 6:30am.
I understand that what I want can be configured with priority interruptions and it looks like it's working like intended except the scheduling part which was completely removed by Samsung. So now I have to turn priority interruptions on and off manually and if I forget it, some incoming spam mail may wake me in the middle of the night, wtf Samsung!
Is there a way to schedule this switch somehow automatically?

foo said:
Hi all,
I don't know what Google and especially Samsung were smoking when releasing Android Lollipop, but the new "interruptions" were really a bad idea IMHO.
If Samsung had just copied what Google did there, it would be still ok, but Samsung removed the schedule option in the interruptions menu! Why Samsung, why?
Is there a way to schedule this switch somehow automatically?
Click to expand...
Click to collapse
Yes you are completly right ,Samsung decided to cut even more in the new notification strategy on the Note 4 then Google did originally and no it's not possible to schedule like it is in the "complete" Lollipop release

Seems not a very interesting topic based on the amount of replies in this thread - anyway, I found some "solution" which I'd like to share with you
I remembered that I bought Tasker a long time ago out of curiosity, but as this app is pretty complicated (for me), I never really used it. I just gave it another try and I'm happy that it can deal with "interruptions", so it can be configured to set interruptions to priority mode for a certain period of time which is exactly what I want.
As I still don't like this app, do you know of any other similar apps that can deal with interruptions but have a nice and shiny user interface?

battery life with resolutions

I have not seen real comparisons yet of battery at all 3 resolutions. Has anyone tested? I'm running at the lowest today just to see. Honestly screen is fine and can barely tell the difference at lowest res

curious for this as well. Got fairly good life out of it with factory settings at 1080. Switched to 1440 last night and cant really tell a difference in resolution but i think battery life is hurting.

EDIT: Tmo S8 with update, for reference.
Because I also couldn't tell a difference, I immediately switched to the lowest resolution. With the following settings, I had 92% battery left at the end of a work day where I would have had about 60% on the Nexus 6p:
- Brightness always at max and disable auto brightness. Bluetooth on, WiFi off.
- Disable pretty much every Samsung feature, gesture, and Samsung app. Made as Nexusy as possible (still using Samsung launcher, which is fine, and I uninstalled Google because I don't really use Google Now and suspect it's a battery hog. The only voice feature I was using was "ok Google navigate home", but now the maps app just let's you save directions as home screen shortcuts).
- Going through the permissions settings in the advanced app options menu in Samsung settings, I disabled all permissions for each app except the ones I know they need.
- Installed Package Disabler Pro and blocked a **** ton of stuff, including in the system packages. Anything with the word bixby in it, all of the T-Mobile apps except visual voicemail (anyone know if I can disable that and still get visual voicemail via the Samsung phone app??), and most of the Samsung apps except things with the word clock or calendar in them because I assumed the overall ROM relies on them but I could be wrong.
- Once done with everything, close all apps then go into settings > device maintenance > optimize now, then reboot the device.
- This CAN have VERY good (potential) battery life, better than the Nexus 6p when reviews were suggesting it was pretty bad.

.psd said:
EDIT: Tmo S8 with update, for reference.
Because I also couldn't tell a difference, I immediately switched to the lowest resolution. With the following settings, I had 92% battery left at the end of a work day where I would have had about 60% on the Nexus 6p:
- Brightness always at max and disable auto brightness. Bluetooth on, WiFi off (only whole at work).
- Disable pretty much every Samsung feature, gesture, and Samsung app. Made as Nexusy as possible (still using Samsung launcher, which is fine, and I uninstalled Google because I don't really use Google Now and suspect it's a battery hog. The only voice feature I was using was "ok Google navigate home", but now the maps app just let's you save directions as home screen shortcuts).
- Going through the permissions settings in the advanced app options menu in Samsung settings, I disabled all permissions for each app except the ones I know they need.
- Installed Package Disabler Pro and blocked a **** ton of stuff, including in the system packages. Anything with the word bixby in it, all of the T-Mobile apps except visual voicemail (anyone know if I can disable that and still get visual voicemail via the Samsung phone app??), and most of the Samsung apps except things with the word clock or calendar in them because I assumed the overall ROM relies on them but I could be wrong.
- Once done with everything, close all apps then go into settings > device maintenance > optimize now, then reboot the device.
- This CAN have VERY good (potential) battery life, better than the Nexus 6p when reviews were suggesting it was pretty bad.
Click to expand...
Click to collapse
Did you actually know what you were disablinh in pdp

km8j said:
Did you actually know what you were disablinh in pdp
Click to expand...
Click to collapse
Kind of, but not entirely.
It has a section for verified safe-to-disable apps. If that isn't enough, there's a section for "system" packages where I avoided disabling anything that I want pretty confident wouldn't affect the overall system (like I didn't disable anything that has to do with sound or audio for example, even though a few of them looked like bloat). I'm the system section however is where you can disable bixby and carrier related ****. There's a search section, which is very helpful (e.g. search "bixby' and disable everything).
I have the advantage of having messed with phones and done trial and error with a much less organized app that essentially does the same thing, which has always been very popular for topped devices, called Titanium Backup.
Finally, when you're done blocking everything you want to block, hot the menu button (top right) and clear the data of disabled packages! VERY good app overall in my opinion, beat $1.50 spent in a long time!

How to disable/adjust the background task limit?

My background with android is long and rocky.
A long time ago in a galaxy far away, I had a Samsung Galaxy S, then a S2.
I can remember a Google Nexus phone in there somewhere.
Then at some point I switched over to Windows Mobile for many years.
A couple of hears ago I came back to android with a Samsung Galaxy S8+ and I hated it.
Recently I upgraded to a OnePlus 6T McLaren and here I am.
I had been expecting to see android happily use up 7, 8 or even 9GB of ram before the background task manager would begin to kill tasks.
Except that I seldom saw android use much more than 5GB of ram.
And worse, background tasks were being killed on a regular basis.
Widgets would stop working overnight, or even in just a few hours.
Spotify would close while a playing a playlist.
A quick search on XDA reveals that many users believe that Android will just use up as much ram as your phone has.
However, that is simply not true.
And so, I began my quest to have Android use as much ram as the phone could provide.
In my case, 10GB.
- I understand that there is an inherent trade-off between keeping background apps running and battery usage. I can live with extra battery usage in exchange for keeping my widgets running or Spotify running for an entire playlist.
- I realized very quickly that in order to achieve the results that I was looking for that the phone would have to be rooted. So rooting was one of the first things that I did.
Step 1.
I started with the basic stuff that a quick google search would provide;
- Settings -> Battery -> Battery Saver (off)
- Settings -> Battery -> Adaptive Battery (off)
- Settings -> Battery -> Battery Optimization -> widget app (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Spotify (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Deep Optimization (off)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Sleep standby optimization (off)
- Settings -> Apps -> Widget app -> Battery -> Background Restriction (app can use battery in background)
- Settings -> Apps -> Spotify -> Battery -> Background Restriction (app can use battery in background)
This helped but not enough to make the widgets or Spotify usable.
Step 2.
I supposed that my specific background tasks that I wanted to keep running were being killed because of the many other apps that were running in the background.
I searched for and found Tomatot DeBloater scripts for the Oneplus 6.
Excellent! Just what I was looking for.
I chose the Tomatot-Debloater-OOS-Light-2.3.zip and installed it.
This helped some more but not enough to make the widgets or Spotify usable.
Step 3.
I realised that there were still some apps running in the background that I didn’t use or want.
So I used Titanium Backup to freeze the following apps;
- Calendar
- Calendar Storage 9
- Contacts (O+)(I replaced with google contacts)
- Dashboard
- Drive
- Face Unlock
- Gboard
- Gmail
- Google
- Google partner setup 9
- Google play music 8
- McLaren AR
- Messaging (O+)(replaced with google messaging)
- OK google enrollment 9
- Oneplus system 1
- Youtube
Perfect! These apps were no longer competing for phone resources with the apps that I wanted to run.
This helped some more but not enough to make the widgets or Spotify usable.
This did make the phone feel faster and smoother.
The phone is much more responsive and fluid to my input.
This made me realize that the apps were being closed not due to a lack of phone resources, but a background task manager being aggressive.
Presumably for battery saving purposes.
I changed my focus to adjusting that background task manager.
Step 4.
Enable the recent screen ‘LOCK’ on the widget app and Spotify.
This didn’t do anything for me.
Everything that I’ve read on it says that it just stops the task from being killed when you click on kill all tasks.
The lock doesn’t lock the task from being killed by the background task manager.
Step 5.
Further google searching led me to believe that the OEM kernel was limiting background tasks.
I choose ElementalX-OP-3.09 and the EX Kernel Manager.
I had to read a lot of google university material to make any sense of the settings in here.
I’m not sure that I fully understand even now.
Eventually, I ended up with the following settings;
Memory
- Adaptive Low Memory Killer (disabled)
- dirty ratio (20)
- dirty background ratio (5)
- min free kbytes (12398)
- vfs cache pressure (100)
Memory -> Low Memory Killer
- apply on boot
- Foreground app (72mb)
- Visible apps (90mb)
- Secondary server (108mb)
- Hidden apps (200mb)
- Content Providers (587mb)
- Empty apps (783mb)
This helped a lot.
This almost made the phone usable to the state that I wanted.
But the widget and Spotify would still stop running overnight and by morning the apps would have to be reopened to get them to run again.
At least the apps would run most of the day without being killed.
Still not the behaviour that I expected from a phone with 10GB of ram.
Ram usage was still not going much over 5.5Gb even if I opened up many apps at once.
Can I ever get ram usage up to the 10Gb that I have?
Step 6.
The last thing that I tried yesterday afternoon was to increase the background task limit in the build.prop.
ro.vendor.qti.sys.fw.bservice_limit=5 (changed it to 60)
ro.vendor.qti.sys.fw.bservice_age=5000 (changed it to 10000)
Yes, I know that I am on PIE and there isn’t supposed to be any effect.
No, I don’t know yet if this had any effect.
I am hopeful.
The widget app didn’t close last night, but Spotify did.
I am getting closer!
This is the best that I could do on my own without asking for help.
So here I am posting my question and asking for help.
How do I get the apps that I want to run to not be killed by the background task manager?
OR
How do I get the phone to use the 10GB of ram?
I feel that I am missing something.
With any luck, one of you smarter persons will be able to point it out to me.
As an aside from all of these changes the phone feels very smooth and fluid.
Except for apps closing that I don’t want to, this phone is a great experience and a pleasure to use.
Apps that I want to run are staying open much longer then before I started.
It’s now just an overnight issue.
And getting the phone to use over 6Gb of ram.
I would suggest that I am 90% happy with it now.
KERNAL: ElementalX-OP6-3.10
ROM: STOCK OOS 9.0.11
PHONE MODEL: 6013 O+6T McLaren

Tomorrow I may try making this change to the build.prop file;
ro.vendor.qti.sys.fw.bservice_enable=true to false
Don't know if it will help or not.

Wow dude, interesting read, i will sign up for notifications from this thread hoping you get your answer because i have the exact same problem but with my work app, throwing it all out of whack and making me a target to big fines (in the $1,000's) and potentially reducing my marketability!
The attached screenies are from before i realized that the app getting killed in the background is what causes the problem (I've left it in the foreground HOURS a few times and it works perfectly!)

UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...

geeksquad2 said:
UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...
Click to expand...
Click to collapse
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference

UPDATE:
I am a silly goose.
I broke a cardinal rule while troubleshooting.
I may have had a few too many wobbly pops and made two changes at a time, thus when change was affected, I was unable to determine properly which change caused the affect.
The rule is, "only make one change at a time when testing".
Yes, all of my apps stay open all the time.
I am getting the behaviour that I was looking for.
However it wasn't necessarily changing the build.prop bgservice_limit from 60 to 120 that did it.
Let me back up a bit.
Earlier I had suggested that locking an app to the recent screen didn't do anything for me, and that in my reading it only locks the app from being killed by you when you try to close it manually.
However in reading up on the oneplus framework-res.apk I found a reference to an oneplus whitelist of apps that will never be killed, and a reference to the recent screen app lock that suggests that oneplus will add a locked app to the whitelist and not kill it.
In the course of a single day, I had inadvertently edited the build.prop and locked the widget app to the recent screen thus breaking the one change at a time rule.
So the next morning and the following days when all apps were staying open I attributed it to changing the build.prop not realizing that it could also have been the app lock.
Last night I realized my mistake.
I unlocked the widget app from the recent screen and went to bed.
When I woke up this morning the widget app was not running for the first time in days.
Also the notifications that I was receiving about the widget app consuming excessive battery have stopped.
It would appear that I was wrong in my earlier observations regarding the app lock mechanism.
It appears to be very useful for keeping apps running all the time.
Did changing the build.prop have any affect on keeping apps open?
Maybe?
I have noticed that my battery life has gone for a complete ****.
I can barely get 24 hours out of the phone.
Worse is that it doesn't matter if the screen is on or not, battery usage remains the same.
i.e. with the screen off and the phone put down, battery life appears to be used at the same rate as when the phone is in use.
I had expected the battery life to be not as good, but I didn't expect it to go to for a **** that badly.
There must be a balance between aggressive app management and acceptable battery life.
The phone didn't display this behaviour until I changed ro.vendor.qti.sys.fw.bservice_enable=true to false.
I think that today I will change ro.vendor.qti.sys.fw.bservice_enable= back to true and observe the battery tomorrow.

kantjer said:
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference
Click to expand...
Click to collapse
I think that ro.vendor.qti.sys.fw.bservice_limit= and ro.vendor.qti.sys.fw.bg_apps_limit= are essentially the same thing, except for android versions.
ro.vendor.qti.sys.fw.bg_apps_limit= is for Android 7: Nougat and below.
ro.vendor.qti.sys.fw.bservice_limit= is for Android 8: Oreo and above.
Someone more knowledgeable than me should chime in here though.

Do you think any of this could have to do with the way the phone keeps disabling push in Gmail? (Every other day I need to set my O365 exchange in Gmail back to push because it automatically changes to the default of checking every 30 mins.)

Any conclusion?

Did you guys manage to solve this issue please by editing the build prop?

Latest smurf kernel rc14b seems to have solved the RAM management issue. I haven't had any apps closing in background since using it.

thank you for the thread!

What did you find in the end?
How did you set this ?
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000

So what's the verdict on the buildprop edits? Do they make a difference?
I notice that sometimes my on-going weather notification doesn't update, or gets killed off. I also have an app that controls rotation per app, and that also seems to stop doing it's thing after a while.

Just want to share. If you are rooted with Magisk, try appsystemizer module. System apps don't get killed by oneplus as aggressively. Tried it with accubattery and it works.

I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.

scloss84 said:
I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.
Click to expand...
Click to collapse
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY

popy2006 said:
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY
Click to expand...
Click to collapse
I'm actually Oneplus 6, OOS 9.0.9.
I also read that it doesn't work on Android 10 because magisk doesn't mount /system in Android 10, but there is a magisk module workaround that you can use. And hopefully magisk will update in the near future to fix that. Just google "Android 10 can't edit build.prop" and you'll find heaps of info.

This is what I have in my build.prop file and it seems to help. I have Oreo it works great on my phone I don't know about later versions of Oreo.
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_age=5000
ro.vendor.qti.sys.fw.bservice_limit=5
ro.sys.fw.bg_apps_limit=64