[Q] How do I keep my browser in memory? - Nexus 7 Q&A, Help & Troubleshooting

So I just got this thing, and it, like my last 2 Android devices, has this very annoying issue: it loses my browser tabs.
It's really annoying - it means that the browser will reload my tabs when I come back to it.
It also means that I lose the text I typed in the page, and that if I'm on a slow or a metered connection, I'll end up having to wait for my tabs to load and waste my bandwidth.
I tried EVERYTHING.
All the browsers: Dolphin, AOSP Browser, Chrome, Firefox, Boat, Maxthon, Opera.
I set my OOM values to zero.
Tried V6 supercharger.
Nothing helped. I just can't get my browser to stay in memory.
Is there a way to make it stay?
Or just completely kill the built-in multitasking manager Android has?
I'd rather just kill tasks myself with a real task manager. (and don't give me the 'leave it to android, task managers are bad' bull**** - I've heard all that before, and honestly, at this point, I don't even care anymore - I just want my browser to work right)

Have you tried bulletproofing it with the supercharger script?
Sent from my Nexus 7

Yep. Didn't work.
Though considering how long the guide is, I probably ****ed something up. Gonna give it another try.

Tried it again. Didn't work.

Tried Swapper 2
didn't work

tried v6 for the third time
did everything right for sure
didn't work.

SilverHedgehog said:
tried v6 for the third time
did everything right for sure
didn't work.
Click to expand...
Click to collapse
Using the latest supercharger script?
android automatically closes apps after a certain amount of time
The newest supercharger script disables that 'feature' of android
Are you playing intensive games that gobble up ram by any chance?
Sent from my Nexus 7

Yeah, latest V6 - replaced services.jar and etc.
The script says that I'm 200% supercharged.
I do play games, but not that often. Still, I'd rather just manage apps manually at this point - really not happy with Android's idea of multitasking.

SilverHedgehog said:
Yeah, latest V6 - replaced services.jar and etc.
The script says that I'm 200% supercharged.
I do play games, but not that often. Still, I'd rather just manage apps manually at this point - really not happy with Android's idea of multitasking.
Click to expand...
Click to collapse
what rom are you using? using aosp and the aosp android stock browser(not chrome thats in stock) i dont get browser reloads. chrome needs too much ram i think, and am happy that aosp uses the regular android browser. and i agree with you about managing apps/memory manually, i dont like how android manages it also.

simms22 said:
what rom are you using? using aosp and the aosp android stock browser(not chrome thats in stock) i dont get browser reloads. chrome needs too much ram i think, and am happy that aosp uses the regular android browser. and i agree with you about managing apps/memory manually, i dont like how android manages it also.
Click to expand...
Click to collapse
right now i'm on paranoid 2.12

SilverHedgehog said:
right now i'm on paranoid 2.12
Click to expand...
Click to collapse
maybe its the rom with the memory management issues

Chrome always saved my tabs, it was am little annoying to be honest, I would forget to close tabs and end up with like 10-15 tabs open lol

brando56894 said:
Chrome always saved my tabs, it was am little annoying to be honest, I would forget to close tabs and end up with like 10-15 tabs open lol
Click to expand...
Click to collapse
Same here. I actually just opened up about 4 or 5 tabs in Chrome, shut down my tablet, then turned it back on. All the tabs were saved and opened up just fine. I'm on the stock ROM, perhaps it maybe the OP's custom ROM that's causing problems.

Can't be - I tried it on stock, and the issue was there.
Chrome does save tabs, but tell me, when you open it, is the page content instantly showing, or is it reloading it?
For me it is reloading them most of the time. While it's better than nothing, it's still annoying: imagine typing a long post, switching for a moment to check something, and coming back, only to see the browser reload the page - with all the text missing.

Same problem for me. Dolphin keeps getting killed when it is for an extended time in the background although free ram never dropped below 300 mb. I am on Paranoid Android and the newest beta of Faux kernel.

anyone? surely there has to be some solution!
there has to be a way to get true multitasking!

Ups, totally forgot to post my findings in this thread, good thing I have it still subscribed.
I got rid of most of my issues by modifing my service.jar for use of the supercharger script with pepcisko's Windows tool for patching services.jar for V6 SuperCharger (0.9.0.6). I didn't even used the actual supercharger script, just run the Windows tool and applied it to the Nexus 7. IIRC the tool asked me at one point if it should deactivate Android's "kill everything that is longer than 30 minutes in the background function" (WTF?).
Don't forget to raise your minfree settings or your system will start to slow down after some time.
Word of warning: On Paranoid Android 2.13 and Faux Kernel I think my N7 was slower than it was before. But that could be just a negative placebo. And I did still expirince some time that dolphin got killed in the background even though memory usage wasn't up to the minfree setting but it only happend two times at all.
Anyway, I'm now using Clemsyn's Elite Kernel (version of 8/17/2012) @ 1.5 ghz and Jay's Recipe for Buttery Goodness and my N7 is flying.
Tool for patching:
http://forum.xda-developers.com/showthread.php?t=1869663
Kernel:
http://forum.xda-developers.com/showthread.php?t=1831780
Butter:
http://forum.xda-developers.com/showthread.php?t=1831780

yeah, i have that, but as you said, it still gets killed sometimes.

Hi I'm the guy from the other thread. In case you don't know, stock browser is designed to reload the webpage whenever you return to it. It never gets killed. Proof? Disconnect from 3G or WiFi so you have no connection and maybe play a game. Then go back to browser and the page doesn't reload because they know you have no internet and they create a cache file. Lol.
Sent from my GT-I9100 using xda app-developers app

Related

[Q] Lack of RAM - any solutions? HTC DZ

I'm getting quite annoyed at my phone's lack of RAM.
I browse the internet and constantly open new windows (up to the max 4 allowed by the HTC browser, but that's another story) so that I can quickly go back a page when I need to.
If for some reason I go and use a couple of other apps on the phone, and then come back to the browser I constantly find that the oldest 3 pages have dropped completely out of RAM, and the 4th one has as well, and that last one alone loads up again.
This is annoying, time-consuming and messes up my browsing session. Is there some way I can prioritise the browser so that most other apps get killed off before it does?
setspeed said:
I'm getting quite annoyed at my phone's lack of RAM.
I browse the internet and constantly open new windows (up to the max 4 allowed by the HTC browser, but that's another story) so that I can quickly go back a page when I need to.
If for some reason I go and use a couple of other apps on the phone, and then come back to the browser I constantly find that the oldest 3 pages have dropped completely out of RAM, and the 4th one has as well, and that last one alone loads up again.
This is annoying, time-consuming and messes up my browsing session. Is there some way I can prioritise the browser so that most other apps get killed off before it does?
Click to expand...
Click to collapse
Try using firefox instead on the defualt browser .its not perfect yet but its getting
better and better with every beta release .
I don't think an alternate browser will help with Android unwantedly killing off processes.
Incidentally, I tried Firefox a couple of months ago and found it to be completely unusable - I take it it's worth checking out again now then?
Another possibility is to set the Android memory manager to be less aggressive in removing things from memory (you can use an app like AutoKiller to change the settings easily---try tweaking the settings to see if helps with your usage model).
I know AutoKiller will also allow you to lower the oom value for the process (the lower the oom, the less likely the memory manager will kill it in the background), but I don't think this will help for the browser (since the OS will dynamically change its oom each time you bring it to the foreground and send it to the background again). If someone knows a way to make the oom value permanently lower, that sounds like exactly what you want.
Maybe someone else has some ideas. I know often times launchers will have the option to keep themselves in memory, and CM6 has the option to keep messaging in memory (more like your situation), so it should be doable.
setspeed said:
I don't think an alternate browser will help with Android unwantedly killing off processes.
Incidentally, I tried Firefox a couple of months ago and found it to be completely unusable - I take it it's worth checking out again now then?
Click to expand...
Click to collapse
defo ,its much better now i figured since you were annoyed by 4 tab limit
you might find firefox helpful. because it doesnt have limit or if it does its more than 4 for sure also it has an aption called (your tabs from last time) which again i think
you will find it usefull ,you can also sync it with you pcs firefox too .
EDIT: I just tried it to make sure, even if you reboot your phone
and open firefox again you can just press on (your tabs from last time)
and it will restore them all.
The way I see it there are a few things you can do...
Firstly, you could try a renice script. It does what other people have suggested and changes the oomph value to what you like. It was commonly used on the g1 for the dialer so that you wouldn't miss phone calls lol. Its easy to do if you know the syntax, I would make you one myself if I was near a computer lol.
Another thing you could do is try an aosp/CM based rom, as those generally have much, much lower ram usage compared to sense.
Lastly you could try a different browser. There are so many to choose from I'm sure one will fit your needs.
Sent from my HTC Vision using XDA App
I use autokiller on my DZ, you have to have root to use this tho... quite satisfied about it, almost all the time 90+ free ram even when doing heavy stuff... quits the unused shizzle...
cheers
I HIGHLY recommend Dolphin Browser HD.
It is significantly faster than the stock Browser and I have had no issues with Android closing it down. One feature I like is that there is actually an 'Exit' button in the menu for those individuals who have OCD like me and don't like the Browser running in the background when not wanted.
Thus far, this is the best mobile Browser I have used. That being said, I have not tried Firefox and have been a regular user of Opera Mini in the past on other devices.
You should try miren browser once, i'm using it now instead of dolphin hd, and there is a exit button in the menu to. I think its better styled, it has got all the features of dolphin HD without all the bloating around... no gestures tho
cheers
I think its more of poorly optimized software because im pretty sure that google devs don't even utilize the full 512mb of RAM in 2.2. Chances are its the HTC sense limiting you.
Sent from my T-Mobile G2 using XDA App
Yeah I don't think this issue is anything to do with a lack of RAM.
I may try another ROM, however I'm just not up for flashing all the time like I used to with my old Desire or G1 before that. I want a 100% working ROM, preferably something that allows overclocking with a kernel that doesn't break stuff.
And I also want my HTC phone dialler/contacts as well, not vanilla or a cheap copy from the Market. Oh, and I hate the vanilla lockscreen - it's just hard to operate compared to the Sense one. I don't know why it's so hard to unlock side to side on Android - the iPhone takes a little flick and it's unlocked - vanilla Android is like a mission to ensure I've dragged it far enough across to unlock.
And I don't want my keyboard or capacitive keys or quick keys mullered up (I am running a Euro DZ).
If these issues can be dealt with easily when setting up the ROM/phone then I'm prepared to devote a little time to doing it.
So - any suggestions, please?
dont use htc sense roms.
I'm running the virtuous sense rom with his advanced kernel, ive ran the normal rom about 2 weeks, and ive yet to see differences other then a huuuuuuuge speed increase... i would just try it once if i were you its such a relieve...
I played with the latest over the weekend. I ended up uninstalling it. I'd hit a page with scripting and then firefox would lock up and crash.
Web2Go isn't perfect, but at least it doesn't crash as often.
This has nothing to do with RAM. This phone handles RAM just fine. Use Miren and thank me later. It's the best browser by far!
mr.boonet said:
You should try miren browser once, i'm using it now instead of dolphin hd, and there is a exit button in the menu to. I think its better styled, it has got all the features of dolphin HD without all the bloating around... no gestures tho
cheers
Click to expand...
Click to collapse
No text reflow = showstopper.
Unless I'm just being blind, I can't find any way to enable this in the settings for Miren.
It's sense. Sense roms use way more RAM than vanilla roms do. Also check out dolphin HD or dolphin mini browser.
Another issue I'm having which points to lack of RAM (whether this is due to Sense sucking it all up or not) is that programs do not stay in in RAM for that long, ie I go away from an app then return after using a few other apps (not massive games or anything) and when I return the first app's UI has been kicked out of memory and has to load up again, causing anything between a momentary (dialler, mesaging) to an annoyingly long (browser, maps, market) white screen, as data is downloaded again.
People talk a lot of sh*t about the iPhone, but cacheing (caching? sp?) a copy of the last screen for each app before it's closed so you instantly get a visual image of the UI of the app following the opening animation is a pretty good idea IMO.
Has anyone here used the Desire HD? I would think with the 768MB of RAM on that badboy this would be less of a problem.
setspeed said:
Another issue I'm having which points to lack of RAM (whether this is due to Sense sucking it all up or not) is that programs do not stay in in RAM for that long, ie I go away from an app then return after using a few other apps (not massive games or anything) and when I return the first app's UI has been kicked out of memory and has to load up again, causing anything between a momentary (dialler, mesaging) to an annoyingly long (browser, maps, market) white screen, as data is downloaded again.
People talk a lot of sh*t about the iPhone, but cacheing (caching? sp?) a copy of the last screen for each app before it's closed so you instantly get a visual image of the UI of the app following the opening animation is a pretty good idea IMO.
Has anyone here used the Desire HD? I would think with the 768MB of RAM on that badboy this would be less of a problem.
Click to expand...
Click to collapse
I've now installed Enomther's Official rom - what a difference to the speed of the phone! It absolutely flies, even when clocked at a lower CPU speed, and it appears to retain stuff in memory a lot better than the standard Sense rom. Also, there's over 100MB more of free RAM afte a fresh boot.
I'm definitely sold on the efficiency of stock Android, but I'm now missing some of my HTC goodies... I don't think anyone can deny that the HTC dialler is a different level to the rudimentary Android one. And I am missing my HTC browser - that seems a bit smoother, and the text reflow is more reliable, the stock browser seems a bit temperamental on that front.
Other than that, I can live without all the other Sense stuff. So my next question is, can the dialler and browser be installed on my new rom? Do they have any dependencies which would prevent me using them? How would I go about ripping the apps from the HTC rom? I'm an ADB noob so I need some kind expert to tell me how

troubleshooting a slow G1

I rooted my phone a few months back and it's slow switching between a few screens, mostly from calling or web browsing back to home. Painfully slow, sometimes up to a minute. It's always been like this and I just want to know if there's steps I can take to speed it up or if it's just a memory problem. I used Cyanogen 6.1 to upgrade to android 2.2.1
Baseband62.505.20.17u_2.22.19.26I
Kernel 2.6.35-9cyanogenmod [email protected]#2
Build number - FRG83
G1's are just slow!
Try keeping it lite. Uninstalling apps, keeping the essential ones, app2sd?
Don't have loads of widgets on your homescreen.
Task manager, i recommend ATK.
Hope this helps.
chitin said:
I rooted my phone a few months back and it's slow switching between a few screens, mostly from calling or web browsing back to home. Painfully slow, sometimes up to a minute. It's always been like this and I just want to know if there's steps I can take to speed it up or if it's just a memory problem. I used Cyanogen 6.1 to upgrade to android 2.2.1
Baseband62.505.20.17u_2.22.19.26I
Kernel 2.6.35-9cyanogenmod [email protected]#2
Build number - FRG83
Click to expand...
Click to collapse
If you are up to it, flash different ROM. There are ROM out there that is lightweight and fast. My personal favorites is SuperAosp. Currently they just released SuperAosp 6.0 that is fast and also best on bettery life.
flyboyovyick said:
G1's are just slow!
Try keeping it lite. Uninstalling apps, keeping the essential ones, app2sd?
Don't have loads of widgets on your homescreen.
Task manager, i recommend ATK.
Hope this helps.
Click to expand...
Click to collapse
Well, it's slow compared to what's out there, but it isn't "one minute to switch apps" slow for me... without a task manager or auto-killer. Every time I wipe I install nine apps from Market, and ten from SD card. They may sit back and be inactive if I've opened them, but they don't just all run at once and slow down to "one minute each switch"...
I'd agree with the widgets on homescreen though. I tend to avoid them out of preference, but they 'can' eat memory faster than we can down a beer. I don't have anything locked in memory except Messaging. Depending on what I'm switching from, it doesn't usually take that long to switch. If it's something like Skyfire -then no matter what I'm doing, the G1 just dies and Skyfire force closes pretty quickly. It just cannot handle such a memory hog. If I play SNesoid, I never see a force close and it takes seconds to switch. I don't fully understand it, but consider how resource heavy your apps are.
Seems to me you have swap enabled and now it's swapping ...
Try to run without swap / compcache and see if this helps.
Sent from my Gingerbread on Dream using XDA App
AndDiSa said:
Seems to me you have swap enabled and now it's swapping ...
Try to run without swap / compcache and see if this helps.
Sent from my Gingerbread on Dream using XDA App
Click to expand...
Click to collapse
Reducing the widgets helped a lot. It's very usable now until I need to upgrade to 4G. Thanks for the recommendation. What is swap enabled?
Might I recommend trying a different ROM? On my Samsung Vibrant, I had stock TouchWiz and it went slow as hell, I tried another custom ROM and it works great. Much much MUCH faster, trust me get a different ROM, ask around for the best most light weight one, Super AOSP w what someone recommended here? Try that.
Sent from my Xoom
Def check froyobylazlo 5.2 you'll need the new radio/spl hack by ezterry but its soo worth it. Auto memory manager helps out greatly too cuz its based off androids internal tasker instead of just another program made from someone else. With that app your g1 will fly even on default settings, on extreme....lol thank me later
Sent from my HTC Dream using XDA Premium App
My G1 got slower recently, but not one minute slower. I've been really good about not installing anything except I configured titanium backup to run automatically, but the home screen has been crashing a lot too for some reason.
All I did was create three shortcuts for calling and texting someone. Those aren't the same as widgets are they?

[SOLVED] Swiftdroid is killing apps way too quickly. How to prevent this?

Hey,
I was using swiftdroid last two days and it appears to be killing all apps almost as soon as I quit it. I checked with Advanced Task Killer and it appears swiftdroid is trying to keep at least 45MB free even after I enabled 32MB swap with built-in VRAM.
This is very annoying. It keeps quitting facebook chat and IMO chat as soon as I switch to another app. I'm aware GT540 has very low memory but the thing is in stock, I didn't have any problem even though I didn't have VRAM/swap. I usually get around 25MB RAM free all the time and most apps stay in memory. I'm usually like able to launch the IM app, facebook app and still be able to use the browser or file expert or messaging app.
So, is there's a workaround? It's really annoying when it keeps quitting the IM app just like that!
Sorry for saying it's annoying. I know we get this for free and I shouldn't be complaining at all. It's just that it pissed me by quitting IM app, the only app I want to stay in the memory.
What version of Swiftdroid are you using
The latest one (M5), has improved RAM management a lot
And comes with better battery life, too
I got the same thing. Always 40-45mb free and apps being killed quickly. I'm on M5. Someone said that Joestone's AOSP is better in this aspect, but I didn't test it yet.
Mitalca:
I'm on M4. I downloaded M5 only today. I don't think it lacks good RAM management. It's just that its memory management settings have been tweaked to keep maximum possible amount of RAM free so that any new app will launch faster. Am sure there must be a switch to change it.
EazyLuke:
I don't really have any problems with stock 2.1. I checked out Joe's AOSP and swiftdroid. The only real advantage apart from speed is voice input. In Joe's AOSP, I couldn't get voice to work. In swiftdroid, it worked.
that's what I meant with RAM management
Maurik changed the settings on M5
mhoangtr said:
In M4 rom, lowmemorykiller setting is 6,8,16,20,32,40 MB so apps killed too fast.
If you want to keep apps longer, try set to 6,8,16,20,22,24 MB (this is default value of android).
Click to expand...
Click to collapse
But I don't know how can you change that setting in M4
Try M5, if it ain't working for you, go to Joe's
Mitalca said:
that's what I meant with RAM management
Maurik changed the settings on M5
But I don't know how can you change that setting in M4
Try M5, if it ain't working for you, go to Joe's
Click to expand...
Click to collapse
@Mitalca: That's the whole purpose of the post. I couldn't find the option where I can change 6,8,16,20,32,40 MB to 6,8,16,20,22,24 MB.
How do I change it?
You can change these values with e.g. this application https://market.android.com/details?id=com.lim.android.automemman&feature=search_result
I installed this app: https://market.android.com/details?id=com.rs.autokiller
It does the same thing.
I set the values to 6-8-12-18-20-20. Now I'll have to see if that brings an improvement.
EDIT: Tested it for a few minutes. And it seems to be an awesome improvement! I can switch from Facebook, Twitter and Browser, and everything is kept in memory, meaning these apps don't have to reload everything!
And it seems to be stable. I also use some of the "advanced system tweaks settings".
Thanks you guys.
XDA memebers. Useful as ever.
I'm gonna try both the apps and keep the app with slicker interface.
M5 isn't working.
Says assert failed when trying to flash via recovery.
Trys v6 SuperCharger!
http://forum.xda-developers.com/showthread.php?t=991276
It Works Perfectly on our GT540!
I found this problematic, too.
I installed M5 yesterday. Everything is great except this (and I don't like oversensitive accelerometer, but it's not urgent problem ).
Last night I listened Music player, and surfed via Miren. After two opened tabs, Music player shut down . After four opened tabs, phone rebooted. Factory widgets' widgets are useless with this agressive RAM menagment.
hash87 said:
You can change these values with e.g. this application https://market.android.com/details?id=com.lim.android.automemman&feature=search_result
Click to expand...
Click to collapse
Thanks man.
Works excellent .
EazyLuke said:
I installed this app: https://market.android.com/details?id=com.rs.autokiller
It does the same thing.
I set the values to 6-8-12-18-20-20. Now I'll have to see if that brings an improvement.
Click to expand...
Click to collapse
To bad - it want access to too much permissions.
Access to too much permissions? Use LBE Privacy Guard!
What permissions?
And by the way, I wrote a PM to Mur4ik and asked him to try this app out. Maybe he'll change the numbers for RAM-management in his next release if he thinks it's an improvement.
EazyLuke said:
What permissions?
And by the way, I wrote a PM to Mur4ik and asked him to try this app out. Maybe he'll change the numbers for RAM-management in his next release if he thinks it's an improvement.
Click to expand...
Click to collapse
There are plenty of custom ROMs that use Mur4ik's config. It boils down to personal preference. Do you want newer apps to launch really fast or do you want certain apps to stay in memory all the time?
Multi-taskers would prefer to have all apps in memory while people who like doing one thing at a time or who use phone for gaming mainly would prefer Mur4ik's config which launches apps faster.
The best thing for Mur4ik is to include an option to change the memory management config depending on user.
After changing the numbers my apps don't really seem to open slower.
In my opinion Mur4ik could lower the numbers a little bit, to allow better multitasking, but still let new apps open fast (just my personal opinion).
But I don't say he HAS TO do that, just a suggestion, if he doesn't like it it isn't a problem at all, because everyone can simply adjust the numbers easily .
That's true. xD
If I were to suggest, I'd suggest to add the option to change these settings. Apps opening fast depends on what individual apps are in the memory and what new app you are opening.
For example, if you open Angry Birds while your memory is at 16MB, you certainly can't expect it to open fast.
On the other hand, if you open messaging app while memory is at 16MB, it certainly will open faster.
But, I really disliked the apps Swiftdroid had in the latest release. I had to get rid of the whole GO suit with Uninstaller for Root.
nibras_reeza said:
But, I really disliked the apps Swiftdroid had in the latest release. I had to get rid of the whole GO suit with Uninstaller for Root.
Click to expand...
Click to collapse
Try M6, was released yesterday, it's completely clean! Only Tonepicker and QuickSettings are added.
SWEETTTTTTTT!!!!!!!!!!!!! xD
you could also try to put mur4ik rom in the kitchen and play with autokiller settings ...
this is michalak8 from android.com.pl (mike's froYo dev) looking for that magic 10 posts to post my rom) Could someone close the rom thread in development section - I would like to post it my self without google-translate bugs
mikegapinski

V6 SuperCharger for a laggy phone

I just want to know if anyone else is running this script. I refused to believe my Nexus S was not behaving, after all, it's a Nexus S! But, eventually even I had to get real. Truth is, lately, no matter what ROM I'm running after a few days things would slow down way too much. Lag, Launcher redraws, FCs due to lag. Things were too slow.
Anyway, I used the V6 SuperCharger script and it really has changed things. I used the MegaRAM option for 512 MB phones and I swear it has been a revelation. Even overclocking couldn't bring about this change. Currently, I'm on MIUI which most people consider to be a bit heavy and clunky. However, after supercharging with the MegaRAM option and Bulletproofing the launcher it's unstoppable! Highly recommended for those of you experiencing phone lag. Make sure to follow the Dev's instructions for using his script. All credit to user: zeppelinrox. Amazing stuff!
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
I used the 2nd MegaRAM option as well. But, I'm going to test out the first option. As I understand it, the more memory you want free in the 3rd slot the less multi tasking you can do (as this is where the secondary apps will be places)...I THINK!
As per that thread if 25 MB is good enough on a Milestone, a Nexus S should do well with 40 MB.
THIS from the thread:
zeppelinrox said:
Additional Info: You can find each app's priority and OOM.
....................... In AMM, Press Menu > Running Processes > Group by OOM grouping.
....................... Expand each group and see what apps are included and each app's priority level. (Higher numbers get killed first!)
....................... If you tap on an app, you can get additional info. Tip: Check and see what's included with android.process.acore
The default minfree values ("kill thresholds") for each OOM group are, as far as I can tell: 6, 8, 16, 20, 22 and 24 mb. (CyanogenMod 6.1.2)
This means that: when free memory lowers to 24 mb, EMPTY_APPS get killed; at 22 mb free ram, CONTENT_PROVIDER apps get killed; and so on...
Now, because the Milestone has only 256 mb of memory, I found these numbers too low, especially the 3rd one.
Basically, with those settings, you will usually be sitting with only 20 - 25 mb of ram.
Possibly less. Basically, it's the 3rd number (16) + 5. That's your free memory.
And my phone just chokes when it has that little ram available. Lag, home screen redrawing, the launcher getting killed.... ugh....
After extensive fiddling around, I've come to the conclusion that setting the third slot to about 25mb works great.
No home screen redraws while not being too aggressive on secondary/background apps while having about 30-35mb free all the time
BTW, free ram is not wasted. Android will use that memory to cache the file system and this speeds things up. See this informative post.
Click to expand...
Click to collapse
Si_NZ said:
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
Click to expand...
Click to collapse
Just tested the 1st MegaRAM option and things are quite smooth. Launcher is not as buttery as with the 2nd option but, it's still great. The browser does quite well too, pinch to zoom is smooth but, scrolling is a little stuttery on a heavy page like Engadget's.
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
never heard of this till this morning, thanks for bringing it up
trying it out now
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
I love it when a tweaker tells tweakers not to tweak.
Really!
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
you should know that two scripts running can cause issues......
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
I didn't said anything against your script, just told the users to not use it on my custom ROM. A think that as maker of your script you should know - two RAM scripts on same ROM are doing only damage.
They don't stay running.
They execute and end.
Whichever one runs last is the one that sticks.
Many people were using juwe's script with the V6 script and things ran fine so it's not a big deal.
Of course, if somebody wanted to, they can delete the minfrees in any of their custom roms and plug them into supercharger...
Why do you guys like scaring the crap out of people for nothing? lol
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
Great to hear from you. Haha. Just about to ask you
does it work well with cm7?
mohsin125 said:
does it work well with cm7?
Click to expand...
Click to collapse
I'm running it on cm7, and my phone seemed to be a bit snappier
time will tell though
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
rican408 said:
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
Click to expand...
Click to collapse
use this guide, and it will be easier than you could imagine
http://forum.xda-developers.com/showthread.php?t=1126940
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Haizum74 said:
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Click to expand...
Click to collapse
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Just an update on my settings. The MegaRAM seem to really speed everything up but, I find that they weren't being nice to my Whatsapp (I was missing messages now and then) I think Whatsapp would receive the message but get immediately killed before it could broadcast the notification. Once it even seemed to exit in app for no reason at all. So I switched to Balanced Settings 3 and so far Whatsapp as well as the launcher and phone in general has been very responsive.
Sent from my Google Nexus S using XDA App
deejaylobo said:
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
I went for Megaram option 1 (I think). I disabled password and it then worked but by this time I had uninstalled the script. Any particular option you suggest? Cheers for the reply too.
It depends on your usage. I would suggest starting out with Balanced settings 3 and moving up or down the menu depending on whether you want more(down) or less speed(up). I've found that the trade off is speed vs multitasking. Though, I think zeppelinrox could confirm whether I'm right.

ICS 4.04 disapointment ...

Hello, I just installed the stock ICS on my Xoom, and I'm disapointed ...
As everybody was saying "the Xoom is now a whole new device", I was expecting so ...
There are good points with ICS :
- new functionalities like icons directories.
- gpu acceleration for a few 2D applications.
- a few websites are now smoother.
- typing texts in forums is now fast.
- a lot more available memory : around 512Mb instead of 400Mb in 3.2.1. EDIT : since a reboot of my Xoom, the available memory dropped down to 360Mb !!!
But I was expecting a lot more fluidity, smoothness, from the 2D applications of Android.
- the new market is more laggy than the one of honeycomb 3.2.1.
- some web pages are smoother now, but some other are slower !!!! XDA for exemple lags more than in 3.2.1 !!!
- the 2D GPU acceleration does not work for all applications : even when "force 2d acceleration" is selected, some applications become smooth, some other don't, even when they are the same kind of applications.
- stock web browser crashes more than in 3.2.1.
- on stock browser search string on some forums don't work anymore (try on XDA !), same problem with some dropdown menus which let the web page disappearing ...
- the new kill apps system in ICS does not really kill all apps. So we still need an app killer.
- the portrait mode is still laggy compared to the landscape mode.
- the available memory, when the Xoom has just been rebooted, vary between 510Mb and 360Mb ... !!! With absolutly no change in my Xoom configuration.
- When you force OFF the screen rotation in landscape mode, if you lock the Xoom and put it in portrait position, when you unlock the Xoom the display will be in portrait mode, and right after the Xoom will be unlocked it will go back to Landscape mode. This bug didn't exist in Honeycomb.
- the cursor to select text to copy seems more difficult to position than in Honeycomb.
- if you kill the stock browser with an app killer, when you relaunch the browser it will then open the last visited website, which is as expected. But if you kill the browser with the Android task killer, then the browser (when relaunched) will display nothing.
So I don't feel like I have a new device, some things are better, some worse.
As I am very concerned by the Android fluidity, ICS is a big step forward, but there are still some more steps to do, and I hope we will be able, one day, to see Android as fluid as an ipad on our Xoom ... But I guess I should stop dreaming.
Maybe you should trying running one of those custom ROMS and see if you see and
better performance or features..it's worth a shot
I think even Stevie Wonder saw this thread coming.
dizzy33 said:
As I am very concerned by the Android fluidity, ICS is a big step forward, but there are still some more steps to do, and I hope we will be able, one day, to see Android as fluid as an ipad on our Xoom ... But I guess I should stop dreaming.
Click to expand...
Click to collapse
Stop running crappy apps and it'll be "fluid".
ZanshinG1 said:
Stop running crappy apps and it'll be "fluid".
Click to expand...
Click to collapse
There will always be people taking personaly what you say about their toy ! This kind of people should just open their eyes, and stop being agressive.
glock20c said:
Maybe you should trying running one of those custom ROMS and see if you see and
better performance or features..it's worth a shot
Click to expand...
Click to collapse
You may be right but I would expect Google to optimize more Android without the need of tuning a custom Rom to gain (maybe) a few more images per seconds ...
With this thread I wanted to ađvise people who are still waiting for the ICS update to minimize what they can expect of it, this way they may not be as disapointed as I was...
dizzy33 said:
There will always be people taking personaly what you say about their toy ! This kind of people should just open their eyes, and stop being agressive.
Click to expand...
Click to collapse
No.
Most of the stuttering is caused by apps which are written by developers who don't really understand Android,
Seriously.
Pay attention to which apps aren't responsive. Look at memory use, wake locks, watch for unnecessary services and background threads.
Eliminate apps one-by-one until stuttering in menus and the desktop stops. Don't run live wallpapers.
Factory reset. System settings from prior Android revisions can cause problems.
I have fixed many of my friends' Android devices when they blamed the device or OS for lag.
Stock 4.04 is quite responsive and fluid. If yours isn't, it's probably the apps you've installed or settings conflicts.
Change animation settings under development to none or at least down to .5 from 1.0.
Use a third party launcher and third party browser if unsatisfied with stock. We have choice...we can use it.
My Xoom is as smooth as butter...no lag or stutter at all.
I always choose the apps to install according to their fluidity. I know some apps are badly developped. I also have no apps running in background (that's why I choosed the stock ICS), always killing running apps before running a new one. I also don't use animated background.
I do my best to let my Xoom run as smooth as possible.
dizzy33 said:
I always choose the apps to install according to their fluidity. I know some apps are badly developped. I also have no apps running in background (that's why I choosed the stock ICS), always killing running apps before running a new one. I also don't use animated background.
I do my best to let my Xoom run as smooth as possible.
Click to expand...
Click to collapse
Have you changed your animation settings under Developer Options (in Settings Menu, toward the bottom) If you don't need animations, then change the settings to "none" it will make a difference.
okantomi said:
Change animation settings under development to none or at least down to .5 from 1.0.
Use a third party launcher and third party browser if unsatisfied with stock. We have choice...we can use it.
My Xoom is as smooth as butter...no lag or stutter at all.
Click to expand...
Click to collapse
Thanks for these advises but the problem for me is not the speed of the device but its fluidity. So changing the animation setting did change the speed of the way the menu are displayed but not the fluidity of the animations.
About the fird party launcher, I think it will not make it run smoother as it will run in the background and occupy memory.
dizzy33 said:
Thanks for these advises but the problem for me is not the speed of the device but its fluidity. So changing the animation setting did change the speed of the way the menu are displayed but not the fluidity of the animations.
About the fird party launcher, I think it will not make it run smoother as it will run in the background and occupy memory.
Click to expand...
Click to collapse
Why, I don't know, but I have always found increased smoothness from launcher like ADWEX. As they say, "your mileage may vary." The configuration in my signature represents what I think is probably the best, smoothest and fastest combination I can find. I also have tons of apps and a pretty elaborate theme and still my Xoom is butter-smooth. It can be done.
dizzy33 said:
I always choose the apps to install according to their fluidity. I know some apps are badly developped. I also have no apps running in background (that's why I choosed the stock ICS), always killing running apps before running a new one. I also don't use animated background.
I do my best to let my Xoom run as smooth as possible.
Click to expand...
Click to collapse
Why kill the apps before running a new one? If you are choosing apps based on how well programmed they are that seems completely unnecessary.
Sent from my ADR6300 using xda premium
Hi,
You didn't mention what apps you are running.
I'm running 4.0.4 stock rooted - and no issues in general. It got very laggy once after running for a week, but a reboot fixed it. Like any OS, very complex and not perfect - reboot once in a while.
I honestly don't find ICS to be very much different than HC (nor did I expect it to be). (ICS is what google wanted HC to be but ran out of time, so released HC)
dizzy33 said:
Thanks for these advises but the problem for me is not the speed of the device but its fluidity. So changing the animation setting did change the speed of the way the menu are displayed but not the fluidity of the animations.
About the fird party launcher, I think it will not make it run smoother as it will run in the background and occupy memory.
Click to expand...
Click to collapse
Adw auncher makes for a much smoother home screen experiance than stock. Stock struggles with more than a couple of Widgets. Its a diferant experiance, but definatly faster.
dizzy33 said:
I always choose the apps to install according to their fluidity. I know some apps are badly developped. I also have no apps running in background (that's why I choosed the stock ICS), always killing running apps before running a new one. I also don't use animated background.
I do my best to let my Xoom run as smooth as possible.
Click to expand...
Click to collapse
Which is why you were so quick to see my original suggestion as a personal attack?
ZanshinG1 said:
Which is why you were so quick to see my original suggestion as a personal attack?
Click to expand...
Click to collapse
I thought you took it as a personal attack because you said "stop using crappy apps", which to my point of view is agressive.
That's it. I'm sorry if your goal was not to be agressive.
You know, there are lots of fixes for any problems this device had at one time, but many require rooting and installing custom roms/kernels/recoveries and certain non-stock apps. I realize that some people like staying stock as much as possible...I don't. I want to get root immediately and start customizing. That's just me. Some people don't like to eat meat...I do. Some people can't imagine not driving everywhere...I've never owned a car. We're all different. But sometimes you just have to understand that your desire to stay all stock comes at a price. Lag exists. That's why custom roms exist...to eliminate lag, among other brilliant things.
okantomi said:
You know, there are lots of fixes for any problems this device had at one time, but many require rooting and installing custom roms/kernels/recoveries and certain non-stock apps. I realize that some people like staying stock as much as possible...I don't. I want to get root immediately and start customizing. That's just me. Some people don't like to eat meat...I do. Some people can't imagine not driving everywhere...I've never owned a car. We're all different. But sometimes you just have to understand that your desire to stay all stock comes at a price. Lag exists. That's why custom roms exist...to eliminate lag, among other brilliant things.
Click to expand...
Click to collapse
OK, so I'll check the custom ROMS ... Can anyone specify which ROM is the best for fluidity ?
I didnt have or notice any of the problems you had on stock ICS
I am running the following rom on my xoom atm and have had no issues
http://forum.xda-developers.com/showthread.php?t=1437358

Categories

Resources