Should you disable it? Well, Froyo was built optimized with JIT. If you are running a 2.1 ROM - xtROM or xtrSENSE, for example - you should probably not enable JIT (it is disabled by default in those ROMs). If you are running a 2.2, or Froyo ROM, you should probably leave it enabled. It is true that there have been apps in the past that do not run well with JIT enabled - Pandora rings a bell - but I believe that particular problem was solved.
There is no harm in disabling JIT in 2.2 to see how your phone runs, but I am willing to guess that if you run it without JIT (you need to restart the phone to enact the change) for a few days you will probably not notice a difference. If you do, and things are better, leave it that way.
I think it depends on the specific Eris. Whenever I run JIT with 2.2 my phone runs fine for a day or 2 then starts lagging really bad. Are there other variables that could be contributing? Probably. But it works better for me iwth it off so thats how I leave it. Right now I have my 2.2 rom running as smooth as xtrROM and thats saying alot.
JIT disabled
Autokiller set to strict
CPUBoost w/ governor set to ondemand with 710/245 cpu using CFSv9.
Well, if we are trading anecdotes, I have tried running CELB with JIT disabled and it lags more for me (and seems to burn battery faster) than JIT at default enabled. I think it's less the Eris than it is the mix of user apps that you have installed.
And, I can't run my phone at Autokiller strict, as it starts shutting down apps that I want to keep running in the background (namely, Tweetdeck), so updates stop being delivered. If you are going to play with Autokiller - and I agree that it is a great app - I'd start with "Optimum" defaults and see if things are better, then start dialing up to higher levels.
But, again, everyone's requirements are different.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.