Database Develop

Auto Memory Manager 1.0.3

Hi guys. Just wanted to plug my app here. It's based on the work that has been happening in the "auto task killer" thread.
In a nutshell this app lets you configure Android's internal memory manager to help define when to shut down different types of apps.
Features:
- Presets and custom settings
- Works with Android 1.5+
- Sliders for easy setting of the apps.
If you have any questions just pop me and email or hit me up on twitter. This is very much a work in progress so I'll be updating it fairly often. So give it a try (QR code below) and I hope you find it useful.

Requires root access
Another good reason to root my Hero. I'd probably do that before upgrading to 2.1.

sanderg said:
Requires root access
Another good reason to root my Hero. I'd probably do that before upgrading to 2.1.
Click to expand...
Click to collapse
Sorry. forgot to mention that it requires root. If you are rooting then I would recommend flashing a 2.1 ROM since that's faster than the 1.5 ROMs. There are caveats of course since not everything is working perfectly on the 2.1 ROMs but it's working good enough for me. Call me shallow but I LOVE live wallpaper.

Could you perhaps give more information? I have set it to mainly 120MB (to test) and nothing is happening. Does it happen every x mins or something?

G8D said:
Could you perhaps give more information? I have set it to mainly 120MB (to test) and nothing is happening. Does it happen every x mins or something?
Click to expand...
Click to collapse
This works differently than a task killer. What you are doing is setting thresholds for each application type. So if you set the threshold for Empty Apps to be 120MB then Android will kill these apps when there is only 120MB left. This would be most of the time.
However these thresholds are soft settings. So if Android needs to start an app/service or the user manually initiates an app/service then these will still start as normal.
This is my understanding of how it works. (I am not an expert regarding this.) However I have noticed that Android is still starting up certain apps that seem to be useless and I haven't used either e.g. Amazon MP3. This could be something to do with the out-of-memory priority of the app. (will need to investigate this)
For me at least, I have found that using a task killer to kill all apps after you apply your settings works the best. But the app should keep things much tidier in terms of memory usage.
As mentioned above these are soft settings and I have tried setting all bars to 120MB and everything still works fine. You may or may not get the same experience but these are soft settings so the worst that could happen is that you have to reboot your phone and revert to the default setting.
In the next update the settings will be saved after reboot but you will still able to go into the app to change the setting anyway.
I hope I answered your question.

[[Speed Improvements]] Brainstorming & Testing Thread!!

Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets​
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2​
Difficulty Easy - Controlling app 'net Access​
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3​
Difficulty Moderate - SD cache/readahead tweaking​
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4​
Difficulty Moderate - Overclocking​
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5​
Difficulty Advanced - How Android Manages Memory/apps​
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6​
Difficulty Advanced - Managing Apps that auto-start on boot​
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.

Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any TOPAa-specific tweaks that others should be made aware of!

Update to this - I changed around how topic 4 is done. Feel free to re-read that section.

Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?

metho88 said:
Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?
Click to expand...
Click to collapse
For the pm disable stuff? If you find an app that does it, more power to you. I want to control Android directly, hence the reason I went with a script that utilizes that concept. The pm disable stuff is obnoxious I know - so if you do find an app that'll do it for you, have at it. I didn't want to add any more apps into the mix if it wasn't necessary .

Rhod400 in startup.txt
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?

1edge1 said:
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?
Click to expand...
Click to collapse
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...

arrrghhh said:
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...
Click to expand...
Click to collapse
yeah i do use the startup for topaz. Was just wondering. haha. thanx for clearing it up

[Q] CM9 : Permanent Background process limit

Hi guys,
just one question, search for it but didnt found a solution jet.
I´m using CM9 , latest version ofc. Under Settings -> Developer options -> Background process limit there is some options to choose. I´m unsig "At most, 2 processes". But, after rebooting the device, the option reset itself to "standart".
My question is : Is it possible to set this command as an startup file in the init folder, that after every restart it will be "2 processes" instead of "standart" ??
I hope to get some help, thanks !!!

saphirrot said:
Hi guys,
just one question, search for it but didnt found a solution jet.
I´m using CM9 , latest version ofc. Under Settings -> Developer options -> Background process limit there is some options to choose. I´m unsig "At most, 2 processes". But, after rebooting the device, the option reset itself to "standart".
My question is : Is it possible to set this command as an startup file in the init folder, that after every restart it will be "2 processes" instead of "standart" ??
I hope to get some help, thanks !!!
Click to expand...
Click to collapse
Just a thought but I doubt you can as the phone needs more than 2 process to boot up?.....so I'm guessing this won't ever be a persistent or init.d feature,
Sent from my GT-I9000 using xda premium

Bro, noone said that i want to apply this while booting to phone up...

saphirrot said:
Bro, noone said that i want to apply this while booting to phone up...
Click to expand...
Click to collapse
It was merely a thought
Sent from my GT-I9000 using xda premium

I´ve the same problem....
But I´ve an idea. This app runs an sh file on startup: search in google play for Autostart (root).
but I don´t know the command to set the background process limit... And I don´t know if theres any...

Or can somone say where th Backround Process Limit is saved?

Pretty interesting feature that saves lots of memory and makes the devices work better; i have been using this feature on my Samsung Galaxy tab 2 7, and still setting it up. Makes thing runs better although sometimes you can kill apps that you want to be running in the background.
Any ideas on his question?.

shinydesert said:
Pretty interesting feature that saves lots of memory and makes the devices work better; i have been using this feature on my Samsung Galaxy tab 2 7, and still setting it up. Makes thing runs better although sometimes you can kill apps that you want to be running in the background.
Any ideas on his question?.
Click to expand...
Click to collapse
I'm setting up phones for other people and I have found out that it is the single feature that probably speeds up -the most- most of the phones especially those that are low in the memory department.... Unfortunately to most of the people (that I'm helping with their phones) it is impossible to set this option each and every time that their phones boot so I thought maybe I'd add it a as init.d feature or -maybe so that not to disrupt the booting process- as sth which would run after a timer (which -say- lasts for a minute) runs it's course.
My only question is if anyone know how to enable this feature programmatically (e.g via shell)...
(sorry for the thread ressurection btw)

Two years old unsolved thread and no answer yet... what a shame ...
Greetingz.

this app works for me, there's an option in settings to stop background processes http://forum.xda-developers.com/xposed/modules/recent-app-cleaner-t2734053 although you need to be rooted and have Xposed Framework.

Finally figured this out, man was it annoying.
I need it for my 2012 Nexus 7 running Android 5.1.1
It was running slower than molasseses until I changed the data partition to f2fs (make sure you have a kernel and ramdisk that support f2fs!) and enabled this tweak.
It can be done with root access with a single command.
service call activity 51 i32 x
Where x is the number of background processes you want.
If the API changes in the future, it's easy to look it up again.
http://grepcode.com/file/repository...4.4_r1/android/app/IActivityManager.java?av=f
Look for the line with SET_PROCESS_LIMIT_TRANSACTION
Then just extrapolate that info to http://grepcode.com/file/repository...ERSION/android/app/IActivityManager.java?av=f
Replacing DESIRED_ANDROID_VERSION with the version you're interested in.

Activity number has changed for android 8 and 9
For now the end of 2019, android 8,9 has been the major platform for recent user's handy phone, the command for those use:
```
service call activity 51 i32 x
```
can not be exactly do what you will see in android8 and android9, the major issue was for the activity number '51' must to set it to 42 to Oreo and 47 for Pie, see github issue link (https_:_ //_github.com/flode/SetAndroidProcessLimit/issues/5#issuecomment-546690235 )
That means you should use: `service call activity 42 i32 x` for Oreo and 47 replaced for Pie.
Hope for adding new activity number for Android10

Check that thread for reference:
https://forum.xda-developers.com/showthread.php?t=1494530

[Q] Ram issues, often less than 256 MB free

The title is the real starting place of my issue. Out of the devices 2 GB, 1.5 GB is the average amount that is used and its really starting to impact the performance of the phone. The few things that I have tried never seem to be a more permanent solution. My Moto X is Rooted with a Sunshine Unlocked Bootloader.
Normally on my phone I have the following running in background:
tasker & Related plug ins
Xposed framework
Some widgets( Evernote, weather & Calendar)
Here is what I've tried so far:
Greenify, to help manage what apps are operating in the background.
Uninstalled a large number of my tasker plug ins
Reduced the number of Xposed plugins that I have running
Reduced the number of widgets that I have my launcher running
Here are my ideas that I have left but I don't know what it will fix.
Find an app launcher with lower RAM requirement that still meets my needs. Currently using an old version of GO Launcher I like.
Wipe the phone and start over with the stock AT&T 4.4.4 ROM.
Another possibly related issues is that I've been having apps crash often, like Touchless controls and Contacts, but when I try and send the bug report it has my own address listed instead of Motorolla's.

Icon000 said:
The title is the real starting place of my issue. Out of the devices 2 GB, 1.5 GB is the average amount that is used and its really starting to impact the performance of the phone. The few things that I have tried never seem to be a more permanent solution. My Moto X is Rooted with a Sunshine Unlocked Bootloader.
Normally on my phone I have the following running in background:
tasker & Related plug ins
Xposed framework
Some widgets( Evernote, weather & Calendar)
Here is what I've tried so far:
Greenify, to help manage what apps are operating in the background.
Uninstalled a large number of my tasker plug ins
Reduced the number of Xposed plugins that I have running
Reduced the number of widgets that I have my launcher running
Here are my ideas that I have left but I don't know what it will fix.
Find an app launcher with lower RAM requirement that still meets my needs. Currently using an old version of GO Launcher I like.
Wipe the phone and start over with the stock AT&T 4.4.4 ROM.
Another possibly related issues is that I've been having apps crash often, like Touchless controls and Contacts, but when I try and send the bug report it has my own address listed instead of Motorolla's.
Click to expand...
Click to collapse
have you tried flashing a stock firmware through RSD LITE? have you tried doing a hard reset? from stock recovery? your problem sounds like that a 3rd party app has screwed up your phone... And please dont use 3rd party launchers... They cause alot of problems.

whizinc said:
have you tried flashing a stock firmware through RSD LITE?
Click to expand...
Click to collapse
I was hoping to use this as a last resort
whizinc said:
have you tried doing a hard reset?
Click to expand...
Click to collapse
When you say hard reset do you mean a reboot? Factory Reset? I'm not 100% sure what your talking about.
whizinc said:
your problem sounds like that a 3rd party app has screwed up your phone... And please dont use 3rd party launchers... They cause alot of problems.
Click to expand...
Click to collapse
If you asking to me stick with stock launcher I don't think I can do that. There are a lot of features the stock launcher is missing like Folders that sync to folders within the App Draw, just the way they display an open folder, the ways you can organize the app folder, how you hide apps you don't use, ie keyboards and the visuals associated with the uninstall process. But if you have suggestions on how to resolve some of the feature differences I'd be interested to hear.

Icon000 said:
The title is the real starting place of my issue. Out of the devices 2 GB, 1.5 GB is the average amount that is used and its really starting to impact the performance of the phone. The few things that I have tried never seem to be a more permanent solution. My Moto X is Rooted with a Sunshine Unlocked Bootloader.
Normally on my phone I have the following running in background:
tasker & Related plug ins
Xposed framework
Some widgets( Evernote, weather & Calendar)
Here is what I've tried so far:
Greenify, to help manage what apps are operating in the background.
Uninstalled a large number of my tasker plug ins
Reduced the number of Xposed plugins that I have running
Reduced the number of widgets that I have my launcher running
Here are my ideas that I have left but I don't know what it will fix.
Find an app launcher with lower RAM requirement that still meets my needs. Currently using an old version of GO Launcher I like.
Wipe the phone and start over with the stock AT&T 4.4.4 ROM.
Another possibly related issues is that I've been having apps crash often, like Touchless controls and Contacts, but when I try and send the bug report it has my own address listed instead of Motorolla's.
Click to expand...
Click to collapse
You should check the running apps in the settings also check the cached background processes.
You'll find the culprit there.
Post screenshot if possible.
It's probably Facebook or something like that

adity said:
You should check the running apps in the settings also check the cached background processes.
You'll find the culprit there.
Post screenshot if possible.
It's probably Facebook or something like that
Click to expand...
Click to collapse
What would you say is a good threshold to use to consider if an app is a problem? Would you say more than 25MB? 50MB?
A screen shot isn't going to be possible until after 7 pm

Icon000 said:
What would you say is a good threshold to use to consider if an app is a problem? Would you say more than 25MB? 50MB?
A screen shot isn't going to be possible until after 7 pm
Click to expand...
Click to collapse
Apps like chrome consistently use 100mb..
Otherwise 50mb
Also post screenshots man

Icon000 said:
I was hoping to use this as a last resort
When you say hard reset do you mean a reboot? Factory Reset? I'm not 100% sure what your talking about.
If you asking to me stick with stock launcher I don't think I can do that. There are a lot of features the stock launcher is missing like Folders that sync to folders within the App Draw, just the way they display an open folder, the ways you can organize the app folder, how you hide apps you don't use, ie keyboards and the visuals associated with the uninstall process. But if you have suggestions on how to resolve some of the feature differences I'd be interested to hear.
Click to expand...
Click to collapse
Take that last hope..Rsd lite your stock firmware and all your problems will be vanished.. Im sure..
A hard reset is a reset which you do thorough the Bootloader of your phone without booting to actual android home screen... Like you open your Boot loader by pressing appropriate keys and select recovery and Erase Cache and Factory reset from there... Google Hard reset and learn about it. Its really important to learn about hard reset if you own an android device..
As far as your launcher is concerned i can understand... And i dont really think that the launcher might be causing the problem... You just need an RSD LITE flash to completely wipe your phone and bring it to the factory state and make it completely fresh... I bet rsd lite flash will fix your problem because it erases the whole device and reflashes everything like boot,modem,system,kernal etc... GO FOR RSD LITE FLASH... and please take extra precautions before Flashing through RSD LITE.. because its risky if you do it in the wrong way.... Make sure to find the exact firmware of your phone which matches the carrier.. and also check the bootloader version of the firmware.. DOWNGRADING THE FIRMWARE WILL BRICK YOUR DEVICE PERMANENTLY.. so always upgrade or flash the same firmware as you have now.. Take extra precautions.. Good luck..
Sent from my ghost using Tapatalk

It is Linux based, free RAM is wasted RAM. The system will put stuff into memory as needed, and remove it as needed. The system tries to keep as much stuff in memory as possible to improve performance so it doesn't have to put it back into memory if you launch it again. It is how the Android memory killer works, and the kernel is what controls the free memory.

imnuts said:
It is Linux based, free RAM is wasted RAM.
Click to expand...
Click to collapse
if this is true why do i have more performance issue when the ram is full? I have to wait for the phone to respond to the touches on the screen.

Icon000 said:
if this is true why do i have more performance issue when the ram is full? I have to wait for the phone to respond to the touches on the screen.
Click to expand...
Click to collapse
If that is the case, then your device is likely not freeing memory properly. Either an app is not closing properly, or you have a lot of background apps running that can't be freed from memory, or you have a rogue app killing your phone.

As he said, "free memory" will always be very low.
This is part of why people freaked out over vista... As modern kernels do, it was using most available ram for tasks that might happen because this memory can be cleared instantly. But vista actually reported this memory usage, and people freaked out, not being used to the concept. I believe they adjusted how memory was reported in 7...
Give this a read
http://serverfault.com/questions/85470/meaning-of-the-buffers-cache-line-in-the-output-of-free
If you have a terminal emulator the command "top" will show you memory usage by category so you can see not only how much is free, but how much COULD be free at a moments notice if needed. This is what you want to know.
"atop" is another version of top, it reports slightly different statistics and can be a little more readable...(it may be htop not atop, if one doesnt work try the other. They both exist but only one is prepackaged and... I forget.)
You should also be able to look at processes to see what is using up significant amounts of memory....

Over-aggressive background task and notification killing on Honor 7 Lite (NEM-L21)

I'm on Honor 7 Lite (NEM-L21C432B356), I love the phone hardware itself but the stock OS (EMUI 5.0.2) is driving me crazy. Background tasks get killed really quickly and often notifications get deleted before I can even see them. I've tried factory reset and everything I've found on Google to no effect.
This isn't about the known push notifications issue. Notifications do work, but then they usually disappear almost immediately. I sometimes hear the notification tone, pick up the phone and unlock it to see a notification icon in the top bar for less than a second and then it's gone. Or if a notification comes in when I'm using the phone, I might see the notification in the list briefly and then it just vanishes.
Background tasks like Twilight or JuiceSSH with statusbar icons seem to get killed really aggressively. This seems to happen more to some apps than others, but I can't figure out any common denominator for the apps. It happens to both online and offline apps.
I've disabled everything related to Huawei's task killing/battery saving settings and added all apps to all exception lists that I've been able to find. Free memory seems to hover consistently around 500-700MB, I don't think I've ever seen free memory dip below 500MB.
It's hard to get good memory stats out of Android 7 without root, but it almost seems like the OS is pre-emptively keeping that 0.5GB of RAM free in case some foreground app wants a lot of memory, and it's willing to pre-emptively kill background tasks, even ones with status bar icons, to achieve it. I don't know if this is true, but Huawei doesn't seem to trust Android's own memory management much in general, with all their dumb "memory cleaning" and "battery optimization" stuff.
I'm at my wits' end here. I rely on seeing all notifications to keep up with reminders and other things, and I need background apps to stay there when I multitask. Custom ROMs aren't really an option, since I want everything on the phone to Just Work without any extra fiddling and hassle and I can't risk my only phone. I appreciate custom ROM developers' work though.
Thanks in advance for any useful answers.

On the P9 Lite with 2 GBs of RAM they are using more than 1.5GBs of zRAM which is crazy. I don't think that's needed at all. If your phone is rooted, you can install a Magisk module called Swap Torpedo to disable swap and maybe change some LMK values. Also you can disable the Power Genie app if you don't have root access.

erayrafet said:
If your phone is rooted, you can install a Magisk module called Swap Torpedo to disable swap and maybe change some LMK values. Also you can disable the Power Genie app if you don't have root access.
Click to expand...
Click to collapse
I'm not rooted, because unlocking the bootloader and rooting would trip SafetyNet, which I can't afford because I need some apps that depend on SafetyNet and I don't want the whole cat and mouse game with Magisk trying to keep ahead of Google on that.
Thanks a lot for the Power Genie tip (called Power Genius on my phone), I haven't seen that mentioned anywhere else and will try it out. I hadn't noticed that process at all since it's running under AndroidSystem.
Edit: unfortunately the "Disable" button is grayed out on Power Genius, so disabling it doesn't seem like an option. I can stop it manually, but I assume it'll just get autostarted again. I don't seem to have permissions to hide it from adb shell either.

Same problem here (NEM-L51C432). It aggressively kills all background applications. This prevents multitasking. It is annoying to see a lot of RAM is free and will not be used. RAM is there to take use of it and not to keep it free.