Database Info

Making the HERO FASTER project

howdy peeps i have an idea of how maybe we could solve the speed issues with the hero rom but my programming skills have not reached java as of yet, i am learning as we speak, but heres my idea...
im thinking of a program that sits in the background that basically controls the priority of certain programs running on android like rosie.apk.
for instance if the home button is pressed not only is the rosie apk brought to the front but is given more cpu priority over other applications running which in affect should speed up delays. a bit like when you do it in task manager on windows.
i am trying to figure out how to write this with java and the android sdk but wondered what your views are on this and if anyone can actually implement this quicker and better than i will be able to lol
look forward to hearing your views

I think the problem with this is that processes in Android drop in and out of memory. So, for example, Rosie will be dropped out of memory to make way for the browser and a heavy web page. Applications that are dropped have their state saved, so when you go back to them you are taken back to the position you were in. However, big processes like Rosie take a noticeable time to get back to where they were.
I think the key to speeding up Hero is increasing "memory" so that processes don't need to get dropped. Hence why I've been looking for that elusive perfect Compcache build. If we can make 100Mb of usable memory work more like 200Mb or more, then that might do the business.

ahh i see, but would not doing this speed up the pick up time of the for instance rosie apk?i can see where you are coming from because if we had more memory we would not need to drop the rosie out of memory, im thinking tho if you had both more memory and a process manager it could be some speedy stuff...hmm

Changing process priority probably wouldn't help, because (using Rosie reloads as an example) there isn't a process to prioritise - Rosie isn't actually there any more to give increased priority to. Maybe you could give priority to the process that does the reload but the subjective speed increase would be I think negligible, because loading from sd or memory is going to depend on the speed of the memory, not how much processor grunt the reload process gets.
A nice idea but I think the way Android works would make it problematic.

cool cheers for the insight into android glad someone knows there stuff lets hope someone comes up with a working solution

hmmm. also i think that android itself is doing it's job not sooo bad. i can't imagine that loading back the rosie process is not getting enough cpu time, that would be a huge design failure ...
correct me if i'm wrong, but i really hope, that android is intelligent enough to do this on it's own.

Has there been any optimization of hero or just a straight port?

bademasta said:
hmmm. also i think that android itself is doing it's job not sooo bad. i can't imagine that loading back the rosie process is not getting enough cpu time, that would be a huge design failure ...
correct me if i'm wrong, but i really hope, that android is intelligent enough to do this on it's own.
Click to expand...
Click to collapse
but what ur missing is that hero is not built for the magic with 192mb of ram is it now? so somewhere u are guna have to make some OPTIMIZATION

Android is very good at managing resources and applications...
Having developed some Android applications, I can't really think of a good way to improve on the current system. Perhaps all I could suggest is running a Manual Process Manager... and closing applications/Services which you no longer are using but are still running.
A quick tip would be, when you are running an application and no longer need it... use the back button, not the Home button.
If you use the Back button, the application will Destroy... the Home button will 'Pause' the application and assume that you will want to come back to it later.
Android maintains a chain of open Activities, you can keep opening new Activities and it will maintain the old one you were running in a 'Paused' State. If you keep moving forward and opening new applications, but never go backward... you will end up with a lot of things running... so each time you open something, it may need to free up some memory by closing an application that has not been used for a long time which is still in a paused state.
You could speed things up in that scenario by running a task manager and killing processors... or I usually just reboot my phone...
Here is a diagram which shows the Life cycle of applications. Services have a slightly different Life cycle.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can read more here
Hopefully this info helps, sorry for wandering a little bit bit off topic...

Hello,
Before tweaking Android to try to run Rosie properly, perhaps we can try to optimize Rosie ?
For example, in the first roms we found here, Rosie.apk was about 4Mo. Now in the Qtek 1.2 swap, it is only about 690Ko. Here, we can find a 330ko version.
But perhaps some people can do the same job to optimize all the UI of Rosie, i think about all the widgets ,the browser, the keyboard ...
The more lighter UI Rosie is, the less memory Rosie need ?
Scargoll.

I did that but it's not finish yet. i just use a png optimizer so i can make every apk a bit smaller but my problem is that i don't really know how to sign an .apk file
when i know how to do that will have an fully working hero rom with compcache about 60 mb ...

MarcoNieddu said:
I did that but it's not finish yet. i just use a png optimizer so i can make every apk a bit smaller but my problem is that i don't really know how to sign an .apk file
when i know how to do that will have an fully working hero rom with compcache about 60 mb ...
Click to expand...
Click to collapse
Good news !!!
I don't know how to sign apk files, but i found this, perhaps this can help ?
http://www.anddev.org/signing_your_apk-application_for_release_keytooljarsigner-t3069.html
Scargoll.

I follow this tutorial more than 3 times now. when i want to install the signed apk to my phone there ist always an error -- > can't install ...

You're trying to install an app that's already running. You need to flash it with an update.zip+script or copy it with ADB when your device is in fastboot.
Ill see if I can optimize rosie's images, I brought down the HTC_IME size down by 25% just by optimizing the png images.
Sizes of the IMAGES in rosie.apk, not total size.
141 KB smaller than the original. Good result if I say so myself!

bump.
No one wants to continue? I'll optimize any image I can find and reduce the size of all images by 20% as well ending up with a probably faster running phone

Can you post directions on how to optimize???

A lot of people have already done some work trying to optimise Rosie. Speaking personally, the ne thing I always do when I install a new Hero build is to push the Rosie from
http://forum.xda-developers.com/showthread.php?t=532822
onto the phone. It's the stablest I've found that manages to do everything in a small-ish footprint without making it crash prone and buggy. There's a 300-odd K one in the same thread that I've never been able to get to work. There's also a 300-odd K one that came with Drizzy's 1.2 Hero release which was buggy - his next release took the file size back up to 3.5Mb!
tl;dr: there are already optimised Rosies, but not all of them work particularly well.

Has anyone been able to tweak the drivers to get slightly better fps or anything?

briggs81 said:
Has anyone been able to tweak the drivers to get slightly better fps or anything?
Click to expand...
Click to collapse
I wonder this too.

sibbor said:
I wonder this too.
Click to expand...
Click to collapse
My main phone is an HTC device running Android on sd card.. developers were able to get the fps to run up to 24, which is about 6-7 lower then a stock Magic.. not bad.. for a 2 year old phone!
Perhaps when other things are going smoothly someone with that type of knowledge will be able to play with driver software or something.
I think right now, Magic users get about 27-29 fps.

What the hell is wrong with the memory (RAM) usage on this phone?

Even my desire with latest htc sense and gingerbread I had at least 100mb free ram. With this phone I barely have 50mb free, the phone is slow, skinned launcher pro is laggy and when I try to see which app is eating so much, android system is at the top with ~70mb of usage. If I add all the other apps there I can't even reach 200mb in total, where is the rest of 300MB?
I assumed that aosp ROMs should be smooth and without problems, but my HTC Sense was way much more responsive!

Dunno but I have at least 465mb free on my SGS2

psp888 said:
Dunno but I have at least 465mb free on my SGS2
Click to expand...
Click to collapse
Well that is great, but not really a helpful response. Still, nice phone you got there.

I'm not running Launcher Pro (yet), but with stock launcher I've got 151mb free.
I'm so pleased with the performance of the stock launcher in GB that I was afraid to switch to LP.
With all of these things though, there are so many variables that your mileage will differ greatly from everyone else's based on the # of apps, widgets, etc.
But right now, mine's humming right along.

756MB free on my NS4G

Myself, and others on the NS4G have all agreed, launcher pro hates this phone and runs terrible.. ADW is my preferred choice now.

I'm running ADW Launcher EX on my NS with 2.3.4 and I usually have around 145mb free. Gingerbread seems to be handling system resources well on my device, I rarely experience any lag. Are you rooted? If so you could do a full wipe and reinstall gingerbread fresh. That may straighten things out for you.

Are we talking about the same things here?
RAM = running programs
vs program storage?
The NS4G has 300mb of RAM with 1GB of program storage.
My NS4G averages 150mb of free RAM and storage hovers around 750mb.

I have about 174MB free ram on stock 2.3.4 if that helps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I've got about 130 free with stock rom/launcher.
Sent from my Nexus S 4G using XDA App

I don't think its a problem with this phone specifically, I think it has to do with gingerbread itself. As you can see in my sig (have to update it these days) I'm coming from an HTC Desire and if I ran an AOSP gingerbread ROM I was having the exact same issue with launcher pro. But the RAM memory was not there, I had above 100mb free all the time. Desire has the same amount of RAM as NS.
The free RAM displayed in running services is not accurate, if you want to see ur free RAM download quick sytem info or system info widget.
Here's a pic with my usage without browser running (just closed it, otherwise I would've had less then 50mb free):

On my NS4G, running the OpenSoju rom, and Launcher Pro, it is running like butter:

I think Gingerbread runs more like Windows 7 does on the PC.. If there is free RAM, it's going to use it to make the OS more responsive.. If demand rises for app or game usage it should (in theory) start freeing up RAM to compensate.

Exploring this further, there is definitely some conflicts of usage depending on what you use to view RAM.
Gingerbreads app management tells me I have 136M free.. While a system info app tells me 77M available.

I killed every single app I could see in quick system info and reached almost 150 mb free (for real, not the usage u see in running services) and even then launcher pro is laggy. When going into sense-like preview (pinch to zoom out) and sometimes even scrolling through screens it feels laggy, its certainly not as responsive as it was with my HTC Sense ROM on the HTC Desire.
ADW also feels laggy.
And I can confirm that froyo works just fine, this is a screw-up from google. And their launcher sucks!
Edit: Ok I removed all the 4x4 widgets and the phone is now ok, it runs fine. Apparently if you have a lot of widgets running on several home screens it will lag. Again, on froyo there is no such problem
I will try MIUI today and report back.

if you have a problem with memory handling try searching ANDmemory in xda. its still in beta but it does a pretty good job.

styckx said:
Exploring this further, there is definitely some conflicts of usage depending on what you use to view RAM.
Gingerbreads app management tells me I have 136M free.. While a system info app tells me 77M available.
Click to expand...
Click to collapse
Are you running a custom rom? I want that battery indicator.

djorijun said:
756MB free on my NS4G
Click to expand...
Click to collapse
Talking about RAM not ROM

I limited to 3 screens for now, a main screen and 2 side ones filled with 2x2 launcher pro widgets. It feels much smoother now, but the RAM usage is still big.

psp888 said:
Dunno but I have at least 465mb free on my SGS2
Click to expand...
Click to collapse
Then what are you doing in this forum dummy.

One XL Rogers LTE Ram size

Hi everyone,
According to XL Rogers specs, I might have 1 gig RAM but I only have 671 Mg.
Is it some king of Rogers limitation?
Can someone having a Rogers One XL release can confirm that?
Annoying because even with a few application in process, Sense is randomly restarting because, I think, of a lack of memory. It often happen right after using a browser for few minutes
Thanks!

I noticed that when looking at ATT One X
Would like to know as well. WTF..

i could be wrong but i think it's because the memory is shared with the gpu.

Weird because it shows 1Gig in parameters/hardware Info.
But still 671 in memory management and benchmark utilities...

That is normal. Some parts of the memory are reserved (for OS, GPU etc.) and are not accessible for all apps. For example, my Galaxy Nexus has 1GB RAM, but only "693 MB" is displayed under "about phone". That has always been the case for all Android phones, although how much of the memory is reserved differs between phones/ROMs.

tsekh501 said:
That is normal. Some parts of the memory are reserved (for OS, GPU etc.) and are not accessible for all apps. For example, my Galaxy Nexus has 1GB RAM, but only "693 MB" is displayed under "about phone". That has always been the case for all Android phones, although how much of the memory is reserved differs between phones/ROMs.
Click to expand...
Click to collapse
I wonder why this always comes up when a new phone is released. When people buy a computer with 6 gigs of ram, do they get mad when Windows or OSX uses 2 of it?
It's the same concept here, but this always comes up.

If you run:
cat /proc/meminfo
That should give you all the physical memory available to Android.

Squeak22 said:
I wonder why this always comes up when a new phone is released. When people buy a computer with 6 gigs of ram, do they get mad when Windows or OSX uses 2 of it?
It's the same concept here, but this always comes up.
Click to expand...
Click to collapse
It's not really the same concept, as that has to do with the 32-bit limitation. And yes, people did complaining a lot a few years ago when 4GB RAM started to become really affordable. People rarely complained about that these days, not because they finally understood the issue, but rather most computers are shipped with 64-bit OS now.

tsekh501 said:
It's not really the same concept, as that has to do with the 32-bit limitation. And yes, people did complaining a lot a few years ago when 4GB RAM started to become really affordable. People rarely complained about that these days, not because they finally understood the issue, but rather most computers are shipped with 64-bit OS now.
Click to expand...
Click to collapse
/facepalm
When you load up task manager in windows, it shows how much free memory you have. The amount of free memory is NEVER what your total physical memory is. There is always about a third used for cached data, OS processes, and stupid widgets that you have running on the desktop.
Nowhere did I mention the 32bit limitation, that would be a valid issue.

Squeak22 said:
/facepalm
When you load up task manager in windows, it shows how much free memory you have. The amount of free memory is NEVER what your total physical memory is. There is always about a third used for cached data, OS processes, and stupid widgets that you have running on the desktop.
Nowhere did I mention the 32bit limitation, that would be a valid issue.
Click to expand...
Click to collapse
There's no need to be so rash. He does have a valid point.
cat /proc/meminfo returns the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Whereas the task manager displays 672MB total memory (used+free):

danada said:
There's no need to be so rash. He does have a valid point.
Click to expand...
Click to collapse
150ish meg for ramdisk and another 150ish meg for GPU. Explained away.
This is common on every phone that's ever come out for the last year + with 1 gigs of ram.

Squeak22 said:
/facepalm
When you load up task manager in windows, it shows how much free memory you have. The amount of free memory is NEVER what your total physical memory is. There is always about a third used for cached data, OS processes, and stupid widgets that you have running on the desktop.
Nowhere did I mention the 32bit limitation, that would be a valid issue.
Click to expand...
Click to collapse
That's free memory that you are talking about. Its total physical memory and I and OP were saying. My Windows 7 task manager always shows the actual total physical memory, and that wasn't the case with winxp before either sp2 or sp3 and tons of people whined about that on a daily basis.
The OP's question, however, concerns Android and it doesnt show the correct amount of physical memory on the phone. He is not saying "free memory", which is of course changing all the time depending on running apps.
Sent from my Galaxy Nexus using XDA

I am seeing a total of 970ish MB's on my international htc one x. Currently 709MB used and 267MB free.
I believe some of the RAM is reserved for the GPU and since there are different GPU's in the two models it is probably what makes up the difference in available RAM.

Wondering why the S6 can't hold apps in its memory?

Well, if you have wondered why, I think I may have the answer.
Samsung made a claim that the new Touchwiz is stripped down and optimised for better performance, well, they LIED. True optimisation isn't easy, but another manufacturer did it - HTC. Below are the two screenshots of the respective "Running" app section of the settings and see the difference? 1500MB vs 355MB. 5 times more.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My S6 is running the latest version of Touchwiz, COGA, and the M8 is running a lollipop custom ROM ported from the M9 (sort of). I sincerely hope Samsung will fix this issue, as even the 4GB RAM Note 5 and Edge Plus are also experiencing app shutdowns. What are your experiences? If you have a solution, please share. Thanks!

Agressive memory management and Sh*twiz cached in RAM causing this. Some custom kernels are better than stock, but no fix as of now.

8GB ram is a must for TouchWiz

Again:
the workload of the ram is not the problem!
I'm running a very stripped down TW rom and I never reach a full ram. I am around 80%. The Problem is that the system is killing processes to early, even if the ram is far away from being full. That would happen with any amount of ram.
Yes Samsung should fix this or should have already fixed that issue.

Yeah it f*cking sucks. It's rendering my g watch unusable since it's aways killing the wear app

they didn't do nothing to optimize its almost the only software to eat all the ram.. it was always like this, and now in the s6 it reloads apps.... normal..i had an s3, s4 and now s6, you can have 3 apps in background nothing more....

XxM4tzexX said:
Again:
the workload of the ram is not the problem!
I'm running a very stripped down TW rom and I never reach a full ram. I am around 80%. The Problem is that the system is killing processes to early, even if the ram is far away from being full. That would happen with any amount of ram.
Yes Samsung should fix this or should have already fixed that issue.
Click to expand...
Click to collapse
yes, this ram freeing by killing apps is somehow intentional

According to the samsungmobileuk twitter person there is no issue!
I even sent them video demonstrations. The s6 cannot multi task as well as a 3 year old nexus 4 with less memory.

In my s6 applications running in the background, and it does not kill them
but my Ram is 75% all the time..

There is no reason for RAM to stay empty. It's very normal for an OS whether it be Windows or iOS or Android to use up all available RAM, that's the way it should be.
S6's problem is not that RAM is almost full all the time, which is normal, but that background applications get autoclosed after a short time, which is a kernel setting. My guess is that Samsung does it to save battery rather than RAM, since background apps eat up a lot of battery.

aydc said:
There is no reason for RAM to stay empty. It's very normal for an OS whether it be Windows or iOS or Android to use up all available RAM, that's the way it should be.
S6's problem is not that RAM is almost full all the time, which is normal, but that background applications get autoclosed after a short time, which is a kernel setting. My guess is that Samsung does it to save battery rather than RAM, since background apps eat up a lot of battery.
Click to expand...
Click to collapse
Spot on well said. Have a thanks

samsung will be always like that, i remember in s3 the same problem just worst because of lag, then s4 still laggy with touchwiz, s5 better touchwiz and still laggy, then our s6 with 3 gb of ram cant hold 4 apps in ram compared to other phone that doesnt have the crappy, useless, laggy, and ugly SH*TWIZ. Samsung always be like that and they will never fix lag and ram problems never. even S6 Edge + with 4gb of ram Still the same crap with touchwiz.
i hope cm arrives to our s6, if not we will be screwed in the new android update 6.0 marshmellow.

I think more to the point, WHO gets to use the memory is what matters. In Sense, the streamlined system processes takes very little of the available ram, and the apps get to fill the rest. In Touchwiz, it's the other way round - system sucks up most of the ram. I think the key to allow more apps in the background is in reducing the amount of ram system is using on top of less aggressive app killing.

For "Used RAM is not wasted RAM" guys...
System RAM is WASTED RAM in the sense that there are less RAM available for multitasking. Period.

I already commented on this topic on reddit. Here's the link: https://www.reddit.com/r/Android/comments/3i8hgs/slug/cue76g4
Also don't forget to read my reply to one of the comments where I explain why Samsung decided to have this aggressive memory management.

bregan90 said:
For "Used RAM is not wasted RAM" guys...
System RAM is WASTED RAM in the sense that there are less RAM available for multitasking. Period.
Click to expand...
Click to collapse
This would be true, *IF* things were being killed because the system is out of memory; however, that is not what is happening here... even with memory to spare, things are getting dumped.

rkhighlight said:
I already commented on this topic on reddit. Here's the link: https://www.reddit.com/r/Android/comments/3i8hgs/slug/cue76g4
Also don't forget to read my reply to one of the comments where I explain why Samsung decided to have this aggressive memory management.
Click to expand...
Click to collapse
Yes I am fully aware what he issue can be resolved by a ROOTED user in minutes but out of reach for most - I did it myself on the 5.0.2 ROM. But even though samsung promised to fix the ram issue in 5.1.1 update, fact is, people still can't open apps and leave them in the background. I hope they will release a "fix" and make the value what they should be.

Thread closed as there is a thread already dedicated do this issue >>> http://forum.xda-developers.com/galaxy-s6/general/galaxy-s6-ram-issues-intentional-t3172296

How To Guide ***CLOSED*** Samsung: How to KEEP apps in the BACKGROUND!

Hey guys,
in case you are not happy with the default One UI apps background management, you can check this solution. In a nutshell, there is a Memory Guardian module part of Good Guardians, that allows the user to switch from default to the so called "quick switching mode" that somehow reduces the aggressive background app killing, i.e. app refresh.
Moderator Edit: YouTube link removed due to violation of XDA external links policy.
I have tested this with following apps:
- Spotify
- Mixcloud
- Instagram
- Snapchat
- Tiktok
- Youtube
Some other users tested this with Waze and other apps and it seems that it works.
What is the idea? Well imagine you are browsing through insta and you find a nice post that you d like to check, but then something else pops up and you switch to another app. Then after you are back to your app (in this case insta) One UI would "refresh" the app, meaning that it will reload it, and you will lose your "last state", i.e. imagine refreshing the app or close/opening it.
Download Samsung Good Guardians from the Store ► https://bit.ly/3yGFUms
Download Samsung Good Guardians for a manual install ► https://bit.ly/3yOehYD
It is also supposed to work with some of the heavy games, test it and let me know if you apps refresh is a bit better (i.e. not refreshed so much) or ... no difference at all.
I have tested this on my S22U with 12G of RAM but I guess it should have a better impact for 8 GB and lower RAM configs.

Appreciate the find!
I have 8gb version and apps are staying open much better now

billmurray1004 said:
Appreciate the find!
I have 8gb version and apps are staying open much better now
Click to expand...
Click to collapse
Nice to hear that! Can you let us know which apps did you test? Also - how much of VRAM (Virtual RAM) do you use?
I makes a bit of difference on my 12GB version so I assumed that it would be even better/bigger impact on 8GB and less.
Strangely enough this function is not very popular, was almost not able to find much info around. The whole Good Guardians tools are widely underestimated and they pack a few good tricks.
Thermal Guardian for example can let you adjust the thermal threshold of your phone, so it can potentially tolerate a bit more heat where battery life is exchanged for better peak performance and hopefully also sustained.

velqn said:
Hey guys,
in case you are not happy with the default One UI apps background management, you can check this solution. In a nutshell, there is a Memory Guardian module part of Good Guardians, that allows the user to switch from default to the so called "quick switching mode" that somehow reduces the aggressive background app killing, i.e. app refresh.
Moderator Edit: YouTube link removed due to violation of XDA external links policy.
I have tested this with following apps:
- Spotify
- Mixcloud
- Instagram
- Snapchat
- Tiktok
- Youtube
Some other users tested this with Waze and other apps and it seems that it works.
What is the idea? Well imagine you are browsing through insta and you find a nice post that you d like to check, but then something else pops up and you switch to another app. Then after you are back to your app (in this case insta) One UI would "refresh" the app, meaning that it will reload it, and you will lose your "last state", i.e. imagine refreshing the app or close/opening it.
Download Samsung Good Guardians from the Store ► https://bit.ly/3yGFUms
Download Samsung Good Guardians for a manual install ► https://bit.ly/3yOehYD
It is also supposed to work with some of the heavy games, test it and let me know if you apps refresh is a bit better (i.e. not refreshed so much) or ... no difference at all.
I have tested this on my S22U with 12G of RAM but I guess it should have a better impact for 8 GB and lower RAM configs.
Click to expand...
Click to collapse
il try this thanks, HTRACK is always closing after 5 or more apps overtake it in the que

velqn said:
Nice to hear that! Can you let us know which apps did you test? Also - how much of VRAM (Virtual RAM) do you use?
Click to expand...
Click to collapse
So...I just sort of excluded all apps for the most part to test. They stay in ram longer but still hit a point where they refresh. Using 8gb vram but haven't seen ram usage above 6gb or so yet

gav83collins said:
il try this thanks, HTRACK is always closing after 5 or more apps overtake it in the que
Click to expand...
Click to collapse
Can HTRACK be further tweaked, perhaps from dev options? I remember seeing something for background processes, like a limitation factor setting.

billmurray1004 said:
So...I just sort of excluded all apps for the most part to test. They stay in ram longer but still hit a point where they refresh. Using 8gb vram but haven't seen ram usage above 6gb or so yet
Click to expand...
Click to collapse
Yep, it`s not a silver bullet, but still some positive impact.

velqn said:
Can HTRACK be further tweaked, perhaps from dev options? I remember seeing something for background processes, like a limitation factor setting.
Click to expand...
Click to collapse
Yeah there is but only upto 4 processes I sometimes have many any more apps open at once, anyway I'm trying it now and here are some screens if you wanna attach to op and il delete from this post once you add them
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

update, i must say this app so far has seemed to keep my HTTrack running great in the background, it ha certainly made a difference, i did have it set "unrestricted" in the app settings/battery setting before and that didnt help, this app now works even with the app power settings set to "optimised"

***Moderator Announcement***
Due to violation of the XDA External Link policy, this thread has been locked.