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.

[Q] Apps kept coming back after autokill -> memory leak -> lag

Hi all,
1. I've got these applications (Smartone-Vodophone SV app, 5 days weather, google map, social hub and such) that would keep coming back, relaunching themselves even after I put them onto my task manager's autokill list. Seems like they would wait around for me to enable the wifi/3G connection and then launch themselves. I even installed other apps to disable autolaunch and they would still launch themselves in the background every now and then. I had to kill them every time I unlocked my screen and these "launching and killing" cycles eventually depleted my memory down to below 100MB, making the lag situation even worse. Does anyone know how I can stop them from launching, without having to uninstall these apps?
2. I haven't installed the lagfix and I understand that the fix has to do with reformatting the apps' partition with a faster file system to reduce the lag (probably by giving it faster I/O access to the program's binaries?) I'm still waiting for Froyo, which should be out in a couple of weeks in my country. Does anyone know if Froyo would take care of this file system problem? Even with the Froyo or one-click lag fix, it still would not solve the apps launching and memory leak problem, right?
3. I notice that after I've installed more apps, the lag situation got worse. I was playing some songs on the external SD cards and it choked once in a while. I made sure I killed all the other apps and that I still got 100+MB to run just this one song player app and yet it would still choke. This tells me that the lag has nothing to do with available memory. And the player app was stock that came with the phone so there shouldn't be any fragmentation issue (apps installed later might have?) that makes it run slow. And if its the bad file system, this app, running all by itself, should have all the I/O bandwidth to itself so the access to the app's binaries should not have any lag... and neither should the access to the songs on the external SD card. So what exactly is causing the lag then? I don't see how the lagfix would solve this problem either. I actually have read that the lags would come back after a period of usage even with the lagfix. Anyone got an insight to this problem? What exactly is causing the lag? and why installing more apps seem to make it worse? and would Froyo be able to fix all these problems?
Thanks a lot.

@boarder838
I think you really need to read a lot more about just how Android works as you seem to have some strange ideas about how it works.
To start with you need to realise that having 200mb or 100mb of free Ram makes zero difference to performance only when you have no free Ram is it a problem and even then the system will sort it out for you by closing the least used program. Free Ram is just wasted Ram as it's not doing anything and will not make your device respond or work faster using a Auto Task Killer is wasting your battery and slowing down your device not speeding it up and saving battery as you seem to think. As i have pointed out above stop obsessing over your free Ram amount as unless you have none its not a problem stop using a Task Killer and you will most probably see your device responds faster as its not constantly killing things and just leaves them open doing nothing in the back ground which doesn't use Ram or Battery so just leave them be.
Yes Froyo will bring many improvements to our devices but won't fix a problem that doesn't exist re memory leaks and apps launching that you seem to think you have. I don't know but some of those apps may be system apps that need to run all the time which is why they keep relaunching. As for a lag fix well that's what we are all hoping for but if not I'm pretty sure the great people of this forum will come up with an easy to apply fix to it.
I have absolutely no problem playing Music or even streaming it over Bluetooth no lag stutters or break ups at all although my Music is on the Internal SD card. Maybe you should look at the quality that you have encoded your Music in as that may be causing problem. maybe some of the apps you have installed are also causing a problem but its impossible to know as we all install different apps and have different set ups.
I don't know how much experience you have with Android devices or flashing Roms but if you read enough and understand it you have the possibility to flash custom Rom's and various tweaks and fixes to make your device how you want it. That's part of the beauty of Android but don't rush into anything you are not sure about as you can end up with an expensive brick so read things many times and make sure you understand step by step what you are doing if you are going to attempt any of these things.
If you look at my signature you will see i am running a Custom Rom that includes a lag fix and various other tweaks it also allowed me to remove some of the programs in the official Rom that i didn't want or need. For me my device runs nice and smooth and fast of course I'm looking forward to Froyo and all the improvements that will bring but I'm quite happy with my Galaxy S the way it is now. Oh and this is my second Android device and I've never used a Task Killer never mind an Auto Task Killer and have never seen an out of Ram message either.
Marc

exactly what he said ^

Hi Marc,
Thanks for spending time to read through my long post and reply to it. I probably didn't explain my problem clearly in my post.
There were a couple of reasons I wanted to kill/stop the apps from starting:
1. Even before I installed any of those apps killer, I noticed that the available memory kept going down after a couple days of usage and it went down to below 100M. I figured some of the apps would need 10's of MB to run so I thought I should at least keep 100MB around so that it wouldn't run out of memory and start swapping when I start those apps. I don't know enough about Android but I assume its just like linux or other OS, when it runs out of physical memory, it would start swapping and slow things down. Even after I started using task killer and killed all the other tasks, the memory level would still not recover. That seems to point to a memory leak problem but using "Memory Booster" to do garbage collection seems to help. Still, it would be nice to be able to stop them from launching in the first place. <-- my first question.
2. I do not want any jobs/processes/apps that I don't need to run in the background to drain my battery. I don't think I can say for sure that those apps are all just idling and not using much CPU/battery. There are quite a few of them so if each of them use some CPU time/battery, it will add up eventually. Note that these are not system processes (or daemons as in unix's init.d). They are crappy apps from the cellular provider so I'm pretty sure they don't have to be running (they're probably just collecting my personal data or smth). I just thought there would be a way to stop them from launching without uninstalling them.
Thanks for answering my question regarding Froyo. If they would do the filesystem lagfix then I'll just wait for that update.
As for the music stuttering problem, my songs are on the external SD card but my old Nokia E85 phone has no problem playing with those songs on the same SD card. As I have pointed out in my last question, I was only running one app and with plenty of memory so it had nothing to do with available memory. I also suggested that however bad the filesystem was, the I/O bandwidth should still be enough to run this one music player app (access the program binary/libraries?) and to retrieve data from external SD card to play the music smoothly. So applying the lagfix probably won't help this problem though I still haven't tried the lagfix. Now I'm thinking that one of the task killer might be killing some system processes which were needed by the music player. I probably should uninstall all these task killers and see if it would help.
I have gotten the phone for only a couple of weeks so I haven't gotten around to try flashing different roms or rooting my phone. There's so much info scattered around on the web and I can't seem to find a source that really has the authority or complete information. I'll see if I have time later to look into all the tweaks and such but for now its just a phone to me and I just want it to run smoothly without having to spend too much effort to tune it.
Don't get me wrong. I still love the flexibility and customization opportunities provided by the Android platform and I just love to show off my "Beautiful Weather Widget", "Live Aquarium Wall Paper" and my cool 3D scrolling "Launcher Pro" to my iphone4 buddies and make them drool.
Thanks for you comment and let's hope Froyo will bring us a smooth running and stable platform.
Dogmann said:
@boarder838
I think you really need to read a lot more about just how Android works as you seem to have some strange ideas about how it works.
To start with you need to realise that having 200mb or 100mb of free Ram makes zero difference to performance only when you have no free Ram is it a problem and even then the system will sort it out for you by closing the least used program. Free Ram is just wasted Ram as it's not doing anything and will not make your device respond or work faster using a Auto Task Killer is wasting your battery and slowing down your device not speeding it up and saving battery as you seem to think. As i have pointed out above stop obsessing over your free Ram amount as unless you have none its not a problem stop using a Task Killer and you will most probably see your device responds faster as its not constantly killing things and just leaves them open doing nothing in the back ground which doesn't use Ram or Battery so just leave them be.
Yes Froyo will bring many improvements to our devices but won't fix a problem that doesn't exist re memory leaks and apps launching that you seem to think you have. I don't know but some of those apps may be system apps that need to run all the time which is why they keep relaunching. As for a lag fix well that's what we are all hoping for but if not I'm pretty sure the great people of this forum will come up with an easy to apply fix to it.
I have absolutely no problem playing Music or even streaming it over Bluetooth no lag stutters or break ups at all although my Music is on the Internal SD card. Maybe you should look at the quality that you have encoded your Music in as that may be causing problem. maybe some of the apps you have installed are also causing a problem but its impossible to know as we all install different apps and have different set ups.
I don't know how much experience you have with Android devices or flashing Roms but if you read enough and understand it you have the possibility to flash custom Rom's and various tweaks and fixes to make your device how you want it. That's part of the beauty of Android but don't rush into anything you are not sure about as you can end up with an expensive brick so read things many times and make sure you understand step by step what you are doing if you are going to attempt any of these things.
If you look at my signature you will see i am running a Custom Rom that includes a lag fix and various other tweaks it also allowed me to remove some of the programs in the official Rom that i didn't want or need. For me my device runs nice and smooth and fast of course I'm looking forward to Froyo and all the improvements that will bring but I'm quite happy with my Galaxy S the way it is now. Oh and this is my second Android device and I've never used a Task Killer never mind an Auto Task Killer and have never seen an out of Ram message either.
Marc
Click to expand...
Click to collapse

Oh I found the problem with stuttering music. It was the "beautiful weather widget"! I tried removing all the task killers and aquarium etc and it still wouldn't work. As soon as I removed the weather widget there was no problem with music playback anymore. Anyone has the same problem that pretty weather widget?? I've already set the refresh period to every 3 hours but it still wouldn't help?!

Nook memory leaking...anyone else?

I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?

Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
The fact that you can see an application's process "running" does not mean the application is running or doing anything. It may simply be there because Android needed it at some point, and has decided that it would be best to keep it around in case it needs it again.
...
Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations.
Click to expand...
Click to collapse

czarjohn said:
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Click to expand...
Click to collapse
It will not reboot when it runs out of ram. My suspicion is you're seeing the 'random reboot' problem that happens on the stock B&N ROM. See here for a workaround: http://nookdevs.com/NookColor_Issues
mrapollinax said:
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
Click to expand...
Click to collapse
I totally agree with this on 2.2 upwards... Unfortunately 2.1 is a little more lax about memory handling, and can sometimes get quite slow and jumpy and can benefit from a flush. I use System Panel and exclude all of my important tasks and widget, and if I see my NC getting jumpy or such, I'll kill all (which excludes those already excluded apps of course). But auto task killers are always a bad idea.

mrapollinax said:
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
Click to expand...
Click to collapse
Thanks for the post, that was a great read and I am uninstalling my task killer now.
Mike

Regarding task killing, I recommend something like Watchdog to monitor apps as opposed to an auto-task killer. Watchdog has a really nice widget for monitoring system resources and in the rare occasion that an app starts misbehaving, it will give you a notification and the option to kill it. Otherwise letting the OS handle things itself is the best option. I've been using computers for a very long time and idea of leaving apps running seems counter-intuitive, but in my experience there is no reason to not trust what Google says about the issue.

czarjohn said:
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Click to expand...
Click to collapse
i am also having these problems but im on honeycomb
i dont have any task killer installed but i installed one last week to check if my memory was leaking or if the rom was just rebooting

Great stuff here. Thanks for all the info. I think it was the random reboot since it did seem to happen most often when i was putting the nc in to standby.
Lots of good stuff here. Gonna miss the little green widget on my home screen, but i guess google knows best...

czarjohn said:
Great stuff here. Thanks for all the info. I think it was the random reboot since it did seem to happen most often when i was putting the nc in to standby.
Lots of good stuff here. Gonna miss the little green widget on my home screen, but i guess google knows best...
Click to expand...
Click to collapse
well i installed honeycomb preview v2 on my eemc from samuallhaff and it seems to remove this problem
i suggest you switch to his rom if you want the memory leaks to stop

luigi90210 said:
well i installed honeycomb preview v2 on my eemc from samuallhaff and it seems to remove this problem
i suggest you switch to his rom if you want the memory leaks to stop
Click to expand...
Click to collapse
Don't confuse "memory leaks" with "weird wifi sleep reboot bug".

[[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

Task switching without reloading? What memory is required?

Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?

douginoz said:
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
Click to expand...
Click to collapse
Try enabling zram, I haven't tried it personally but its supposed to allow for more multitasking.
Sent from my Nexus One using xda app-developers app

Moved To Q&A​
You may of considered it dev based, but its a question so belongs in the Q&A section.​

I've tried ZRAM now for a couple of days but makes no difference. I also have the problem on another Android device. I'm convinced its some sort of design limitation of the opsys or something. When I start up Grindr, it takes a long time to load all the images, make connections, etc. Then I start of Gruff, and it does the same. As long as I don't try to go to another app, I can flip between the two of them without them restarting/reloading/reinitialising themselves. That is clearly because their pages didn't get swapped out of memory or flagged for deletion and deleted.
But if I do something else, or even try to use additional functions within either app, its too much and the next time I try to flip to the other app, it has to reload and reestablish connections etc.
Its not just those apps either. The same with a game like Candy Crush. Or many many apps.
So either my devices don't have enough memory of some form to allow many concurrent apps to run without being swapped out, or Android can't handle it and unnecessarily swaps out or deletes a process's memory pages to make room for the next process, >>> even if the device has plenty of memory<<<.
I don't know which type of memory the opsys needs if this is the case. I'd like to know so that i can make sure there's ample available so that this constant restarting doesn't keep happening. It seems stupid to me that Android does this if the device has got "heaps" of available memory (no pun intended). Newer devices will continually have more and more built in memory, so if Android is doing this arbitrarily and not because of space issues then its, well, stupid.
I have to assume its my devices that are the problem. They're both old (Nook Color, Nexus One). But with the NC, I'd assume we can partition some of that 5GB for use as main memory to run lots of processes concurrently, without this annoying swapping/page deletion/forcing re-inits all the time.
I'm also having problems figuring out where in XDA to post this question - its not NC specific, or dev specific, but I need answers from people that know the Android architecture so I can work out if its possible to stop this from happening.