Database Users

auto killer preset or custom settings

Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.

I use either the aggressive or custom depending on the Rom honestly. DC ROMS= Aggressive. FRESH ROMS= strict. and all others = custom
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

I have the damagecontrol rom and I dont know if it came with auto killer or what...I restored my titanium backup and all i know is i dont have it now...is there an apk floating around for it?

Try the market

I thought it was a custom xda application. I didn't see it in
the market.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?

I used either the aggressive or strick on Fresh 2.0d. So far everything is running the smooth and fast. This the way HTC hero should have come out of the box.

What does each preset do? Is this for speed or battery life or both?

flammenwurfer said:
I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?
Click to expand...
Click to collapse
Damn. I wish Homerun Battle 3D would run great for me. Problem is I get crummy service at work and with it going in and out of 1x and EVDO, causes the game to lag.
I have noticed sometimes on first opening HRB, it force closes but it always opens the second time.

james33440 said:
Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.
Click to expand...
Click to collapse
i'm running aosp 1.6 from gbhil and i used custom autokiller settings.
the way i see it they made these phones with all this ram may as well use it, what good is it to have all this free ram?
1536,3072,4096 (all default) then hidden app is 7680. content provider is 8960 and empty app is 10240. i normally run around 40-45 free ram thats about where i like it. the phone still runs fine all the way down to 20mb free but any less than that it starts going downhill.
so, im MB my settings are 30 then 35 then 40. runs great!

yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.

flammenwurfer said:
yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.
Click to expand...
Click to collapse
Well, mine actually lags on offline play too. As long as the phone isnt switching back and forth, it runs smooth.

How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail

vedwed said:
How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail
Click to expand...
Click to collapse
Using command prompt (adb)
adb shell
# rm Autokiller.apk

troyboytn said:
Using command prompt (adb)
adb shell
# rm Autokiller.apk
Click to expand...
Click to collapse
Ohh thanks much appreciated.
I did not try that way, I figured if it couldn't be done in freshkitchen then it was just built into the rom. Thanks much again

Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.

Sawawa said:
Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.
Click to expand...
Click to collapse
Autokiller does have a built in task killer but its real use is to tweak memory settings at boot and then shuts itself down (so Android can take care of the rest). So, in reality it is not really a task killer per say.

Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.

Sawawa said:
Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.
Click to expand...
Click to collapse
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that

Jus10o said:
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that
Click to expand...
Click to collapse
Either way it should be a choice made by the USER not someone who decides what I need or do not need on my phone. What I choose to have running or not running, there is no need for this garbage for the average joe who just wants something that does not look and feel like Sprint garbage. If its such a great and useful thing put it on the market and let users have a choice.

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?

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.

What does the "Wiper App" do?

Hello.
Recently I've been noticing my U8800 being really slow even on simple tasks like, opening the Messenging or Gtalk app, using Swiftkey and other trivial tasks and I've been paying more attention to the free RAM the Aurora 4.1.
While taking a closer look to the running apps I found the "Wipper App" com.qualcomm.wiper. Well the name sounds suggestive and the qualcomm in the package name makes it sound important but being curious I tried to find what the app really does but google didn't help much.
Turns out it shows a lot xda posts with BatteryStats and similar apps dumps, a bunch of chinese sites and a few "download insert_seach_string here" spam sites.
So... does anyone know what it really does? Is it some sort of task/memory manager from qualcomm?

VuDuCuRSe said:
Hello.
Recently I've been noticing my U8800 being really slow even on simple tasks like, opening the Messenging or Gtalk app, using Swiftkey and other trivial tasks and I've been paying more attention to the free RAM the Aurora 4.1.
While taking a closer look to the running apps I found the "Wipper App" com.qualcomm.wiper. Well the name sounds suggestive and the qualcomm in the package name makes it sound important but being curious I tried to find what the app really does but google didn't help much.
Turns out it shows a lot xda posts with BatteryStats and similar apps dumps, a bunch of chinese sites and a few "download insert_seach_string here" spam sites.
So... does anyone know what it really does? Is it some sort of task/memory manager from qualcomm?
Click to expand...
Click to collapse
You can safely delete it (I always do), and you're correct, it's somewhat of an automatic task killer. Since android 2.3 it's even discouraged to use task killers, the system does it automatically.

fjsferreira said:
You can safely delete it (I always do), and you're correct, it's somewhat of an automatic task killer. Since android 2.3 it's even discouraged to use task killers, the system does it automatically.
Click to expand...
Click to collapse
Well, but it comes on the default Aurora install which is built from the AOSP, seems weird to have superfluous stuff even when dzo and everyone else clearly showed concerns about RAM issues.
I've uninstalled some less important apps, rebooted and the Wiper is no longer taking some RAM, still I bet it'll show up sooner or later.
Now I have >90MB free and the phone is clearly more fluid. It's been a while since I used a 2.x ROM but using this phone on Aurora with the free RAM below 70MB is pure masochism!
Too bad this phone doesn't come with 768MB or 1GB of RAM... I'm already used to charging everyday so the battery isn't a big issue... but lag and stuttering really makes me throw the phone out the window.

I have a hacker destruction on my life. Has completely driven me crazy and drove my friends and loved ones away. Anybody out there that can help please don't want litigation just payback or finished

[Q] How do I keep my browser in memory?

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